Skip to content

fix(browser): distinguish dispatched actions from failed observations #38

Closed

Description

@trmosala

What to build

An agent can tell whether input was dispatched when navigation or a failed snapshot interrupts the response.

Acceptance criteria

  • Tool results distinguish not-dispatched, dispatched with refreshed observation, and dispatched with uncertain outcome.
  • Navigation, cancellation or observation failure after dispatch preserves dispatch status and never triggers automatic action replay.
  • The agent receives an explicit safe recovery instruction to observe current state before deciding on further input.
  • Failures retain typed causes with localized user-facing descriptions.
  • Regression coverage includes a calendar-like click that succeeds while follow-up observation fails, plus cancellation before and after dispatch.

Blocked by

None - can start immediately.

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
    bugSomething isn't working
    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.

    Results distinguish not-dispatched, dispatched-observed and dispatched-uncertain outcomes. Observation failure preserves dispatch status and instructs a fresh read, without automatic action replay. Native action-outcomes and cancellation coverage passed.

    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

    bugSomething isn't workingready-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