[BUG] API Error: Rate limit reached despite Claude Max subscription and only 16% usage

What this error means

Rate limit reached despite Claude Max subscription and only 16% usage is a Claude Code failure pattern reported for developers trying to fix spurious rate limiting in claude code when subscription is max and actual usage is well under limit (16%). Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub Issues #29579 in anthropics/claude-code, open since Feb 28 2026, 150 comments. Labeled area:api + area:auth + bug + has_repro + platform:vscode/windows. Distinct from general quota exhaustion — this is incorrect rate-limiting during active sessions. Category: Anthropic API per approved mapping. Not covered by existing entries.

Common causes

• GitHub Issues #29579 in anthropics/claude-code, open since Feb 28 2026, 150 comments. Labeled area:api + area:auth + bug + has_repro + platform:vscode/windows. Distinct from general quota exhaustion — this is incorrect rate-limiting during active sessions. Category: Anthropic API per approved mapping. Not covered by existing entries.

Quick fixes

1. Confirm the exact error signature matches Rate limit reached despite Claude Max subscription and only 16% usage.
2. Check the Claude Code account, local tool state, and provider configuration involved in the failing workflow.
3. 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

1. Capture the exact error message and the command, editor action, or request that triggered it.
2. Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
3. Review the source evidence below and compare it with your environment.
4. Apply one change at a time and rerun the smallest failing action.
5. 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.

Sources checked

• https://github.com/anthropics/claude-code/issues/29579

Evidence note: GitHub Issues #29579 in anthropics/claude-code, open since Feb 28 2026, 150 comments. Labeled area:api + area:auth + bug + has_repro + platform:vscode/windows. Distinct from general quota exhaustion — this is incorrect rate-limiting during active sessions. Category: Anthropic API per approved mapping. Not covered by existing entries.

Related errors

• AI Coding Tools

FAQ

What should I check first?

Start with the exact Rate limit reached despite Claude Max subscription and only 16% usage text and the smallest action that reproduces it.

Can I ignore this error?

No. Treat it as a failed Claude Code workflow until the root cause is understood.

Is this guaranteed to have one fix?

No. The imported evidence supports the troubleshooting path above, but tool behavior can vary by account, plan, version, provider, and local configuration.

How do I know the fix worked?

Rerun the same command, editor action, or request. The fix is working when that action completes without Rate limit reached despite Claude Max subscription and only 16% usage.