To check Claude Code usage, enter /usage in a Claude Code session. It opens your usage summary, including plan limits where available. You can also open Claude’s Usage settings to check your account’s allowance and reset information.
The useful number depends on the question. “Can I keep coding?” needs a plan limit. “How much will this cost?” needs billing data. A token counter can be interesting without answering either one.
Check your usage in Claude Code
- Open Claude Code with the account you want to check.
- Enter
/usageat the prompt. - Find the plan-usage section. Read each available window separately, including its reset information.
- Use the account’s Usage settings when you want the browser view.
Anthropic’s current command reference lists /cost and /stats as aliases for /usage. Older tutorials may describe them as separate screens. Type / to see the commands available in your installed client.
On supported plans, the browser shows a five-hour session allowance and weekly limits. Check the time beside the particular limit you are watching; a weekly reset and a session reset answer different questions. Anthropic explains the account view in its usage-limit guide.
Allowance, context, tokens and cost: which number matters?
| Reading | What it tells you | How to use it |
|---|---|---|
| Plan allowance | How much of a named usage window has been consumed. | Check before starting a substantial piece of work. |
| Reset time | When that particular window is due to reset. | Keep the window’s name beside the time. |
| Context percentage | How much of the conversation’s context capacity is occupied. | Understand the current conversation, rather than your account’s remaining allowance. |
| Local token history | Activity recorded by the sessions included in a report. | Compare work patterns while keeping the report’s coverage in mind. |
| Estimated session cost | A monetary estimate based on token use and pricing. | Use it for analysis; check provider billing for actual charges. |
For example, 82% remaining means 18% used in the same allowance window. It does not mean 82% of your context remains, or that you have 82% of a dollar budget left. Keep five-hour and weekly percentages separate instead of adding them.
The Session dollar figure in /usage is an estimate. For Pro and Max subscribers, it is not a bill for included usage. Paid usage credits and API billing have their own monetary reporting. See Anthropic’s cost and usage documentation when reconciling those figures.
Keep usage visible with a Claude Code statusline
A statusline keeps a small reading beneath the Claude Code prompt. To set one up, give /statusline a description such as:
/statusline Show each available subscription allowance window with its name, percent used, and reset time in my local timezone. Label context percentage separately. Omit unavailable values.Review the proposed script and settings changes. Then compare the labels and percentages with /usage. Anthropic’s statusline documentation covers manual setup and Windows examples too.
The documented subscription fields provide five-hour and seven-day percentages used, with reset timestamps. They are available for eligible Pro and Max accounts after a response supplies the data. An absent field means unavailable, not zero. A statusline can redraw without receiving a new allowance reading, so a moving countdown alone does not prove the percentage is fresh.
When should you use a separate usage monitor?
Start with the built-in view for current allowance. A history tool makes sense when your question is “What did I use yesterday?” or “Which sessions account for the activity?”
ccusage, for example, analyzes locally recorded Claude Code usage. Its reports are useful for comparing token activity over time. Its cost modes can use stored amounts or calculate estimates, so check the chosen mode before treating a dollar total as meaningful. Local history does not automatically cover another computer or your browser conversations.
Put Claude usage on your desk with TickrMeter
If you want the reading beside your editor, TickrMeter’s AI Usage app offers a physical view of supported personal allowance data. The terminal can get back to being a terminal.
You’ll need a TickrMeter, a supported Claude Code account, and the local helper on the computer where you use Claude Code. The helper requires Node.js and a compatible Claude Code installation; follow the current requirements shown during setup.
- Open Apps, choose AI Usage, and select the personal Claude connection.
- Copy the one-time connection command from your account. Run it on your Claude Code computer and follow the connection instructions.
- Return to TickrMeter and check the connection. Allow your normal Claude activity to supply an allowance reading.
- Choose the supported personal-usage view, save the setup, and review its preview before sending it to your TickrMeter.
- Compare the same allowance window with Claude’s own usage screen. Check whether each view labels the percentage as used or remaining.
The helper needs an awake, connected computer to send new readings. Claude activity, the helper and the display each have a part in updating the result. Treat an old reading as the last known state, especially after your computer has been asleep.
Why is usage missing or unchanged?
In Claude: check the signed-in account and the available window. If /usage reports cached data or a failed request, use its retry option. Missing statusline fields can also reflect account eligibility or a session that has not received its first response.
On TickrMeter: check the connection, the helper’s computer and the age of the reading. Reconnect through the portal if the account has changed. A blank or stale value is not a full allowance.
Using both coding assistants? See how to check Codex usage. For the physical setup options, start with AI Usage on TickrMeter.
