Agent Chrome gives coding agents one dedicated, persistent Chrome browser that they can control through the Chrome DevTools Protocol (CDP). Your regular Chrome stays separate and does not need remote debugging enabled.
- Reuses one Agent-only browser instead of launching disposable copies.
- Preserves logins, Cookies, Local Storage, and IndexedDB between sessions.
- Copies the selected regular Chrome profile only once, then keeps the two profiles independent.
- Binds remote debugging to the loopback interface on a fixed port (
9223). - Uses only Node.js built-ins; Puppeteer and other runtime dependencies are not required.
- Keeps per-tab CDP sessions alive through authenticated local daemons, reducing repeated Chrome authorization prompts.
- Google Chrome or Chromium
- Node.js 22 or newer
- macOS, Windows, or Linux
Clone the repository into the shared Agent Skills directory:
mkdir -p ~/.agents/skills
git clone https://github.com/wayhome/agent-chrome.git ~/.agents/skills/agent-chromeThen ask your agent to use $agent-chrome, or run the CLI directly:
~/.agents/skills/agent-chrome/scripts/cdp.mjs list
~/.agents/skills/agent-chrome/scripts/cdp.mjs open https://example.comThe first command creates the permanent Agent Chrome profile and starts the browser. Later commands reuse the same browser and profile.
Read Installation for other skill locations, upgrades, configuration, and uninstall behavior. Read User guide for all commands and the security model.
Agent Chrome operates locally. Browser profiles, Cookies, page contents,
screenshots, runtime tokens, and browsing data are not part of this repository
and are excluded by .gitignore.
The initial local profile copy deliberately excludes browsing history, saved password databases, autofill databases, and volatile caches. It does preserve session Cookies and site storage so authenticated sites can remain signed in.
Remote debugging grants powerful access to the Agent browser. Review the security notes before using authenticated accounts.