Skip to main content
ReClaude has two halves:
  1. A local client (reclaude) running on your machine, handling Claude Code’s outbound requests.
  2. The ReClaude service, operated by the ReClaude team, which assigns you a healthy official Anthropic account.

​
What happens during a request

  • Claude Code makes a request.
  • The local daemon forwards it to ReClaude.
  • ReClaude uses the official account assigned to you and connects to the official API on its subscription quota.
  • The response goes back the same way.
To Claude Code, the whole hop is invisible — it thinks it’s talking to a local account.

​
Things you don’t have to think about

  • Configuring an API key: ReClaude uses official subscription quota, no API key needed.
  • Manual account switching: when the account assigned to you is banned, ReClaude queues a replacement automatically and the new account is delivered to the devices you’ve already registered. For the Dedicated 20x replacement tier rules see Subscription → 1-month warranty.
  • Risk isolation: a flagged account doesn’t affect the accounts assigned to other users.

​
What the dashboard shows

The dashboard shows usage metadata (call counts, timestamps, status codes, model, latency, device and the like) — for showing you usage and helping us schedule. Data access is permission-controlled, and it is not used for model training or unrelated analysis. See section 2 of the Privacy Policy.

​
Where usage numbers come from

The overall account usage on the home page is passed through from Anthropic’s OAuth API — we just surface what Anthropic returns. The subscription days remaining are your ReClaude subscription’s expiry, unrelated to the official account. The carpool 5-hour window is managed by ReClaude itself, not Anthropic — we maintain a separate 5-hour rolling window so quota stays evenly split between the two carpool members ($80 per person per window, that is, 1/2 of a Max 5x).
Last modified on October 14, 2026