1. Run the official usage check again
Inside the active Claude Code session, run /usage. Then open Claude Settings and compare the account-specific usage status. Look for which limit is exhausted and the reset time attached to that limit.
/usage
Do not compare a session window with a weekly allowance as if they were the same meter. A plan can show more than one limit, each with its own status.
2. Confirm the account and workspace
Sign out and back in only after you have confirmed which account the session should use. A browser account, a desktop account, a team workspace, and a terminal session can be easy to mix up. Check the email, organization, and plan shown by the current client.
3. Check for API-key authentication
Claude Code behaves differently when it is authenticated with a Claude subscription versus an API key. Anthropic documents subscription limits separately from API-key pay-as-you-go usage. If ANTHROPIC_API_KEY is present in your environment, the session may be using API billing instead of the subscription allowance you expected.
In that case, the absence of a subscription-style reset countdown does not necessarily mean that the usage system is broken. Verify the authentication path and the relevant Console or account billing view.
4. Rule out a context or length limit
A context limit applies to one conversation. It can make a session feel blocked even when the account still has usage available. A usage limit is a time-based allowance across supported Claude surfaces. Starting a new conversation may help with context, but it cannot reset the account usage allowance.
- Use
/contextto inspect a large session. - Use
/compactwhen reducing context is appropriate. - Use
/usagefor the account usage state.
5. Allow for status refresh and the correct reset window
Refresh the usage view, reopen the client, and check the displayed time zone and date. A short delay in status reporting can happen, and a weekly limit may reset at a different time from a session limit. Do not rely on a reset time copied from another user's plan.
What will not reset an account limit
- Opening a new conversation or a new terminal session.
- Reinstalling the local application.
- Deleting project files or changing the working directory.
- Switching models without checking which allowance the plan uses.
When to contact support
If the account-specific usage view still shows an exhausted limit after the stated reset time, collect the account, workspace, client, model, time zone, and a screenshot of the current status. Contact the provider through the signed-in support path. Do not include secret API keys in screenshots or issue reports.
Keep the reset state visible
AI Usage Ball is designed for the gap between checking the official usage page and starting the next task. It shows available local usage information for Claude, Codex / ChatGPT, and Antigravity as a persistent visual gauge on macOS.