# Know where your Claude Code limits are, before you hit them

> Tenfold reads Claude Code's own status line, so it knows your weekly limit and where your current pace lands by the reset. The meter sits in the toolbar, always in view, and the usage screen shows what your usage would cost at API rates.

Source: https://gettenfold.app/claude-code-usage-limits · Tenfold is a Mac app for running Claude Code agents side by side. · Updated 2026-11-03

Hitting your weekly limit halfway through a feature is the worst time to find out where it was. Tenfold keeps the number in view, and tells you where your current pace is heading.

## The weekly meter

The usage pill in the Workspace toolbar shows your weekly window: a meter, the percent used, and a countdown to the reset. It turns amber from 70% and rose from 85%.

Hover it for more:

- **The reset time and your pace.** Where you'll be by the reset if you keep going at the current rate, like "~19% by reset". If you're on course to run out first, it says when, like "out in ~42m". At 100% it says "limit reached".
- **Per-model weekly windows**, when your plan has them, with how old the figures are and a button that runs `/usage` to renew them.
- **What you've spent today.**

Tenfold waits until 5% of the week has passed before projecting your pace. Earlier than that, the figure is mostly noise.

## The usage screen

Open it with ⌘U or by clicking the pill. It shows:

- **This month so far**, with a pace bar: what you've spent, where you're on course to end the month, and where last month ended.
- **Today, all time**, and what caching saved you this month.
- **A spend calendar**, one square per day for the last few months.
- **Where the money goes**: the cost split by input, output, cache write and cache read.
- **Models**: cost and tokens per model.

You can copy a text summary or a share card image from the top of the screen.

## Where the numbers come from

Claude Code passes a block of data to its status line every time it refreshes: the model, the context window, the session's cost and, on a Claude plan, your rate limits. Tenfold wraps your status line to read that data, and your own status line keeps running as before. The cost figures come from Claude Code's own files on your Mac. Nothing is uploaded.

Costs are shown as the API equivalent at standard rates. They're not a bill: they show how much your plan is worth. Subscription charges and tool or service fees aren't included.

## Good to know

- Claude Code reports usage limits only on Pro and Max plans. With an API key, there's no weekly window to show.
- The meter appears after Claude's first reply in a session.
- Running [several agents in parallel](https://gettenfold.app/run-multiple-claude-code-agents) uses your plan faster. The pace projection tells you how much room you have.

## Questions

### How can I see my Claude Code usage limit?

Claude Code reports your rate limits to its status line on a Pro or Max plan. Tenfold reads that data and shows your weekly window in the Workspace toolbar: a meter, the percent used and a countdown to the reset. Hover it for the reset time, your pace projection, per-model windows and what you've spent today.

### Will I run out of Claude Code usage before the weekly reset?

Tenfold's pace projection answers that. It shows where you'll be by the reset if you keep going at the current rate, like "~19% by reset", and if you're on course to run out first, it says when, like "out in ~42m".

### Why doesn't Tenfold show a weekly limit for me?

Claude Code only reports rate limits on a Pro or Max plan, and only after Claude's first reply in a session. With an API key, there's no weekly window to show. Check too that the Status line switch is on, on the Integrations page in Settings.

### Are the costs Tenfold shows a bill?

No. Costs are shown as the API equivalent at standard rates, to show how much your plan is worth. Your agents run on your own plan or API key, and Tenfold doesn't add to your Claude usage.

### Does Tenfold replace my Claude Code status line?

It wraps it. Tenfold's reporter passes the status line data to Tenfold, then runs your original command with the same data, so your line looks the same in every session. Uninstalling the integration puts your original back.

## In the docs

- https://gettenfold.app/docs/usage-and-limits
- https://gettenfold.app/docs/what-tenfold-changes
- https://gettenfold.app/docs/troubleshooting