anthropics / anthropics/claude-code

[BUG] Token Usage count

Open
#94,781 1 comment 0 reactions 0 assignees View on GitHub
area:cost bug platform:windows
Dominant language
Python
Stars
145k
Forks
23.1k
PR merge metrics
PR metrics pending

Description

### Preflight Checklist

- [x] I have searched [existing issues](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20state%3Aopen%20label%3Abug) 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?

Why are two different usage counts showing up? I just reset the week, and I'm running out of tokens within 24 hours—yet I’ve used far more than that at other times. The usage displays didn't show anything to trigger that "weekly amount nearing the limit" warning. It makes no sense to have conflicting reports, and I don't know what to go by anymore.

### What Should Happen?

same usage count

### Error Messages/Logs

```shell

```

### Steps to Reproduce

I used Opus yesterday for a strategy task—starting at 10 PM, when my weekly quota reset. Now, I’m using Sonnet much more—and it’s already warning me that I’m close to the weekly limit—just for a single app/game project I’m updating.

### Claude Model

Not sure / Multiple models

### Is this a regression?

Yes, this worked in a previous version

### Last Working Version

2.1.261 (Claude Code)

### Claude Code Version

2.1.261 (Claude Code)

### Platform

Anthropic API

### Operating System

Windows

### Terminal/Shell

Windows Terminal

### Additional Information

_No response_

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the report in Claude Code on Windows Terminal, using Opus and Sonnet around the weekly quota reset. Compare the usage displays with the warning threshold; done means the reported usage and warning state show one consistent count.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.