Skip to content

feat(browser): show actionable operation and recovery states #43

Closed

Description

@trmosala

What to build

Users can distinguish granted access, running operations, busy tabs, crashes and interrupted-input recovery, and take the appropriate action.

Acceptance criteria

  • Main publishes authoritative operation, failure and recovery state; granted access alone does not imply active or healthy automation.
  • Renderer crashes set a visible failure state; typed load and command errors retain their actual cause.
  • Interrupted-input quarantine is visible and offers safe close/reopen recovery without claiming reload or regrant repairs the same view.
  • Takeover/revoke stops further agent access and respects settlement of already-dispatched native work.
  • Controls, errors and recovery actions are localized and keyboard/screen-reader accessible; tests cover stale updates.

Blocked by

Context

Source: revised CM_Browser review and whole-tab Agent Access requirement, 2 October 2026. This is follow-up work to the previously completed bounded browser implementation; existing issues remain closed.

Preserve main-process ownership, explicit revocation, stale-target protection and isolation from unrelated tabs. Coordinate with ongoing browser changes and the separate Microsoft sign-in fix. Native validation must distinguish fixture results from actual authenticated-site evidence. Do not restart the installed app or server, modify real calendar events, or enter/change/submit timesheets.

Activity

  1. added
    enhancementNew feature or request
    ready-for-agentScoped work with acceptance criteria and recorded blockers
    on Oct 2, 2026
  2. trmosala commented on Oct 2, 2026

    @trmosala
    OwnerAuthor

    Completed work saved; closing at the user's request.

    Main publishes authoritative operation, failure, crash, quarantine and revision state. Localized controls allow takeover and close/reopen recovery; stale replies cannot erase newer state. Mounted and native outcome fixtures passed. New English fallback copy still requires translation review; platform accessibility qualification is not claimed.

    Local commit: 7f746e8fcb7d2ad819b107aac2c0d7d9462d1361 on branch browser-gaps. This commit has not been pushed, merged or released.

    Fresh checkpoint validation: 410 tests / 6,620 assertions pass; all five affected package typechecks and the browser plugin build pass; native navigation and leave-confirmation reruns pass; scoped lint has 0 errors and 356 style warnings; formatting and whitespace checks pass. Earlier native fixture results are documented in the committed cm-browser README. These checks do not qualify authenticated Teams, macOS or a packaged app.

    Native UI screenshot and validation archive. No installed app/server was restarted and no real account data was modified.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestready-for-agentScoped work with acceptance criteria and recorded blockers

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions