What this error means
Anthropic Claude Code Sonnet only mode shows 23% usage but cannot use Claude is a Claude Code failure pattern reported for developers trying to fix claude code sonnet only mode quota not working usage blocked. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.
Why this happens
Claude Code in sonnet-only mode reports 23% usage but refuses to process requests. Bug labeled as 'area:cost' — likely a quota tracking or billing system issue. Directly impacts paying users' ability to work.
Common causes
- Users on Claude Code's sonnet-only mode see low usage (23%) but are blocked from using Claude, suggesting a quota tracking or billing bug in Anthropic's system
- Claude Code in sonnet-only mode reports 23% usage but refuses to process requests. Bug labeled as 'area:cost' — likely a quota tracking or billing system issue. Directly impacts paying users' ability to work.
Quick fixes
- Confirm the exact error signature matches
Anthropic Claude Code Sonnet only mode shows 23% usage but cannot use Claude. - Check the Claude Code account, local tool state, and provider configuration involved in the failing workflow.
- Reduce request pressure, check quota or plan limits, and retry with backoff instead of immediate repeated requests.
Platform/tool-specific checks
- Verify the command, editor, extension, or API client that produced the error.
- Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
- Avoid deleting credentials, local model data, or project settings until the failing scope is clear.
Step-by-step troubleshooting
- Capture the exact error message and the command, editor action, or request that triggered it.
- Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
- Review the source evidence below and compare it with your environment.
- Apply one change at a time and rerun the smallest failing action.
- Keep the working fix documented for the team or deployment environment.
How to prevent it
- Keep provider/tool configuration documented.
- Record non-secret diagnostics such as tool version, provider name, model name, and command path.
- Add a lightweight check before CI or production workflows depend on the tool.