How Claude Reset works
This site helps you organize what you can see in your own Claude interfaces. It cannot read your account, grant an offer, reset a limit or confirm that Claude will accept a request.
Rule version: 2026-09-24.1.
Three different kinds of evidence
- Your account input: limits, percentages and times you type or explicitly import. They describe what you observed, and stay local unless you explicitly enable a separate reminder feature.
- Official public sources: Anthropic documentation, reviewed public event records and the independent status snapshot. A public announcement or Operational status cannot establish your account's eligibility or remaining usage.
- SAMPLE data: synthetic examples for learning or tests. They are labeled and never treated as an account observation or real event.
How to read a result
- Unknown means the needed field was not provided or cannot be identified. It never means zero usage or no limit.
- Partial means only some relevant windows are known. Another window may still block the task.
- Recorded time passed means a time you entered is in the past. It is a prompt to check Claude Usage again, not proof that an account reset.
- About 15 minutes is this site's boundary for treating a saved personal observation as needing reconfirmation. It is not an Anthropic reset rule or a guarantee that a timer remains accurate.
Local time and daylight-saving ambiguity must be resolved before a precise check time can be shown. The checker never starts a new period just because a recorded time elapsed.
Rules, sources and coverage
Oldest documented rules-source check: . This date is historical; it is not a live Up to date signal. Recheck is due before a new rule claim.
- S01: What is a limit reset?
Anthropic (Claude Help Center). Free reset offers: granted occasionally, restore what the account shows, do not change the usual weekly schedule, may expire, cannot be undone.
- S02: What is the Pro plan?
Anthropic (Claude Help Center). The weekly reset is a fixed time assigned to the account; it is never derived from sign-up, billing or first use.
- S03: Usage limit best practices
Anthropic (Claude Help Center). The Usage page is where a user reads their own limits; limits differ by plan and seat.
- S04: How do usage and length limits work?
Anthropic (Claude Help Center). Usage limits and context length are different limits; Claude clients on one account share usage.
- S05: Claude Code status line
Anthropic (Claude Code docs). Documented rate_limits fields of the status line input (v2.1.251+): fields may be missing and resets_at is Unix seconds.
- S06: Claude Code interactive mode
Anthropic (Claude Code docs). Waiting for the limit to recover and continuing (v2.1.234+, eligible interactive subscription sessions, with session and sleep conditions).
- S07: Claude API rate limits
Anthropic (Claude Developer Platform docs). API request and token rate limits; the subscription five-hour and weekly windows do not apply to the API.
- S08: Claude status JSON
Anthropic (Claude status page). Public service status; it can never verify one account's limits.
Input coverage
Manual window entry is available. English Claude Usage text and documented Claude Code statusline JSON are candidates for local import, but no real holdout set has been locked and accepted yet; they are not labeled Verified formats. Other languages, unfamiliar model or seat names, and fields outside the documented whitelist remain unknown until reviewed.
Public event records require separate human source review. The service-status JSON is collected independently every five minutes when that collector is deployed; it never confirms a personal balance.