[BUG] Usage limit does not reset to 0 after 5-hour/weekly reset — shows already-consumed usage with no activity

Status Open
Reported on v2.1.206
Maintainer reply None cached
Activity 1 comment · opened Aug 9, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Description
After the 5-hour usage limit resets, the counter does not start at 0. Instead it immediately
shows a significant chunk already consumed (roughly 80k-100k tokens, or ~57-59% of the weekly
limit in one observed case) before any new request has been made in the fresh session.

This is not a one-off — it happens consistently on every reset I've observed.

Steps to reproduce

  1. Use Claude Code until the 5-hour usage limit is reached / blocked.
  2. Wait for the limit to reset (shown in the UI countdown, e.g. "Resets Thu, Aug 13, 3:00 PM").
  3. Open Claude Code again, before sending any new message.
  4. Check the usage indicator (context window / plan usage limits panel).

Expected behavior
Usage counter should start at 0 (or close to 0) immediately after reset, since no requests
have been made in the new window yet.

Actual behavior
Usage counter shows a substantial amount already consumed (e.g. 80k-100k tokens / ~57-59%
of weekly budget) despite zero activity since the reset.

Environment

  • Claude Code desktop app
  • Plan: Pro
  • Platform: ОС Linux]

<img width="805" height="1076" alt="Image" src="https://github.com/user-attachments/assets/8100831f-f956-4969-bd64-336c2b3b8e7b" />
<img width="805" height="1076" alt="Image" src="https://github.com/user-attachments/assets/3342821f-5ade-46c2-b6b7-3112cfc49efc" />

What Should Happen?

Usage counter should start at 0 (or close to 0) immediately after the reset, since no requests have been made in the new window yet. Instead, it shows a significant chunk already consumed (e.g. 80k-100k tokens, or ~57-59% of the weekly limit) right after reset, with zero activity in between.

Error Messages/Logs

No console error or crash — this is a display/accounting discrepancy in the usage limit UI panel, not a runtime error. See attached screenshots for the exact numbers shown before and after reset.

Steps to Reproduce

  1. Use Claude Code until the 5-hour usage limit is reached / blocked.
  2. Wait for the limit to reset (shown in the UI countdown, e.g. "Resets Thu, Aug 13, 3:00 PM").
  3. Open Claude Code again, before sending any new message.
  4. Check the usage indicator (context window / plan usage limits panel).

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.206

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Other

Additional Information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗