Chromeflow use cases — what AI agents can actually do in your browser

What can Chromeflow actually do?

Concrete workflows AI coding agents (Claude Code, Codex CLI) handle end-to-end with Chromeflow — the parts of your job that used to involve flipping to a browser, doing the click-fill-paste dance, and flipping back to your terminal.

Each page below is a tangible walk-through: which Chromeflow tools the agent reaches for, where the human handoff happens (passwords, 2FA, payment), and what you actually get at the end. Not screenshots and marketing copy — the real tool-call patterns.

Set up a Stripe product + capture the secret key

Agent creates a new Stripe product, sets pricing, configures webhook endpoints, reveals the secret key, and writes it straight to your project's .env. You stay in the loop for the password and 2FA.

~5 min · uses open_page, fill_form, read_attachment, write_to_env

Download authenticated Canvas attachments

Canvas attachments live behind student SSO. Chromeflow's privileged-context tools fetch them with your existing session cookies, save to disk, and parse .docx in-extension. No more "log in again to read this PDF".

~2 min · uses fetch_url, download_file, read_attachment

Walk through an OAuth device-code flow

Tools like the MCP Registry publisher, GitHub CLI, and many CI systems use OAuth device-code login. Chromeflow auto-fills the code, highlights the Authorize button (which GitHub anti-bot reserves for a real human click), and detects completion.

~30 sec · uses fill_input, highlight_region, wait_for_click

Capture any API key directly to `.env`

The pattern that applies to Stripe, Supabase, OpenAI, Anthropic, AWS, SendGrid, Twilio — every SaaS dashboard where the key is revealed once and you have to grab it before navigating away. Agent reveals, captures, writes, confirms.

~1 min · uses find_text, write_to_env, clear_overlays

What ties them all together

All four workflows have the same shape: they live behind a login. Playwright, Browser Use, and Puppeteer launch a fresh-profile browser with no inherited sessions, so each of these tasks would start with re-engineering the login (and silently fail at 2FA). Chromeflow drives your real Chrome where you're already signed in — so the agent's first tool call is the actual work, not the auth dance.

If your agent's job lives behind a login, see how Chromeflow compares to Playwright, Browser Use, and Puppeteer. If you're already convinced, install in two commands from the homepage.