BeatAPI/BeatBrowser

English · 简体中文
Your Chrome. Now an agent browser.
No browser switch. No login migration. Your choice of agent.
Connect Codex, Claude Code and other compatible agents directly to the Chrome you already use. Keep your website logins, run tasks in background windows, and take over when needed. BeatBrowser is a free, MIT-licensed Chrome extension and local bridge.
Get started · Cloud agents · Examples · Compare · JavaScript SDK · Website
Normal local browser tools are free, with no BeatBrowser account or API key. Your agent uses its own model access.
## Why BeatBrowser
| Why choose BeatBrowser | What you get |
| Keep Chrome | Use your existing browser and profile. |
| Keep your logins | No cookie export or profile migration. |
| Choose your agent | Codex, Claude Code, WorkBuddy and more. |
| Own the toolchain | Extension, bridge, MCP, CLI and SDK source. |
| Work in the background | Task windows with pause and takeover. |
| Cloud access preview | Self-hosted access to your local Chrome. |
The extension, local bridge, MCP server, CLI and Node SDK are public under MIT. Task windows share their Chrome profile's cookies and storage.
## Choose your mode
| Mode | Agent location | Setup |
| Local Agent | Your computer | Tools + extension; no domain or tunnel. |
| Cloud Agent | Remote / cloud | Tools + extension + credential + your own tunnel. |
Local mode is the default; installation does not enable remote access. Both modes
use your computer's Chrome. Version 1.4.1 includes the optional cloud adapter as a preview. Cloud Agent setup
### Bring the agent you use
| Mode | Agent examples |
| Local | Codex, Claude Code, WorkBuddy, OpenCode, Kimi Code |
| Cloud | Muse, Grok Bot, OpenClaw, Hermes |
OpenClaw and Hermes are shown here as cloud deployment examples; they also work
in Local Agent mode when their tools run on your computer.
More agents, configuration details and verification status are listed in the
Agent directory.
## Quick start
For Local Agent mode: Node.js 20+, Chrome 116+, and a client that can launch a local stdio MCP server. Setup has two parts: the local tools and the Chrome extension.
### 1. Install the local tools
sh
npm install --global @beatapi/beat-browser@1.4.1
beat-browser install --dry-run
beat-browser install
beat-browser extension
--dry-run previews detected client configuration changes. The installer backs up changed configurations; keep the installation so the extension folder stays at a stable path.
### 2. Load the Chrome extension
1. In the Chrome profile you want to use, open chrome://extensions and enable Developer mode.
2. Choose Load unpacked and select the folder printed by beat-browser extension. Load one copy per profile.
3. Restart your agent client and check the connection:
sh
beat-browser doctor --json
Ready means ok: true and extensionOnline: true. The extension is currently loaded unpacked, rather than installed from the Chrome Web Store.
Matching downloads and source setup · Agent installation guide · Release notes
Let your agent guide setup
Paste this into your agent:
text
Set up BeatBrowser from https://github.com/BeatAPI/BeatBrowser.
Read AGENTINSTALL.md, preview configuration changes, then guide me through