Session Usage Jumps 30% Per Prompt in Less Than 1 Minute of Entering the Prompt

What this error means

session usage jumped 30% per prompt in less than 1 minute of entering the prompt — abnormal token consumption spike is a Claude Code failure pattern reported for developers trying to debug abnormally high token/usage consumption where each prompt triggers a 30% jump in session usage instantly upon submission. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub anthropics/claude-code#59973 opened May 17, 2026: Multiple users report massive unexplained usage spikes per prompt, effectively burning through daily quotas prematurely. Occurs across VS Code and Windows platforms. High commercial value because it wastes paid-tier tokens.

Common causes

• GitHub anthropics/claude-code#59973 opened May 17, 2026: Multiple users report massive unexplained usage spikes per prompt, effectively burning through daily quotas prematurely. Occurs across VS Code and Windows platforms. High commercial value because it wastes paid-tier tokens.

Quick fixes

1. Confirm the exact error signature matches session usage jumped 30% per prompt in less than 1 minute of entering the prompt — abnormal token consumption spike.
2. Check the Claude Code account, local tool state, and provider configuration involved in the failing workflow.
3. Compare the failing environment with a known working setup, then change one configuration value at a time.

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/59973

Evidence note: GitHub anthropics/claude-code#59973 opened May 17, 2026: Multiple users report massive unexplained usage spikes per prompt, effectively burning through daily quotas prematurely. Occurs across VS Code and Windows platforms. High commercial value because it wastes paid-tier tokens.

Related errors

• AI Coding Tools

FAQ

What should I check first?

Start with the exact session usage jumped 30% per prompt in less than 1 minute of entering the prompt — abnormal token consumption spike 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 session usage jumped 30% per prompt in less than 1 minute of entering the prompt — abnormal token consumption spike.