setup-dev-browser

Give the agent its own Chrome: a separate window with its own profile, where the user signs in once to their tools, and that the agent drives through the dev-browser CLI. The user's normal Chrome stays untouched, and the agent never needs a password because the sessions stay saved in that profile. Do every step yourself and only ask for what needs a human (installing Chrome, signing in). Talk to the user in their language, short messages, no jargon (never say "CDP", "profile directory" or "PATH" to them).

The setup lives in four places: the launcher ~/.local/bin/chrome-ai (copied from scripts/chrome-ai), the profile ~/.chrome-ai-profile, the debugging port 9333 open on 127.0.0.1 only, and the dev-browser skill that tells every agent to connect there. If the argument gives another port, set CHROME_AI_PORT to it in the user's shell config and use it everywhere below.

1. Check the machine. This works on macOS and Linux; on Windows, stop and say it needs WSL or a Mac.

   node --version && npm --version
   ls "/Applications/Google Chrome.app" 2>/dev/null || command -v google-chrome

If Node is missing, install it (brew install node on macOS). If Chrome is missing, send the user to https://www.google.com/chrome and wait for "done".

1. Install the CLI and its browser, then check it answers.

   npm install -g dev-browser && dev-browser install
   dev-browser --help | head -5

1. Install the launcher: copy scripts/chrome-ai from this skill to ~/.local/bin/chrome-ai and make it executable. If ~/.local/bin is not on the user's PATH, add export PATH="$HOME/.local/bin:$PATH" to their ~/.zshrc (or ~/.bashrc) once, never twice.
2. On macOS, run chrome-ai app to create the "Chrome AI" app in ~/Applications, so the user can open it from Spotlight.
3. Run chrome-ai start. It opens a new Chrome window and prints http://127.0.0.1:9333. Tell the user this window is the AI's Chrome and ask them to pick a different theme color in it (Settings, Appearance) so they never confuse it with their own.
4. Ask the user to sign in, in that window only, to the tools the agent will use (Google, GitHub, Cloudflare, Lumail, Stripe, their own apps), then say "done". Never type a password, a code or a card number yourself, and never copy cookies from their normal Chrome.
5. Make sure the dev-browser skill is installed for their agent; if it is missing, run npx skills add Melvynx/ai-maxxing-skills -g -a claude-code -s dev-browser -y. If the user has a brain folder with an AGENTS.md, add one line there: browser work goes through the dev-browser skill in Chrome AI, never the user's own Chrome.
6. Let the agent run it without asking every time: merge "Bash(dev-browser *)" and "Bash(chrome-ai *)" into permissions.allow of ~/.claude/settings.json, keeping every existing entry. Read the file first and write valid JSON back.
7. Prove it works in the Chrome AI window with a named page:

   chrome-ai start >/dev/null && dev-browser --connect http://127.0.0.1:9333 <<'JS'
   const page = await browser.getPage("setup-check");
   await page.goto("https://github.com");
   const path = await saveScreenshot(await page.screenshot(), "setup-check.png");
   console.log(JSON.stringify({ title: await page.title(), url: page.url(), path }));
   JS

Open the screenshot and check the user shows as signed in on a site they signed in to in step 6. Then run chrome-ai stop, chrome-ai start and the check again: the login must survive a restart. Close the test page with browser.closePage("setup-check").

End with a short check list, a check or a cross on each line: Chrome found, dev-browser installed, chrome-ai launcher works, Chrome AI app (macOS), user signed in, dev-browser skill installed, permissions added, screenshot shows a signed-in page, login survives a restart. Then tell the user in 3 lines: open "Chrome AI" (or just ask the agent, it starts it on its own), sign in there once to any new tool, and one thing to try right now, such as "open my Stripe dashboard and tell me yesterday's sales".