Why does my Claude Code usage differ between /usage and my status bar?

A status line only receives the limits when Claude Code sends them after a reply, so a tool built on it shows the figures from your last reply, which may be hours old. /usage and the account panel show the figures as of when you open them. If the numbers differ, the status line one is almost always the older.

Which Claude Code usage number should I trust?

The one that was read most recently: /usage or the account usage panel right after you open it. A status line figure is as fresh as your last reply, and it can belong to a window that has since reset.

Why did my weekly usage percentage go down?

Usually because the weekly window rolled over, so the percentage now counts from zero in a new window, or because you are comparing a stale reading from the old window with a fresh one. Check the reset time next to each figure: if the two differ, they are not the same window.

Guide

Why Claude Code usage shows different numbers in different places

By Eren Çolak, who makes Paneherd · Updated 26 October 2026

You open /usage and see 6% for the week. A status bar extension says 13%. Neither is broken: they read the same limit at different moments. The short answer is that the status line is a snapshot from your last reply, while the usage screen inside Claude Code shows the figures as of when you open it. This guide shows where each number comes from and which to trust. For what the limits are, see the Claude Code usage limit.

Where each number comes from

/usage and the account usage panel in Claude Code. The session and weekly figures as of when you open them, with a reset time for each.
The status line. On Pro and Max plans Claude Code passes the five-hour and weekly percentages, with their reset times, to a custom status line command, after a reply. It is sent when Claude Code sends it, not on a clock.
Anything built on the status line. The free Usage Meter and Paneherd's sidebar keep that report and show it. They are exactly as current as your last reply.
claude.ai's own usage page. The account's allowance, which Claude Code shares with claude.ai and Claude Desktop.

Five reasons two displays disagree

1. One of them is older

The most common cause. If you last replied three hours ago, a status line tool shows the percentage from three hours ago. Work you did in another window, on another machine or in claude.ai since then does not appear until the next reply.

2. A window has reset since

A figure is only meaningful until its reset time. The five-hour session resets on its own clock, and an old reading from the previous session can sit next to a fresh one that says 1%. Tools that notice a passed reset time hide the figure (the Usage Meter) or show "has reset since" (Paneherd) instead of repeating a number that no longer applies.

3. The weekly window moved

Compare the reset times, not only the percentages. If one display says the week resets on Wednesday and the other in five days, they are describing different windows, so a lower percentage in the second is not a mistake and not a refund: it is a new window counting from zero.

4. Other apps use the same limit

The allowance is shared across claude.ai, Claude Code and Claude Desktop. A long chat in the browser raises the figures that /usage reads, while a status line only learns about it at the next Claude Code reply.

5. You are comparing different rows

Some accounts show more than one weekly line, for example an all-models weekly figure and a separate one for a specific model. Check that you are comparing the same line, with the same reset time.

A real example

On 2026-10-25 a status-line sidebar showed the week at 13% resetting Wednesday, while Claude Code's own usage panel, opened at the same moment, showed 6% resetting in five days. The sidebar figure was three hours old. Asking the account for its figures directly returned the same new window: 7% for the week with the reset on 31 October at 00:00 UTC. The old reading belonged to the old window. Why the window moved is not something either display says, so treat a shifted reset time as a prompt to look, not as an error.

What to do

Trust the freshest reading. Run /usage or open the account panel, and use that as the reference.
Send one message. Any reply refreshes the status line, so tools built on it catch up.
Read the age. A figure shown without an age may be hours old. Paneherd dims figures older than ten minutes and says how long ago they were updated.
Ask for live figures only if you want to. Paneherd 0.12.1 has an opt-in setting, paneherd.liveClaudeUsage, off by default. When on, it sends Claude Code's own sign-in token to Anthropic once a minute, the same request /usage makes, so the sidebar stays current between replies. The endpoint is not documented and may change. What exactly is sent is in the privacy policy. The free Usage Meter never does this: it only reads local files.

If you run several sessions

With several sessions open the gap matters more, because they all spend one allowance and any of them can have sent the last report. See how parallel sessions use your usage limits and why usage runs out so fast. To see when a window ends, read when the Claude Code usage limit resets.

Install Paneherd free