On 2026-11-07 the official OpenCode account announced Browse: an MCP server plus Chromium extension that lets agents drive your local real browser with existing tabs, logins, and extensions. Sensitive steps such as login, 2FA, or payment hand the tab back until you click Continue. It works with Chrome, Edge, Brave, Arc and other Chromium browsers, and with MCP clients including OpenCode, Claude Code, Cursor, Codex, and Zed. Source is MIT at anomalyco/browse; the npm package is @opencode/browse.
Key Takeaways
- ✓Shape: MCP server + Chromium extension; agents drive Playwright tabs in collapsed background groups, with screenshots, recordings, and HAR capture
- ✓Compatibility: browsers include Chrome, Edge, Brave, Arc, Helium, Vivaldi, Opera, Chromium; MCP clients include OpenCode, Claude Code, Cursor, Codex, Zed, and more
- ✓Safety UX: login, 2FA, and payment steps can hand off to the user; sessions support site allowlists; OpenCode published no standalone benchmark
- ✓Install: prefer the Chrome Web Store extension, or
npx @opencode/browse install/curl -fsSL https://opencode.ai/browse/install | bash(Node.js 22.19+) - ✓Source: as of write time the official post had about 3,305 likes, 190 reposts, and ~135K impressions; GitHub anomalyco/browse had about 108 stars (MIT)
Key Decision Metrics at a Glance
Heavy Claude Code use: compare subscription limits and API bills
Compare 40 dev plans & simulate token costs vs $20/mo subscriptions
Project Links & Resources
Direct AccessIn-Depth Technical Analysis
Core Background & Industry Pain Points
Coding agents that check pages, fill forms, or read dashboards often spin up a clean browser, losing logins, extensions, and cookies. Cloud browsers move the session off the machine. Developers want the agent to use the signed-in browser they already have, while returning control for 2FA and payments.
Architecture Highlights & Internals
Browse pairs an MCP server with a Chromium extension. Agents send commands over MCP; the extension drives Playwright tabs in collapsed background groups, with screenshots, recordings, and HAR capture. On login, 2FA, or payment, it hands the tab back until the user clicks Continue. Users can also lend an open tab to the agent. Sessions can use a site allowlist.
Authoritative Benchmarks & Measured Scores
This is a tooling launch. The product page and GitHub publish no success-rate benchmarks. Verifiable facts: Chromium-family browser support, multiple MCP clients, npm package @opencode/browse currently at 0.0.14, and an MIT license. Community privacy scores are not official and are not cited here.
Developer Hands-on Guide
Install the Chrome Web Store extension first and follow its pairing flow, or run npx @opencode/browse install / the official install script (Node.js 22.19+). Then call browse from OpenCode, Claude Code, Cursor, Codex, Zed, or another MCP client. For production, enable allowlists, isolate sensitive sites, and prefer a separate browser profile to reduce prompt-injection and mis-click risk.
Benchmark side-by-side against alternatives, or calculate monthly token cost vs subscription break-even.
Discussion & Comments
0Sign in to join the discussion
Connect with AI developers to exchange benchmark insights.