My session limit is used up
Open Settings → Usage in Claude and read the session timer. A weekly allowance can still have room while the session allowance is exhausted. Use the planner below to keep that time handy.
Open my usage →Practical help
Hit a limit? Find your next step.
First, identify what Claude is telling you. Your account’s timer and a public reset announcement answer different questions.
Is Claude down?
Anthropic’s service status. Your account’s usage limits are separate.
Status not confirmed
Active reports from Anthropic (original titles)
1. What are you seeing?
Select a message above. You can also read every case in the guide below.
2. Keep your reset time handy
Copy the reset date and time shown in Claude → Settings → Usage. If multiple limits block you, enter both: the later time is the earliest point when both entered limits have cleared.
This planner cannot read your Claude account. Times you enter stay in this browser; nothing is sent to our server. It does not predict surprise resets.
Enter at least one time to calculate a wait.
Read the message before choosing a fix
A fresh session, a new chat, and a public reset are different events. For example: if your session resets tonight but your weekly limit resets on Friday, the session refresh alone may not let you continue. If only a conversation is too long, waiting for Friday solves the wrong problem.
My weekly limit is used up
A session refresh does not clear a weekly limit. Read the weekly reset time in your account, including any separate model limit shown there. Waiting five hours may leave the weekly restriction in place.
Open my usage →This conversation is too long
A length limit concerns one conversation’s capacity. Save the goal, decisions, and next task, then start a new chat with that handover. A new chat does not replenish a used-up account allowance.
Read about length limits →My API request returns 429
API limits are separate from the subscription reset board. Read the error and any retry-after header, then check your organization’s rate and spend limits in Console. Repeated retries will not fix a spend cap.
Read API limit documentation →Claude errors even though I have usage left
Compare the exact error with Anthropic’s status page. An incident is different from exhausted usage. If status does not explain it, record the error, product, and time for support; never include an API key.
Open Claude status →I saw a banked reset announcement
A banked reset is a one-time offer you choose to use. Check the announcement’s eligible plans and expiry, then look in Settings → Usage. The announcement date is not proof that your own allowance has already changed.
Read the sourced announcement board →A reset is not a fixed number of messages
There is no reliable “messages left” conversion here. Workload and account limits vary. Check the actual usage meter before a large task rather than treating a historical average as spare capacity.
Make the next session count
Prepare a small handover: the goal, what is already done, and the specific result you need next. Attach only relevant files. For coding, specify the files and acceptance checks before asking for a broad repository investigation. These reduce unnecessary work; they do not promise extra allowance. See Anthropic’s usage best practices.
Claude Code and payment settings
Pro and Max subscription use is shared across Claude and Claude Code. In Code, check your account and authentication method before troubleshooting billing. An API key can put work on API billing instead. Anthropic explains the two paths.
If you choose paid usage credits, review the account’s spending settings first. A paid continuation is a billing choice, not a reset. Read the official usage-credit instructions before enabling it.
Sources and maintenance
Written and maintained by Mike for Claude Resets. Official help pages checked October 17, 2026. This is our own troubleshooting sequence; linked Anthropic documentation and your account control current eligibility and limits.
Found a mismatch? Send a correction with the affected page and public evidence. Do not send credentials or account screenshots containing private data.