Chromeflow

Chromeflow

Let your AI coding agent (Claude Code or Codex CLI) drive your real Chrome — clicks, fills forms, grabs API keys, writes them to .env .

Install · Tools · Website · Security

---

The problem: Playwright, Browser Use, and Puppeteer launch a fresh empty browser every time — no cookies, no sessions, no 2FA. Your AI agent gets stuck at the first login screen.

Chromeflow: drives your actual Chrome, where you're already logged into Stripe, AWS, Supabase, Canvas, GitHub. The agent automates what it can (clicks, fills, uploads, captures keys) and pauses for anything that needs you (passwords, 2FA, payment). One MCP server, 30 browser tools, works with both Claude Code and Codex CLI.

Battle-tested: shaped by 400+ hours of real agentic browser work before public release — every gnarly edge case (React Selects, isTrusted-gated forms, shadow-DOM clicks, page-CSP fetches, silent redirects, cookie leaks, 0×0 hidden elements) is in the error-handling recipes. Not a weekend hackathon project.

Why Chromeflow?

Existing browser automation tools (Playwright, Browser Use, Puppeteer) launch a fresh, empty browser — no cookies, no sessions, no extensions. Every time they start, you're logged out of everything and can't handle 2FA.

Chromeflow works in your actual Chrome browser, where you're already logged into Stripe, AWS, Supabase, and everything else. Claude automates what it can (clicking buttons, filling forms, uploading files) and pauses for anything that needs you (passwords, 2FA, payment details).

Validated platforms 🟢

Tested end-to-end against the live platform before every release. Procedures live in tests/antibot/platforms/; the validated-against page at chromeflow.run/validated auto-updates from tests/antibot/last-run.json on each run.

Submit handoff (by design). Reddit, X, LinkedIn, Facebook, Instagram all gate their submit buttons on a real isTrusted human gesture as part of their anti-bot stack. Chromeflow lands the typing path (which is what an agent actually needs) and then uses highlight_region + wait_for_click so the user clicks Submit themselves.

Why this is the moat. Playwright, Puppeteer, browser-use, crawl4ai all launch a fresh logged-out browser. They can't see your sessions, and the isTrusted-strict checks on these platforms reject their vanilla CDP clicks. Chromeflow runs in your real logged-in Chrome with a humanlike bezier + PointerEvent isPrimary=true click sequence; the validated-against table above shows what that gets you in practice. See /validated for the side-by-side comparison.

How it works

Chromeflow is two things that work together:

• MCP server — gives your coding agent (Claude Code or Codex) a set of browser tools (open_page, click_element, fill_form, set_file_input, get_page_text, write_to_env, etc.)
• Chrome extension — receives those commands and acts on the active tab (highlights, clicks, fills, uploads files, captures screenshots)

Claude drives the flow. You only touch the browser for things that genuinely need you — login, passwords, payment details, personal choices.

Setup

Claude Code

1. Install the plugin (one-time, machine-wide):

/plugin marketplace add https://github.com/NeoDrew/chromeflow.git

/plugin install chromeflow

Run these inside Claude Code. The plugin registers the MCP server, pre-approves Chromeflow tools, and ships the usage skill — no per-project setup needed.

2. Install the Chrome extension (one time):

chromewebstore.google.com/detail/chromeflow/lkdchdgkbkodliefobkkhiegjdiidime — click Add to Chrome.

The extension persists across Chrome restarts. You only do this once.

3. Restart Claude Code.

That's it. Claude will automatically reach for Chromeflow whenever a task needs browser interaction, in any project. The plugin's SessionStart hook also cleans up any stale config left over from older npx chromeflow setup-based installs on first run.

Codex CLI

1. Install the plugin (one-time, machine-wide):

codex plugin marketplace add https://github.com/NeoDrew/chromeflow.git

Then inside Codex:

/plugins install chromeflow

The plugin registers the MCP server and ships the same usage skill that Claude Code uses, host-adjusted for Codex.

2. Install the Chrome extension (one time) — same Web Store link as above. The extension is host-agnostic and serves both Claude Code and Codex from the same install.

3. Restart Codex.

Codex will reach for Chromeflow on browser tasks the same way Claude Code does.

Usage

Just ask Claude normally:

"Set up Stripe for this project — create a product with monthly and annual pricing, capture the price IDs into .env"

"Go to Supabase and get my project's anon key and service role key"

"Help me configure SendGrid webhooks for this app"

Claude will navigate, highlight steps, click what it can, pause for anything sensitive, and write values to your .env automatically.

What Claude can do

File uploads

set_file_input uses Chrome DevTools Protocol to bypass the browser's file-input script restriction — the same mechanism used by Playwright and Puppeteer. It works even when the is hidden behind a custom drag-and-drop zone.

set_file_input("Upload", "/Users/you/Downloads/task.zip")

Terminal screenshots

capture_terminal screenshots the terminal window (Terminal, iTerm2, Warp, VS Code, Ghostty, etc.) and saves it as a PNG. Use this with set_file_input to upload terminal output to a web form.

Dedicated Claude window

Click the Chromeflow extension icon and use "Use this window for Claude" to lock Claude's browser operations to a specific Chrome window. This lets you freely use other Chrome windows without Claude interfering.

Running multiple agent sessions in parallel

Chromeflow supports up to 11 agent sessions (Claude Code, Codex, or a mix) running in parallel, each automating a different Chrome window without touching the others.

How it works:

• Each agent session spawns its own Chromeflow MCP server, which auto-discovers a free port in the range 7878-7888 (first session gets 7878, second gets 7879, etc.).
• The Chrome extension maintains one WebSocket connection per port and tracks per-port window assignments.
• Every browser tool call is routed to the Chrome window assigned to the port the request came in on.

Setup:

1. Start your first agent session as normal — its Chromeflow will claim port 7878.
2. Start a second agent session in another terminal — its Chromeflow auto-falls-back to 7879.
3. Click the Chromeflow extension icon. The popup now shows one row per instance (Port 7878, Port 7879, ...) each with a green dot when live.
4. In Chrome window A, open the popup and c