Browse

Let your AI agents use your real browser: your tabs, your logins, your extensions. An MCP server and a Chromium extension, for opencode and any other MCP client.

Agents get a browse MCP server. They open and drive tabs with Playwright, take screenshots, capture network traffic and record the screen, in background tabs grouped out of your way. When it's your turn (a login, a 2FA prompt, a payment), they hand the tab back to you and continue once you click Continue.

It works in Chrome, Edge, Brave, Arc, Helium, Vivaldi, Opera and Chromium.

Install

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

On Windows, run irm https://opencode.ai/browse/install.ps1 | iex in PowerShell. With Node.js, npx @opencode/browse install works too: it installs the package globally so agents run browse from PATH. The installer puts the browse command in ~/.local/bin ($XDG_BIN_HOME when set) and runs browse install. It reads the channel's manifest from Anomaly's release service, downloads the binary for this computer, and verifies its size and SHA-256 before installing it. --channel stable|beta|dev picks the channel (stable by default); --version <version> installs a specific version from npm, checked against npm's published SHA-512 integrity.

install keeps its files in the XDG folders (~/.config/browse, ~/.local/share/browse, ~/.local/state/browse and ~/.cache/browse; each honours its XDG_* variable), adds the browse MCP server to the agents you choose, and connects the extension:

1. Choose your agents. Detected agents start checked. Type to filter, use ↑/↓ to move, Space to toggle and Enter to confirm. You can uncheck OpenCode, choose an agent you haven't installed yet, or choose none for CLI-only use. Your next interactive install starts with your last selection.
2. Add the extension. install opens browse in the Chrome Web Store; add it to your browser, and install pairs it once it's there. If it's already there, install opens its setup page with a one-time pairing code, so it pairs without copying anything.

That's it. Ask an agent to "open news.ycombinator.com and tell me the top story". Or paste this into opencode: "Install browse with npx @opencode/browse install."

Requirements: a Chromium browser, and opencode or another MCP client. The npx install also needs Node.js 22.19+.

Updates are automatic. A binary install reads its channel's manifest from Anomaly's release service at launch and at least once an hour; an npm install checks npm's dist-tag once an hour. When the current release is a different build, the relay reruns whatever installed browse in the background: a binary install reruns the install script that shipped with the browse version it's running (not one downloaded at update time), which checks the file's size and SHA-256 and replaces ~/.local/bin/browse; an npm install runs npm install -g @opencode/browse@<version>. It restarts the relay when no agent is using the browser, without changing opencode's config. Running MCP servers swap to the new build between tool calls. Choose Only tell me or Don't check under Updates on the extension's settings page (or settings set autoUpdate=notify, or OPENCODE_BROWSER_AUTO_UPDATE=off). Agents can read the current value from status, but the MCP settings tool can't read or change update behaviour; it stays with you. browse update updates now; to go back, rerun the installer with --channel <channel> (binary installs follow the channel) or --version <version> / `npm install -g @opencode/bro

... View full README on GitHub