1
No access by default
The agent sees no tabs until you explicitly share a tab or enable all-tabs mode for an isolated profile.
Local browser access for AI agents
Agent Browser Gateway
Share the tab you choose with an AI coding agent. Nothing else is visible by default, and every local operation is designed to stay inspectable.
Per-tab consent Loopback transport Token-efficient reads Zero telemetry Local audit log
Download Agent Browser Gateway.
The current public build is v0.4.1. Install the macOS app with Homebrew or the signed DMG below; both point at the same current release payload.
Published by ArcManagement, Inc. Public release artifacts are served from this site. Windows packaging is still pending while the signed setup workflow and WinGet submission are completed.
macOS DMG
Tap
arcmanagement/agent-browser-gateway, trust the cask when
Homebrew requires tap trust, then install with
brew install --cask agent-browser-gateway or run the signed DMG.
Windows WinGet / setup ZIP
Use
winget install --id ArcManagement.AgentBrowserGateway after
package indexing. The setup ZIP will be published on this site after the signed
Windows release workflow completes.
CLI ready Installs
abg and refreshes Claude Code and Codex skills. Chrome extension Install from the Chrome Web Store to share tabs with the local gateway.
macOS SHA-256 4d84561b88252f38592c847022101956b11172614cbb5338ad87e9be70cabafa
Windows SHA-256 Available after signed Windows release
macOS trust: verify the SHA-256 checksum before opening the DMG.
Extension: install Agent Browser Gateway from the Chrome Web Store.
Uninstall: remove the app from /Applications, delete
abg from your PATH if manually linked, and remove the Chrome extension.
Why ABG exists.
Browser access is powerful for AI agents because the real work often happens inside pages you are already logged into. That same power becomes risky when the bridge is opaque, global, or tied to a single hosted assistant.
If your AI can see your browser, you should be able to inspect the bridge it uses.
Less ambient access
No tab is shared until you choose it, and sharing is scoped to that tab.
Less platform lock-in
The CLI can be used by Codex, Claude Code, Cursor, Cline, or your own scripts.
Less hidden movement
ABG is local-first, avoids product telemetry, and records operations in a local audit log.
The browser remains human-owned.
ABG is built for the moment when you are already looking at the real page and want to hand selected local browser state to an agent workflow.
2
Per-tab by default
ABG keeps permission scoped to selected tabs unless you opt into all-tabs access for a sandbox profile.
3
Automatic revocation
Manual tab access is revoked when the tab closes, navigates to another origin, or you revoke it.
4
Visible operations
Write actions can require a local approval step before they run.
A small local bridge, not another browser cloud.
Agent Browser Gateway combines a Chrome extension, a macOS menu bar gateway, and
the abg CLI. The extension has no default host permissions, optional
all-tabs access is local opt-in, the gateway listens on 127.0.0.1, and
the product does not include analytics or telemetry.
A
Share from Chrome
You choose the active tab from the extension popup.
B
Use a local CLI
Your agent asks abg for reads, screenshots, console logs, tables, or operations.
C
Review the audit trail
Local operation records are written to a JSONL audit log on your Mac.
Cleaner browser context. Fewer wasted tokens.
Raw browser HTML is noisy: scripts, styles, framework wrappers, hidden UI, and unrelated app chrome all get mixed into the prompt. ABG can return clean Markdown from the shared tab, preserving useful structure while cutting out the page noise.
In a README benchmark on a typical article page, ABG's Markdown read reduced input from roughly 50,000 tokens of raw HTML to roughly 5,900 tokens while keeping headings, links, lists, and article structure.
Raw page HTML ~50k tokens
ABG Markdown ~5.9k tokens
Reduction vs naive full HTML ~88% less prompt noise, with structure preserved
Not a test runner. Not a hosted browser assistant.
ABG is for handing a human-owned, already-open tab to an agent workflow. Playwright remains the better fit when automation should own the whole browser lifecycle.
| Option | Best fit | Tradeoff | Where ABG differs |
|---|---|---|---|
| Agent Browser Gateway | AI-assisted work in a tab you are already using | Requires explicit local setup and tab sharing | Per-tab consent, local transport, CLI-first workflow, local audit log |
| Playwright | Deterministic E2E tests, CI, screenshots, clean browser profiles | Automation owns the browser session | ABG uses your everyday Chrome tab with your current login and context |
| Claude in Chrome | Provider-integrated browser assistance | Tied to that provider's product surface and data path | ABG is agent-agnostic and designed around local-first browser access |
| Browser MCP tools | MCP-native browser control and structured snapshots | Often targets a dedicated or broader browser context | ABG keeps the human's selected tab as the permission boundary |