Chromeflow is a Model Context Protocol (MCP) server plus Chrome extension that lets an AI coding agent — Claude Code or OpenAI's Codex CLI — drive your real Chrome browser. The agent clicks buttons, fills forms, uploads files, and captures API keys directly to your .env file.

How is Chromeflow different from Playwright or Browser Use?

Playwright and Browser Use launch a fresh, empty browser instance with no cookies, no sessions, and no extensions. Chromeflow runs in your existing Chrome where you're already logged into Stripe, GitHub, AWS, Canvas, and every other service. There's no separate auth step and 2FA is handled by you, not by an automation script.

Does Chromeflow work with both Claude Code and Codex CLI?

Yes. Chromeflow ships as a plugin for both. In Claude Code: /plugin marketplace add NeoDrew/chromeflow then /plugin install chromeflow. In Codex CLI: codex plugin marketplace add NeoDrew/chromeflow then /plugins to install. The same Chrome extension serves both — the popup shows which agent is driving which tab.

How does Chromeflow bypass page Content-Security-Policy?

Chromeflow provides fetch_url and read_attachment tools that run in the extension's privileged background context. The extension has full host_permissions, so fetches use your Chrome cookies and are not subject to the page's connect-src CSP. This is how Chromeflow can grab authenticated Canvas attachments or Stripe documents that page-context fetch can't reach.

Is Chromeflow free and open source?

Yes — Chromeflow is MIT-licensed and free. The Chrome extension is on the Chrome Web Store, the MCP server is bundled into the plugin, and the source code is at github.com/NeoDrew/chromeflow.

Chromeflow — guided browser actions for Claude Code and Codex CLI

Heads up: GitHub links are temporarily showing 404 while the chromeflow repository awaits review by GitHub Support. Install should be back within 24 hours.