Claude Code troubleshooting

Claude Code Usage Limit Reached: What to Check

Key facts

ScopeClaude Code
Last verified
DecisionOpen /usage and read the limit scope and reset time. A session or weekly allowance, a model-family restriction and an API spending cap require different responses. Wait for the displayed reset or choose a separately billed option only after checking its terms. Repeated retries and reinstalling do not restore exhausted allowance.
Official documentation

Official error evidence (quote only; variants differ)

Official account and usage guidance

Diagnose Claude Code usage limits by account, window and billing mode. Use official evidence and safe checks before upgrading or enabling extra spend.

Last verifiedOctober 19, 2026
Quick fix

Open /usage and read the limit scope and reset time. A session or weekly allowance, a model-family restriction and an API spending cap require different responses. Wait for the displayed reset or choose a separately billed option only after checking its terms. Repeated retries and reinstalling do not restore exhausted allowance.

What exact error is documented?

You’ve hit your session limit

Documented variant, not every possible message. Official source repository or documentation, checked 2026-10-19.

Match the symptom

  • You’ve hit your session limit
  • A completed sign-in or a visible allowance does not match what the current client can do.

First checks

Collect evidence before changing configuration

Inspect usage in Claude Code
/usage
Inspect the client
claude --version

Diagnosis 1

Which limit did you actually hit?

Match the full message to the account and billing mode. Shared session and weekly restrictions can cover multiple models, while a model-specific restriction may permit another model family. An API rate or spending cap belongs to another billing path. The exact wording and reset time are better evidence than a remembered plan description.

  1. Read the session, weekly or spend label.
  2. Compare the active account with /pricing/claude-code.

Diagnosis 2

Should you wait or pay for extra use?

Waiting for the displayed reset avoids a new spending commitment. Usage credits or API access can have a separate bill and must be enabled deliberately with suitable spending controls. Do not describe either option as free continuation. Save the task state and inspect outstanding changes before leaving an interrupted coding session.

  1. Preserve the repository diff and last successful check.
  2. Read the current credit or API terms before enabling additional spend.

Diagnosis 3

What can you change for the next work window?

Reduce avoidable consumption by keeping tasks focused, removing irrelevant context and reviewing which tools are loaded. These changes help future work; they do not refund completed requests or reset a shared allowance. Track a representative task and its result so a plan upgrade can be evaluated against actual need.

  1. Start unrelated work in a fresh context.
  2. Record billed usage separately from local estimates.

If it still fails, send this evidence

A useful support request is reproducible and does not expose credentials.

  • Client version, operating system and work surface.
  • Exact error, timestamp and timezone, with credentials removed.
  • Account/workspace type and the displayed reset time, without private identifiers.
  • Last successful operation and a small reproducible read-only request.

Related paths

All troubleshooting guides

Related account failures

Frequently asked questions

Will reinstalling reset a usage allowance?

No. A service-side allowance belongs to the account. Reinstall only for an installation problem supported by diagnostics, and use the displayed reset or official support for an account restriction.

Should I post my authentication files for support?

No. Share the error, version, time and a redacted account-mode description. Never upload token files, API keys or an unredacted environment dump.

How do I know the fix worked?

Confirm the intended account and run one small read-only request. Check the resulting usage state before resuming the larger task.

Official sources

Commands and product behavior were checked against first-party documentation on October 19, 2026. Interfaces and authentication flows change; recheck the source when applying this across a team.