codewing has two halves:
- A local client (
reclaude) running on your machine, handling Claude Code’s outbound requests.
- The codewing service, operated by the codewing 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 codewing.
- codewing 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: codewing uses official subscription quota, no API key needed.
- Manual account switching: when the account assigned to you is flagged, codewing 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.
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 codewing itself, not Anthropic — we maintain a separate 5-hour rolling window so quota stays evenly split between carpool members. Last modified on June 4, 2026