Tools · Tracker
Claude Usage Tracker
Usage feels opaque until you name where it goes. Log real work sessions, review the week, then decide whether the problem is volume, model choice or messy structure.
Not affiliated with Anthropic. Claude Token Optimization is an independent site and audit service. Claude and related product names are trademarks of Anthropic PBC. Plan prices, model rates, and usage limits change; always confirm on Anthropic’s own docs.Figures last verified 17 September 2026· Anthropic usage references
For dollars instead of limits, use the Claude token cost calculator.
Weekly worksheet
Manual session log
Rows are saved in this browser. There is no account and no claimed sync with Anthropic.
| Date | Week | Surface | Model | Size | Turns | Limit | Notes | Remove |
|---|---|---|---|---|---|---|---|---|
| Log a few real work sessions this week. The goal is pattern, not perfection. | ||||||||
Why usage feels opaque
Claude usage is not a fixed messages-per-day counter. Length of the thread, files, tools, model and effort all change how fast you burn capacity.
On paid consumer plans, limits typically include a rolling five-hour session window plus a separate weekly limit. Activity across Claude on web, desktop, mobile and Claude Code draws from the same pool. Cowork sits in that same family of surfaces for plan usage. Exact multipliers are plan-specific.
That design is fair for Anthropic’s capacity management. It is also why a mental model plus a weekly log beats relying on memory. Related reading: usage limits, optimization and API pricing.
What Anthropic already shows
- Open Settings > Usage in Claude.
- Check the current session bar, including the five-hour window and time remaining.
- Check weekly limits, including any model-specific breakdown your plan shows.
- Note reset times. Weekly resets are account-assigned; session resets roll every five hours.
- If your plan supports usage credits, that section appears in the same area when enabled.
There is no third-party official integration claimed here. Anthropic owns the source of truth. This tracker is a habit layer on top, not a replacement dashboard.
What to track yourself
The official bars tell you how much is left. Your notes tell you why it moved. You do not need perfect token counts. Approximate size bands are enough for a weekly review.
| Signal | Why it matters |
|---|---|
| Turns / day | Raw activity volume. |
| Re-pastes | The same brief or doc pasted again instead of pinned context. |
| Tool / computer use | Extra round-trips and screenshots can burn capacity quickly. |
| Uploads | Large files inflate context even when you only asked one question. |
| Model switches | Heavier models cost more of the pool per turn. |
| Retries | Try-again and regenerate loops stack quietly. |
| Surface | Chat, Claude Code and Cowork have different work shapes inside a shared plan context. |
| Hit limit? | Ties the log to the moment capacity ran out. |
Weekly review ritual
- Open Settings > Usage. Screenshot or jot session versus weekly bars and next reset.
- Scan your tracker rows. Count limit hits. Note which surface and size band dominated.
- Name one waste pattern: re-pasting the same SOP, leaving a huge thread alive, defaulting to the heaviest model, or retry storms.
- Pick one fix for next week: pin context outside chat, start a fresh thread, switch model for triage work, or cut tool loops.
- Decide whether to optimize structure or buy more capacity. If the log says same mess, more often, structure comes first.
| Usage tracker | Cost calculator | |
|---|---|---|
| Primary question | Where does capacity go? When do I hit limits? | What would this token volume cost on the API? |
| Unit | Sessions, weeks and habits. | Dollars from MTok rates. |
| Best for | Pro, Max and Team operators watching bars. | API and Enterprise-style usage budgeting. |
| Output | Behavioral map plus weekly ritual. | Monthly and annual spend estimate. |
When to go deeper than a worksheet
A tracker will not rewrite your prompts. It shows when you are burning turns on structure problems. Good signals to move to an audit include limits on routine work, repeated re-pastes, tool loops or the same patterns after a plan upgrade.
Paste recent prompts and replies into the async Claude token audit and get a written token map and change list. You can read about the operator, skim a sample audit report and check privacy notes first.
FAQ
Is this an official Anthropic usage tracker?
No. Anthropic’s official view is Settings > Usage. This page teaches how to use that view and keep a simple personal log.
Do Chat, Claude Code and Cowork share limits?
On paid plans, Anthropic describes activity across Claude surfaces, including Claude Code, as drawing from the same usage pool, with rolling five-hour and weekly limits on relevant plans. Confirm the current Cowork wording for your plan in Anthropic’s help center.
Why isn’t there a fixed message count?
Usage depends on conversation length, files, tools, model and related features. A fixed message count would mislead.
Should I log exact tokens?
Only if you already have them from API logs. For Claude.ai work, size bands plus notes are enough to spot waste.
How does this connect to cost?
Limits are not invoices. For API-style dollars, open the cost calculator. To size a paste before you send it, try the token counter. For plan cards and rate context, start with API pricing.
What if I need someone to read my prompts?
Use the audit CTA above, or go straight to the audit page. You can also review privacy and the sample report before submitting.