code mode: desktop-only browser tools exposed in web sessions

Summary

Code Mode advertises the tools.browser.* namespace in a web session even though those tools require an OpenCode desktop-app browser connection. Invoking an advertised browser tool fails with setup instructions that cannot be completed from the web client.

Environment

• opencode version: v0.0.0-beta-19296
• OS: Darwin 25.6.0, arm64
• Terminal: Ghostty; TERM=xterm-256color; COLORTERM=truecolor
• Shell: /bin/zsh
• Install/channel: beta
• Active plugins: local opencode-gpt-imagegen plugin and opencode-chatgpt-websearch

Reproduction

1. Start and use an OpenCode web session.
2. Observe that the Code Mode catalog includes tools.browser.tabs.list() and other tools.browser.* operations.
3. Invoke tools.browser.tabs.list() through Code Mode.
4. Observe the browser.disconnected failure instructing the user to open the session in the desktop app and enable an experimental browser setting.

Expected Behavior

Desktop-only browser tools should not be advertised in web sessions that cannot satisfy their connection requirements. Alternatively, the web client should provide a supported setup flow and documented configuration instructions.

Actual Behavior

The tools are advertised as available, but invocation fails consistently with:

[browser.disconnected] No desktop browser is connected to this session. Open this session in the desktop app, enable the experimental browser setting, and wait for it to connect. Then call browser.tabs.list({}). Repeating browser actions while disconnected will not help.

Additional Context

No browser integration is configured in the user's opencode.jsonc, and the current OpenCode V2 documentation has no browser-integration setup page or documented configuration field. The separately installed browser-control CLI works, but it uses a different relay/extension path and does not make the advertised Code Mode browser namespace usable.

This is primarily a capability-discovery and UX issue: the model sees the browser tools as callable and may choose them over a working CLI workflow, while the user has no way to satisfy the tool's requirements from the web client.