Claude Code usage quota increases with no active tasks — serious usage tracking bug

What this error means

Claude Code quota tracking bug: usage percentage increases without active tasks is a Claude Code failure pattern reported for developers trying to fix claude code usage quota increasing without tasks. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

Sonnet-only mode shows 23% usage but cannot use Claude. Separate report: quota jumped from 64% to 100% with no active tasks. Appears to be a background billing/tracking bug in the quota system.

Common causes

• Users see quota jump from partial usage to 100% with no running tasks. Cannot use Claude Code at all. Direct billing/usage impact on paid subscribers.
• Sonnet-only mode shows 23% usage but cannot use Claude. Separate report: quota jumped from 64% to 100% with no active tasks. Appears to be a background billing/tracking bug in the quota system.

Quick fixes

1. Confirm the exact error signature matches Claude Code quota tracking bug: usage percentage increases without active tasks.
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/59315

Evidence note: Sonnet-only mode shows 23% usage but cannot use Claude. Separate report: quota jumped from 64% to 100% with no active tasks. Appears to be a background billing/tracking bug in the quota system.

Related errors

• Claude Code thinking content invisible Opus 4.7
• Claude Code unhandled case object Object overlay crash

FAQ

What should I check first?

Start with the exact Claude Code quota tracking bug: usage percentage increases without active tasks 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 Claude Code quota tracking bug: usage percentage increases without active tasks.