You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Browser tools leak into child sessions, so explore gets every browser tool #63690
When the desktop browser is attached to a session, subagents started from that session are sent all ~45 browser tools, including the read-only explore agent.
The grant is written to the parent's session.permissions (browser: allow). Session.create copies the parent's permissions to children, and session rules are merged after the agent's rules, so the allow beats explore's * deny. explore has no Code Mode (execute is denied), so Tool.snapshot sends the browser tools as direct tools.
None of them can work in the child: BrowserConnection.target looks up the attachment by the child's session ID, which never has one, so every call returns [browser.disconnected]. The grant also stays on the child after the parent detaches, because the revoke only rewrites the attached session.
I noticed it because the extra schemas broke the subagent entirely: browser_click.count is { "type": "number", "enum": [1, 2] }, which the gateway I use rejects with 400 ... does not accept JSON Schema keyword(s): enum. The main session was fine since there the browser tools are inside execute.
Thanks for the detailed analysis. I think this is a duplicate of #61238. It has the same root cause: attaching the desktop browser adds allow rules to the session's permissions, a child session copies its parent's permissions when none are passed (permissions: input.permissions ?? parent?.permissions in packages/core/src/session.ts), and the attachment exists only for the parent's session ID. So subagents see the browser.* tools, but every call fails with [browser.disconnected]. That issue has already been reproduced.
Possible duplicates and related issues, ordered by likelihood:
I'm closing this issue now as a duplicate of #61238. Please add your extra findings there: that it reaches explore, where the tools are sent directly rather than through execute; that the enum in the browser_click.count schema makes your gateway reject the subagent's request with a 400; and that the copied grant stays on the child after detaching. They're useful for whoever fixes it. If you think this is a different problem, reply here and the issue will reopen.
Activity
opencodejr commentedon Nov 13, 2026
Thanks for the detailed analysis. I think this is a duplicate of #61238. It has the same root cause: attaching the desktop browser adds allow rules to the session's permissions, a child session copies its parent's permissions when none are passed (
permissions: input.permissions ?? parent?.permissionsinpackages/core/src/session.ts), and the attachment exists only for the parent's session ID. So subagents see thebrowser.*tools, but every call fails with[browser.disconnected]. That issue has already been reproduced.Possible duplicates and related issues, ordered by likelihood:
execute. Related, but a different path.I'm closing this issue now as a duplicate of #61238. Please add your extra findings there: that it reaches
explore, where the tools are sent directly rather than throughexecute; that theenumin thebrowser_click.countschema makes your gateway reject the subagent's request with a 400; and that the copied grant stays on the child after detaching. They're useful for whoever fixes it. If you think this is a different problem, reply here and the issue will reopen.