Skip to main content
Currently supported: the official Claude Code CLI, the official Claude Code extension (the one installed in VS Code, Cursor or Windsurf), and Claude Desktop launched via reclaude app. The extension needs a one-step setup — see Install → IDE extension setup.The built-in AI features of Cursor / Windsurf, Cline, and other tools that connect with an API key are not supported.
No. ReClaude uses official Anthropic accounts that we operate ourselves, completely separate from yours. We carry the ban risk — when an account is flagged, we switch you off it automatically.
Official bans during the plan period are on us: once a ban is detected, a replacement is queued automatically — no action needed; when it’s done, just reopen Claude Code or the desktop app. Dedicated 20x gets 2 Max 20x replacements per subscription period (counted from purchase or renewal); from the 3rd ban onward the replacement is a Max 5x dedicated account, and the count resets on renewal. 5x plans are not subject to this limit. Replacements made because the account hit Anthropic’s weekly usage limit are not ban replacements and are not counted.
Per-user cap = the average share. A two-person carpool shares one Max 5x account, so each user gets 1/2 of a Max 5x ($80 per 5-hour rolling window), balanced per window.
macOS, Linux, and Windows are all supported, each with amd64 and arm64 binaries (including Apple Silicon and Windows on ARM). See Install the CLI.
Yes. If two people just want to split the cost, pick the 5x two-person carpool. For proper team features, create a team organization on the Organizations page of the dashboard (members join with a 6-digit invite code), then buy dedicated seats — 5x or 20x, each seat is one dedicated account. The seat count can be adjusted in the dashboard; while active you can only renew the current tier, and you can switch tiers after it expires. Team subscriptions renew per seat and don’t accept redemption codes.
Yes. For example, a personal Dedicated 5x + a team organization + a 5x two-person carpool can coexist — each plan lives on its own org and the quotas are tracked independently. One device runs one org at a time; switch with reclaude org use <org_id>. Full details in Subscription → Holding multiple plans.
Carpool plans don’t support self-service refunds by default. Dedicated plans can be refunded for remaining days, with a switch handling fee deducted per switch. Invoiced orders are not refundable by default. Misuse-driven losses aren’t refunded. See Billing → Refunds for the full terms.
The big difference: ReClaude assigns you a real Claude account, and Claude Code uses official subscription quota instead of an API key. That means Pro/Max subscription resources are fully usable, and Claude Code needs no config changes. There’s no per-token markup like proxies.
The dashboard shows usage metadata (call counts, timestamps, status codes, model, latency, device and the like). Data access is permission-controlled, and it is not used for model training or unrelated analysis — see section 2 of the Privacy Policy.
After signing in, run reclaude app to launch Claude Desktop (carpool and dedicated plans; macOS / Windows, Linux stays on Claude Code). The first run downloads a ReClaude build of Claude Desktop (a few hundred MB); launch it the same way every time after that. Chat / Cowork / Design and other official features work as usual, and the web app is used through the desktop app. After an account replacement, just run reclaude app again.You can’t sign in to claude.ai in a browser directly: ReClaude never hands the assigned account’s credentials to your machine, and account-sensitive actions such as sign-out, payment and prepaid credits are managed by the platform.
reclaude only touches the env section of ~/.claude/settings.json: it writes the proxy and certificate variables it needs, and removes variables that would change where requests go or how they authenticate (for example your own ANTHROPIC_API_KEY, ANTHROPIC_BASE_URL, proxy and certificate variables). Everything else (theme, permissions, hooks, plugins, and so on) is left untouched.The whole file is backed up at login, and reclaude logout restores settings.json from that backup to the state it was in before your last reclaude login.
You can switch back any time: running reclaude logout restores your Claude Code config to how it was before you connected reclaude.If you want reclaude and the native claude (or switcher tools like cc-switch) to coexist, use claude --settings <your-config-file> to point at a separate config so each runs independently of reclaude.One thing to note: these tools share the same env section of ~/.claude/settings.json, so when you switch back and forth on the same config, the last write wins.
The only official support channel is the Tickets system after signing in at reclaude.ai — account, order, refund, and ops requests all go there. We do not run an official support chat group; please don’t ask for support in any chat group, since it might be missed and we can’t verify your identity.
Last modified on October 14, 2026