Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.reclaude.ai/llms.txt

Use this file to discover all available pages before exploring further.

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 flagged, ReClaude switches you to a backup; on monthly plans this isn’t counted.
  • Risk isolation: a flagged account doesn’t affect the accounts assigned to other users.

​
What we log

The dashboard displays metadata by default: request counts, timestamps, status codes, model, token totals — for showing you usage and helping us schedule. The system retains relevant technical logs for troubleshooting, abuse control, and billing disputes, with access restricted by backend permissions. See the Privacy Policy for full details.

​
Where usage numbers come from

The overall account usage and subscription days remaining on the home page are passed through from Anthropic’s OAuth API — we just surface what Anthropic returns. 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 carpool members.
Last modified on May 18, 2026