What happened
Anomaly’s release notes describe OpenCode Browse v0.1.0 as a rewrite in Rust, published on November 16. The project packages its CLI, relay and MCP server in one native binary of a few megabytes, with no Node.js or Playwright underneath. The release notes say the relay idles at a few megabytes rather than hundreds. The Chrome Web Store extension continues to work with the rewritten binary.
The release separates the tools presented to different agent clients. OpenCode gets browser-specific tools such as navigate, snapshot, click, fill, screenshot, network and recording, which can be composed in code mode. Claude Code, Codex, Cursor and other MCP clients get an execute tool that runs JavaScript using a Playwright-style page, together with snapshot() and handoff(). They also get status and tabs tools. This is not simply one uniform browser API exposed to every agent: the project describes a direct tool set for OpenCode and a JavaScript execution interface for other MCP clients.
The release makes tabs, rather than sessions, the handle passed between browser operations. A navigate call opens a background tab and returns its ID; subsequent calls name that tab. Each agent sees its own tabs and tabs explicitly lent to it. The notes say OpenCode now runs one Browse instance per project rather than one per directory. The intended change is to make browser work easier to compose while keeping agents from automatically sharing all of one another’s browser state.
The installation command is npx @opencode/browse install. The v0.1.0 notes say setup supports OpenCode, Claude Code, Codex, Cursor, VS Code, Gemini CLI and 25 more agents. The installer includes a searchable picker that remembers the last choice, --agent <name> and -y options, and edits configurations while preserving comments and formatting. The same release lists fixes including fallback to another port if 19988 is occupied, stopping a cancelled tool call in Browse, and refusing unknown installer options rather than ignoring them.
Subsequent releases add operational details. Version 0.1.2, also published November 17, lets an agent assign an ID such as work-mail to a tab and reuse it; if that tab is gone, Browse opens it. A second call to a busy named tab returns an error instead of interleaving. Version 0.1.4 says running Browse instances check for updates at launch and hourly, with a differing version treated as an update so a rollback can reach users. Version 0.1.5 renames the extension OpenCode Browse in the Chrome Web Store and toolbar.
What the archive adds
New Runtime’s earlier coverage on November 13 described OpenCode subagents returning session IDs and continuing in the background by default. This release is a new event: it concerns the browser tooling those agents can use, including the Rust rewrite, client-specific interfaces and tab-based coordination.
Trend signal
This supports Harness architecture outlives model choice: OpenCode Browse gives several agent clients a browser capability through a shared runtime, rather than tying that capability to a single model family. The practical test is whether developers can carry the same browser workflow across clients while preserving useful boundaries around state and access.
Why now
The release sequence moved quickly: v0.1.0 appeared on November 16, followed by three releases on November 17 in the excerpted release history. That timing matters for teams evaluating adoption because the runtime rewrite and interface are new, while details such as update behavior and named-tab reuse were still changing across successive versions.
Why it matters
Browser agents need more than a model that can describe a page. They need a usable runtime, a way to address browser state across tool calls, and controls that prevent one agent from accidentally acting through another agent’s tabs. Browse’s shift to tab IDs makes the handoff explicit: a workflow can preserve a tab between calls, and clients can identify which tab they mean.
The split interfaces also offer a practical integration choice. OpenCode users can compose browser primitives directly, while other MCP clients can run JavaScript against a familiar page abstraction. The small native binary may reduce installation and idle-memory costs, though those figures are project-reported and not independently measured here. For teams, the key question is whether the convenience of a shared browser runtime fits their security model. In particular, the “own tabs and tabs you lend” boundary deserves testing against real workflows before agents receive access to sensitive accounts or data.
Limits and uncertainty
The release notes’ memory comparison is not accompanied by a benchmark methodology, workload, or independent measurement. They do not establish how browser-task reliability or speed compares with the previous implementation. The described separation of agent tabs is a project behavior claim; teams should verify it in their own multi-agent setups, including shared tabs and browser disconnects. The release history also does not establish how consistently each supported client’s configuration behaves across versions or operating systems. The available details describe the tool and installation path, but not a security audit or a broader assessment of the risks of running agent-directed JavaScript in a browser.
Skill to build now
Take one low-risk browser task and test it with the client your team actually uses. In OpenCode, inspect the navigate → returned tab ID → snapshot flow; with an MCP client, test execute and its page interface. Then try a second agent against a separate tab and confirm it cannot act on the first agent’s tab unless that tab is deliberately shared. This checks the release’s core workflow and access boundary before a wider rollout.
Reader takeaway
OpenCode Browse’s Rust rewrite is more than a packaging change: it provides client-specific browser tools and makes tabs the explicit handle for agent work. If you rely on browser-enabled agents, evaluate the new interface and verify tab isolation in a small, non-sensitive workflow before migrating production tasks.