cd /news/ai-agents/opencode-s-browse-0-1-0-rewrites-in-… · home › topics › ai-agents › article
[ARTICLE · art-170773] src=alphasignal.ai ↗ pub= topic=ai-agents verified=true sentiment=↑ positive

OpenCode's Browse 0.1.0 Rewrites in Rust, Slashing Memory Use by 25x

OpenCode released Browse 0.1.0, a Rust rewrite of its agent-to-browser bridge that the company reports uses 25x less memory, produces a binary 23x smaller, and removes Playwright as a runtime dependency. Browse 0.1.0 consists of an MCP server and a Chromium extension that lets agents drive a developer's real logged-in Chromium profile, with a handoff flow that pauses the agent for logins, two-factor authentication, and payments and resumes when the user selects Continue. The release works with MCP clients including Claude Code, Cursor, Codex, and Zed, and constrains browser control below the prompt layer by rejecting page.bringToFront and closing idle tabs after 10 minutes.

read4 min views2 publishedNov 16, 2026
OpenCode's Browse 0.1.0 Rewrites in Rust, Slashing Memory Use by 25x
Image: Alphasignal (auto-discovered)

A Rust rewrite shrinks the agent-to-browser bridge by 23x and 25x on memory, dropping Playwright as a runtime dependency.

  • OpenCode Browse 0.1.0 ships as a Rust rewrite of its agent browser bridge.
  • 25x less memory, 23x smaller binary, and Playwright removed as a runtime dependency.
  • Agents drive your real Chromium profile over MCP, inheriting logins and extensions.
  • Handoff flow s the agent for 2FA, logins, or payments, then resumes on Continue.
  • Works with Claude Code, Cursor, Codex, Zed and any MCP client; source on GitHub .
  • Allowlists, background tab groups, and blocked focus stealing keep agent tabs out of the way.

OpenCode has released Browse 0.1.0, a Rust rewrite of the bridge that lets coding agents operate tabs in a logged-in Chromium profile. OpenCode reports that the release uses one twenty-fifth of the memory, produces a binary one twenty-third the previous size, and removes Playwright as a runtime dependency. The smaller footprint makes Browse cheaper to keep running throughout a coding session.

Change Practical effect
Rust implementation Replaces the Node.js side process used for browser operations
25x lower memory use Reduces background resource consumption
23x smaller binary Cuts download and disk overhead
No Playwright runtime dependency Simplifies installation and removes a large npm dependency tree

Browse consists of an MCP server and a Chromium extension. MCP, or Model Context Protocol, gives compatible agent clients a standard way to discover and call tools. The extension connects those tools to the browser profile already holding the developer’s tabs, cookies, logins, and extensions.

Rust removes the sidecar #

Earlier Browse releases used a Node.js HTTP bridge because Playwright could not run natively under Bun. That bridge managed Chromium operations and required Browse to ship a Node toolchain, Playwright, and its npm dependencies alongside the agent integration.

The Rust server now implements browser operations and publishes them as MCP tools. Calls no longer pass through the separate Node process, reducing the number of runtimes involved in each request and eliminating Playwright from the installation.

State stays with the page #

Reliable browser automation depends on current page state. Screenshots can become stale as interfaces load, dialogs appear, or navigation completes. Browse keeps the agent connected to the live tab and supports an execute path that can combine several page operations in one script, avoiding long chains of individual tool calls.

  • Supports Chrome, Edge, Brave, Arc, Helium, Vivaldi, Opera, and Chromium.
  • Opens agent-controlled tabs in collapsed background tab groups.
  • Lets a user hand an existing tab to an agent from the extension toolbar.
  • Returns a tab to the user for logins, two-factor authentication, payments, and other manual steps, then resumes after the user selects Continue.
  • Captures screenshots, screen recordings, and HTTP Archive files, commonly called HAR files.
  • Restricts sessions to specified sites through allowlists.
  • Works with MCP clients including Claude Code, Cursor, Codex, and Zed.

Guardrails live in the protocol #

Browser control is constrained below the prompt layer. The protocol rejects page.bringToFront, preventing an agent-controlled tab from taking focus or raising a window over the user’s work. Idle tabs close after 10 minutes, with active scripts exempt from the timeout.

A visited page can still contain prompt-injection text designed to redirect an agent or abuse the permissions available through an authenticated session. A separate Chromium profile and a site allowlist limit the accounts and domains exposed during a run.

The OPENCODE_BROWSER_ALLOW_NODE setting requires additional care because it gives execute full Node.js access. Workflows that do not require local system access should leave it disabled. Browse also uses Patchright-style techniques to reduce common automation signals, though sites with stronger bot detection can still identify or block automated activity.

Install through the extension or CLI #

The recommended setup starts with the Chrome Web Store extension, which guides users through the remaining configuration. Direct CLI installation is available through the following options.

macOS and Linux

curl -fsSL https://opencode.ai/browse/install | bash

Windows PowerShell

irm https://opencode.ai/browse/install.ps1 | iex

npm

npm install -g @opencode/browse && browse install

Bun

bun add -g @opencode/browse && browse install

The open-source code is available in the project’s repository.

Authenticated workflows are the target #

Browse suits tasks that depend on an existing identity or browser configuration. Examples include querying an internal dashboard, filing an issue in Linear or Jira, reproducing a staging bug behind single sign-on, collecting a HAR file from an intermittent failure, and inspecting a site that blocks conventional headless browsers. Existing session cookies remove the need to give the agent raw credentials or create a service account for a short task.

Disposable browser profiles remain better suited to untrusted sites, repeatable test environments, and automation that requires strict isolation. Browse trades some of that isolation for access to an established session, so the chosen Chromium profile should contain only the accounts, extensions, and data required for the work.

The Rust rewrite lowers the operating cost of that tradeoff. Developers can keep the bridge available during routine coding work with a smaller binary, substantially lower reported memory use, and fewer runtime dependencies.

── more in #ai-agents 4 stories · sorted by recency
── more on @opencode 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/opencode-s-browse-0-…] indexed:0 read:4min 2026-11-16 · —