A faster browser for your AI agent

Because browser automation is bursty. Most people do not use an agent browser every day, and a subscription punishes that. You buy a pack, paid credits never expire, and a typical task costs 2-3 credits. No renewal anxiety, no cancel-flow dark patterns.

Nothing breaks. The next tool call returns a polite message with a top-up link instead of running, and Claude relays it to you. Your installation, saved flows, and login states are untouched; buy a pack and the same call works again seconds later. We email you once when you hit zero, and that's it.

Reflex works with any client that can run local MCP servers: Claude Desktop, Claude Code, Cursor, Windsurf, VS Code, and others. ChatGPT currently supports remote connectors rather than local MCP servers, so not yet; the moment that changes, Reflex will work there too, since it speaks standard MCP.

It is, and it's good; Microsoft maintains it and it wins at iframes, network mocking, and Firefox/WebKit. The difference is the cost model inside your chat: in our measured head-to-head the same flows took Playwright MCP 14 tool calls and ~56K tokens of your context window versus 6 calls and ~13K for Reflex, and it completed 3 of 6 flows versus Reflex's 5. Every round trip is seconds of model time, and every token of page dump crowds out your actual conversation. We published the full benchmark, including the places Reflex loses, at /benchmarks. If those numbers don't matter to your usage, use Playwright MCP; it's a fine tool.

Reflex drives your installed Chrome with its own profile. Log in to a site once in that window and tell Reflex to save the session; it stores cookies and localStorage locally on your disk and reuses them on demand. Your logins persist across tasks and never leave your machine.

One credit per tool call, and a typical task is 2-3 calls: one to open and read the page, one batched call that performs every step and verifies the result. That's the core design difference; tools that take one action per call need 5-6 calls per flow for the same work (14 vs 6 across our three measured flows). Failed calls also cost one credit, because the failure report you get back (what missed, the closest candidates, console errors, a screenshot) is usually enough to fix the task in one more turn.

Only for the metering layer, and it never blocks your work. The key is validated when the server starts, credits are decremented against a local cached balance, and usage syncs in the background with an offline buffer. Browsing localhost or an intranet app works fine.

Paid credits never expire. The 30 free signup credits expire after 14 days; they exist so you can evaluate Reflex properly, not as a permanent free tier.

If you bought a pack and it isn't working out, email support within 14 days and we refund the unused balance, no interrogation. Refunds for consumed credits are case by case, biased toward yes; arguing over $9 is not a business we want to be in.