Skip to content
Conduit

skill

agent-chrome-bridge

Let your agents and bots control your chrome!

makriman/agent-chrome-bridgecommunitylistedunreviewed
Use skill

Set up

Skills are installed by placing their folder where your agent loads skills.

Download ZIP from GitHub Open the repository

The download comes from github.com/makriman/agent-chrome-bridge itself, not from our server, so what you get is exactly what its author published.

Install instructions come from the README

Skills do not use an MCP config. Follow the steps in the README below.

README

synced Oct 25, 2026

Agent Chrome Bridge

Give Grok Bot and other agents your Chrome.

Local-only, user-armed Chrome control. Your session stays in your browser. Agents get the tab you arm — not a datacenter Chrome that Cloudflare already blocked.

Canonical repository: github.com/makriman/Agent-Chrome-Bridge.

Mission

Cloud Chrome is not user Chrome.

Agents running in datacenters, CI, or hosted browser farms hit Cloudflare Verify you are human, Access denied, and other bot-score walls that a signed-in personal Chrome tab does not. Exporting cookies, standing up a remote relay, or launching another headless farm does not fix that. Those approaches also ask the user to give up the session.

Agent Chrome Bridge keeps authentication in the user's Chrome profile. The user signs in normally, arms one tab, and lets Grok Bot or another local agent inspect and operate only that tab through a loopback control plane.

Shopify Partners is example proof of the same class of gate — not the product itself. Partner org IDs, Dev Dashboard IDs, and Polaris admin surfaces sit behind human-only challenges that datacenter Chrome fails. This repository exists so agents can work those pages in the user's real Chrome.

What This Repository Contains

A Chrome extension plus a Node bridge on 127.0.0.1. Arm a tab. Inspect, click, type, scroll, screenshot, and run workflows against that tab.

This tree is local-only. There is no remote relay and no MCP server here.

Highlights

  • Give Grok Bot and other agents your Chrome — one armed tab, credentials stay in Chrome.
  • Inspect pages, click by ref, type, scroll, navigate, and capture screenshots.
  • Run scripted workflows with dry-run and resume support.
  • Local loopback only. The user arms the tab. The user can stop it.

Compatibility

The GitHub repo is Agent-Chrome-Bridge. Older codex-chrome-bridge clone URLs redirect here. Keep that old name only for env vars, wire headers, and existing local checkout folders — not as the public repo slug.

SurfaceNameNotes
GitHub repomakriman/Agent-Chrome-BridgeCanonical slug (casing exact)
npm namecodex-chrome-bridgePackage alias only; display name is Agent Chrome Bridge
Extension message sourcecodex-chrome-bridgeWire compat; do not rename
Auth headerx-codex-bridge-tokenWire header; do not rename
Listen port envCODEX_CHROME_BRIDGE_PORTOptional alias: AGENT_CHROME_BRIDGE_PORT
Bridge URL envCODEX_CHROME_BRIDGE_URLDefault http://127.0.0.1:18474
Approval envCODEX_CHROME_BRIDGE_APPROVEWorkflow runner only

Existing ~/codex-chrome-bridge checkouts and CODEX_CHROME_BRIDGE_* scripts remain valid.

Tech Stack

  • Vanilla JavaScript Chrome extension
  • Node.js ESM bridge server
  • Local HTTP control API on 127.0.0.1
  • Workflow scripts for repeatable browser tasks

Getting Started

npm install
npm run bridge
node bridge/control.mjs doctor

Load extension/ in chrome://extensions (Developer mode → Load unpacked). Open the target site in Chrome, then click Arm tab in the popup.

Optional port alias:

AGENT_CHROME_BRIDGE_PORT=18474 npm run bridge

CODEX_CHROME_BRIDGE_PORT continues to work. If both are set, AGENT_CHROME_BRIDGE_PORT wins.

Quality Checks

npm run check

Repository Notes

  • Do not commit generated tokens, screenshots, or zip artifacts.
  • The extension should only be loaded from a trusted local checkout.
  • Pack the extension with npm run zip (writes dist/agent-chrome-bridge-extension.zip).

Contributing

Contributions are welcome. The best contributions are specific, tested, and grounded in the product mission. Good places to help include documentation, accessibility, tests, bug reports, UI polish, data validation, and safer agent behavior.

Read CONTRIBUTING.md before opening a pull request.

Security

Please do not open public issues for secrets, auth bypasses, data exposure, provider key leaks, or abuse vectors. Follow SECURITY.md.

Code of Conduct

This project follows CODE_OF_CONDUCT.md. Be direct, kind, and useful.

License

MIT. See LICENSE.

↑↓ navigate openesc close