Skip to content

Add user-tab consent and per-session agent tab ownership #2622

Description

@iFredOS

Two ergonomics items from running agents against the BrowserOS server, observed 2026-08-29 from Farfadet (a downstream build). Both are things a sidecar cannot fix on its own.

1. A consent path for user tabs

Observed: page 13 is not owned by this agent, twelve times in one session,
for tabs the user had explicitly pointed at.

Why it matters: the guard is right to exist, but it has no way to represent
consent - while the CDP port beneath it answers any local process with no
credential at all. The lock is on the wrong door.

Asked for: a way for the user to grant an agent access to a named tab, so
that pointing at a tab and being refused stops being the default experience.

Workaround until then: open the URL in our own tab with tabs action="new"
and work on that copy, leaving the user's original untouched.

2. Per-session tab ownership

Observed: ownership separates Claude Code from the user, not agents from
each other. Sibling agents close each other's tabs. A pre-filled issue form was
closed within minutes, twice.

Asked for: ownership keyed to the session, not the client.

Workaround until then: name the session early (name_session) so tabs group
under <client>/<name>, and never close a tab this session did not open.

Activity

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions