Skip to content

Releases: dbalders/agent-browser-extension

agent-browser-extension 0.1.0 — Developer preview

Choose a tag to compare

@dbalders dbalders released this 04 Oct 05:29

agent-browser-extension is an independent Chrome extension and local browser bridge maintained by David Balderston. It gives MCP-compatible agents and HTTP clients controlled access to Chrome on the user's computer.

This is the first public developer preview, with a fresh root commit and Apache-2.0 licensing.

Download and setup

Download agent-browser-extension-0.1.0-source.tar.gz, verify it with SHA256SUMS, and extract it. In the extracted directory:

npm ci
npm run build
node dist/cli.js serve

Keep the bridge running. In a second terminal, run node dist/cli.js pair and node dist/cli.js setup. In chrome://extensions, enable Developer mode and load dist/extension unpacked. Pair the extension and add the generated MCP configuration to your agent.

Requires Chrome 125+ and Node 22.12+ on the supported 22.x, 24.x or 26+ lines. The default private connection directory is ~/.agent-browser-extension; use AGENT_BROWSER_HOME or --home to customize it. Earlier development builds may need fresh pairing.

Verification

All six hosted CI jobs passed for commit 3a48f7551e2371e1752fa28d9714d061574b3cb3: Node 22/24/26 on Linux, Node 24 on macOS and Windows, plus isolated Linux Chromium and clean source-archive installation. The behavioral suite has 295 tests. A separate isolated Chrome for Testing 148 run passed on macOS. Gitleaks found no secrets in the complete published history, and the npm audit found no known vulnerabilities at release preparation.

The 72-file source manifest matches that exact commit. The assets exclude credentials, browser profiles, dependencies, generated builds, private test evidence and development history. Scanner results are bounded checks, not guarantees of security.

Scope and support

The release includes 39 browser tools, ask-first website access, separate debugging grants, task ownership, Stop controls and cleanup that preserves existing user tabs and retained results.

This is a source release, not a Chrome Web Store listing or npm package. Setup and updates are manual. Chrome and the bridge must run on the same computer. CPU profiling is browser-dependent; unsupported builds return PROFILE_UNAVAILABLE. Test fixtures do not establish compatibility with every website, browser policy, agent application or model provider.