Agent Browser Gateway

Tracking since May 5, 2026.

Changelog

• Jun 4, 2026
  description

  Control Chrome with Codex & Claude Code
  
  Agent Browser Gateway lets you share the Chrome tab you choose with a local AI coding agent.
  
  It is built for browser-assisted development and support workflows where the human keeps control of the browser session. No tab is visible to an agent by default. You explicitly share one tab from the extension popup, and the local `abg` CLI can then inspect, screenshot, read console or network context, and perform approved operations in that shared tab.
  
  What ABG can do:
  - Share only the tab you explicitly authorize
  - Read page content as text, Markdown, HTML, or JSON
  - Capture screenshots and PDFs
  - Inspect console logs, network activity, tables, and interactive elements
  - Click, fill, paste, scroll, upload files, press keys, and wait for page state
  - Record and replay local browser workflows
  - Use local plugins for site-specific commands and transforms
  - Optionally run advanced JavaScript evaluation only when enabled, explicitly approved, and shown locally before execution
  
  Privacy and control:
  - No account is required
  - No cloud relay is used by ABG
  - No analytics, advertising identifiers, or product telemetry
  - No default access to all tabs
  - Shared tabs can be revoked by the user
  - Operations are written to a local audit log
  - Write actions can require local approval before they run
  
  ABG requires the local Agent Browser Gateway app and CLI. The extension connects Chrome to that local gateway so agents can work with the specific browser tab you choose, using your current login and browser context without handing over the whole browser.

  Control Chrome with Codex, Claude Code, and more
  
  Agent Browser Gateway lets local AI coding agents work with your Chrome session while keeping browser access explicit, local, and under your control.
  
  By default, no tab is visible to an agent. You choose a tab from the extension popup, share it intentionally, and the local abg CLI can then read page context, capture screenshots, inspect console and network activity, and perform approved actions in that shared tab.
  
  For dedicated sandbox profiles, test machines, or disposable Chrome profiles, ABG also supports optional all-tabs mode. When enabled, Chrome asks for explicit permission to access all sites in that profile. This mode is off by default, can be revoked from the popup, and is intended only for environments where every open tab is deliberate agent context.
  
  ABG can:
  
  Share only the tab you explicitly authorize by default
  Read page content as text, Markdown, HTML, or JSON
  Capture screenshots and PDFs
  Inspect frames, dialogs, downloads, console logs, network activity, HAR files, cookies, and Web Storage
  Click, fill, paste, scroll, upload files, press keys, and wait for page state
  Inspect framework signals such as React trees and Web Vitals where available
  Record and replay local browser workflows
  Use local plugins for site-specific commands and transforms
  Run advanced JavaScript evaluation only when eval is enabled by the user. By default, each eval requires explicit approval and a local approval window showing the script; Trusted automation / AutoMode can skip that popup only for already-shared tabs and still writes audit logs.
  Use sandbox-only browser controls in isolated all-tabs profiles
  
  Privacy and control:
  
  No account required
  No ABG-operated cloud relay
  Extension-to-gateway communication stays on the local machine
  No analytics, advertising identifiers, or product telemetry
  No default access to all tabs
  Optional all-tabs access requires a local toggle and Chrome permission prompt
  Shared tabs and all-tabs mode can be revoked by the user
  Operations are written to a local audit log
  Write actions can require local approval before they run
  
  ABG requires the local Agent Browser Gateway app and CLI. The extension connects Chrome to that local gateway so Codex, Claude Code, and other local coding agents can use the browser context you choose, including your current login and browser state, without handing over the whole browser by default.

• Jun 4, 2026
  short_description

  Share specific Chrome tabs with AI coding agents via per-tab explicit permission.

  Share Chrome tabs with AI coding agents via explicit local permission.

• Jun 4, 2026
  permissions

  activeTab, scripting, tabs, storage, debugger, alarms, clipboardWrite

  activeTab, scripting, tabs, storage, debugger, downloads, alarms, clipboardWrite

• May 28, 2026
  description

  Agent Browser Gateway lets you share the Chrome tab you choose with a local AI coding agent.
  
  It is built for browser-assisted development and support workflows where the human should keep control of the browser session. No tab is visible by default. You explicitly share one tab from the extension popup, and the local abg CLI can then read, screenshot, inspect console or network context, or perform approved operations in that shared tab.
  
  Core principles:
  - Per-tab consent instead of broad browser access
  - No host permissions in the extension manifest
  - Local gateway over loopback transport
  - Agent-agnostic CLI for Codex, Claude Code, Cursor, Cline, and scripts
  - Token-efficient Markdown reads that reduce noisy HTML before it reaches an agent
  - Local audit log for inspectable operations
  - No analytics, advertising identifiers, or product telemetry
  
  ABG is not an end-to-end test runner and does not try to replace Playwright. Playwright is the right tool when automation owns the browser lifecycle. ABG is for the tab you are already using, with your current login and context, when you want to hand only that tab to an AI agent workflow.

  Control Chrome with Codex & Claude Code
  
  Agent Browser Gateway lets you share the Chrome tab you choose with a local AI coding agent.
  
  It is built for browser-assisted development and support workflows where the human keeps control of the browser session. No tab is visible to an agent by default. You explicitly share one tab from the extension popup, and the local `abg` CLI can then inspect, screenshot, read console or network context, and perform approved operations in that shared tab.
  
  What ABG can do:
  - Share only the tab you explicitly authorize
  - Read page content as text, Markdown, HTML, or JSON
  - Capture screenshots and PDFs
  - Inspect console logs, network activity, tables, and interactive elements
  - Click, fill, paste, scroll, upload files, press keys, and wait for page state
  - Record and replay local browser workflows
  - Use local plugins for site-specific commands and transforms
  - Optionally run advanced JavaScript evaluation only when enabled, explicitly approved, and shown locally before execution
  
  Privacy and control:
  - No account is required
  - No cloud relay is used by ABG
  - No analytics, advertising identifiers, or product telemetry
  - No default access to all tabs
  - Shared tabs can be revoked by the user
  - Operations are written to a local audit log
  - Write actions can require local approval before they run
  
  ABG requires the local Agent Browser Gateway app and CLI. The extension connects Chrome to that local gateway so agents can work with the specific browser tab you choose, using your current login and browser context without handing over the whole browser.

• May 10, 2026
  permissions

  activeTab, scripting, tabs, storage, debugger, alarms

  activeTab, scripting, tabs, storage, debugger, alarms, clipboardWrite

Permissions & access

Permissions

activeTabscriptingtabsstoragedebuggerdownloadsalarmsclipboardWrite

Host access

None declared

Screenshots