> ## 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.

# FAQ

> Answers to the most common ReClaude questions: supported tools, ban risk, switch warranty, carpool quotas, refunds, team sharing, and OS support.

<Accordion title="Which tools does ReClaude work with?">
  Currently supported: **the official Claude Code CLI** and the official Claude Code IDE extensions (VS Code, JetBrains, etc.). The IDE extensions need a one-step setup — see [Install → IDE extension setup](/en/cli/install#ide-extension-setup).

  Other clients (Cursor, Cline, and other Anthropic-API-compatible tools) are not yet supported. We plan to add support over time.
</Accordion>

<Accordion title="Will my personal Claude account get banned?">
  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.
</Accordion>

<Accordion title="How long do switches take? How does the warranty work?">
  Monthly plans come with a 1-month warranty: 100% coverage for official bans within the period. When the assigned account is flagged, your next request transparently switches to a backup. Switches are unlimited and uncounted within the period.
</Accordion>

<Accordion title="How is carpool quota allocated?">
  Per-user cap = the average share. In an N-person carpool, each user gets 1/N of a Max account, balanced over a 5-hour rolling window. See the plan page on [reclaude.ai](https://reclaude.ai) for exact car sizes.
</Accordion>

<Accordion title="Which operating systems are supported?">
  macOS, Linux, and Windows are all supported, with amd64 and arm64 binaries (Windows is amd64 only). See [Install the CLI](/en/cli/install).
</Accordion>

<Accordion title="Can my team share?">
  Yes. If you just want to split costs, pick a carpool plan. For proper team / organization features (seat management, account assignment), create a **Team organization**. For special arrangements, contact the commercial team.
</Accordion>

<Accordion title="Can I hold multiple plans at the same time?">
  Yes. For example, a personal Dedicated + a 4-person Carpool + some Pay-as-you-go credit 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](/en/account/subscription#holding-multiple-plans-at-once).
</Accordion>

<Accordion title="Can I get a refund?">
  Pay-as-you-go: used credit is non-refundable, unused credit may be refunded. **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](/en/account/billing#refunds) for the full terms.
</Accordion>

<Accordion title="How is this different from API-key-based proxies?">
  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 — Pay-as-you-go is billed at real API cost with no upcharge.
</Accordion>

<Accordion title="Are conversations recorded?">
  The dashboard displays metadata by default (request counts, timestamps, status codes, model, token totals), all queryable and exportable.

  The system retains relevant technical logs; for **troubleshooting, abuse control, or billing disputes**, our engineering team may access these logs, with access restricted by backend permissions. See the [Privacy Policy](https://reclaude.ai/privacy) for full details.
</Accordion>

<Accordion title="How does Pay-as-you-go billing work?">
  Activates immediately on top-up. The USD credit never expires. Each request is billed at real API cost — no monthly fee, no warranty / switching coverage. Good for bursty workloads, one-off big jobs, or topping up after a monthly plan is used up.
</Accordion>

<Accordion title="Why can't I sign in on the claude.ai website?">
  The accounts assigned to Carpool / Pay-as-you-go plans are **not open to the web client**: the claude.ai website rejects sign-ins. Use them only inside the **Claude Code CLI** or the official IDE extensions. Those flows proxy through reclaude, so account resources, subscription quota, and the 5-hour limit all follow your ReClaude account.

  Dedicated plans have a separate Claude Desktop entry point (in closed beta), launched via `reclaude app` — you don't need to, and shouldn't, sign in to claude.ai directly.
</Accordion>

<Accordion title="Does reclaude change my settings.json?">
  reclaude **merges** rather than overwrites — it won't clobber your `~/.claude/settings.json`. It only adjusts the few connection-related variables in the `env` section as needed; everything else (`theme`, `permissions`, `hooks`, plugins, and so on) is left untouched.

  `reclaude logout` restores `settings.json` to the state it was in before your last `reclaude login`.
</Accordion>

<Accordion title="How do I switch back to my original claude? Can it coexist with tools like cc-switch?">
  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.
</Accordion>

<Accordion title="Where do I report a problem?">
  The only official support channel is the **Tickets** system after signing in at [reclaude.ai](https://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.
</Accordion>