Skip to content

Install

  • macOS 14 or newer for the current Gateway app.
  • Google Chrome 116 or newer for the Chrome extension.
  • A terminal that can run the abg CLI.
  • For development builds: Xcode 16 or newer, mise, Node.js, and pnpm.

Install with Homebrew:

Terminal window
brew tap arcmanagement/agent-browser-gateway https://github.com/arcmanagement/agent-browser-gateway
brew trust --cask arcmanagement/agent-browser-gateway/agent-browser-gateway
brew install --cask agent-browser-gateway

If Homebrew prints Not upgrading agent-browser-gateway, the latest version is already installed, the cask is already installed. Verify it with brew info --cask agent-browser-gateway or abg --help; run brew reinstall --cask agent-browser-gateway only when you want to force a fresh cask install. Homebrew may also print trust warnings for unrelated taps; check the final install line and brew info --cask agent-browser-gateway to confirm the ABG cask state. If you previously tapped the temporary public Homebrew repository or the private source repository, run brew untap arcmanagement/agent-browser-gateway once and tap again with the explicit GitHub URL above.

You can also download the current DMG from the download page, verify its SHA-256 checksum, open the DMG, and run the installer.

Launch the app once so the menu bar icon appears. Then confirm the CLI can reach it:

Terminal window
abg status

If abg is not on your PATH, install it from the release artifact or use the Homebrew cask.

Install with WinGet after the current release’s microsoft/winget-pkgs PR is merged and indexed:

Terminal window
winget install --id ArcManagement.AgentBrowserGateway --source winget

Current v0.4.1 status: WinGet is not indexed yet, and no Windows release ZIP is published yet. If winget reports no matching package, that is expected until the signed Windows release and Microsoft indexing are complete.

For current Windows testing, clone the repository on Windows and run:

Terminal window
.\windows-build-install.cmd

Install Agent Browser Gateway from the Chrome Web Store for normal Chrome use. For local extension development, build the extension from the repository and load extension/dist/ as an unpacked extension.

For incognito windows, enable Allow in incognito on the extension details page. Chrome disables extension access to incognito windows by default.

After the Gateway and CLI are available, install or refresh the Claude Code and Codex skill guidance:

Terminal window
abg install-skill --target both

Use --target claude or --target codex when you only want one agent’s skill installed.

The development variant runs as a separate menu bar app on port 8766 and uses separate local state.

Terminal window
CONFIG=debug APP_VARIANT=dev ./build-app.sh
open "Agent Browser Gateway Dev.app"
ABG_PORT=8766 .build/debug/abg status

Production user plugins live under ~/.abg/plugins/. Development runs with ABG_PORT=8766 use ~/.abg-dev/plugins/, so local experiments do not mutate production plugin state.