anthropics / anthropics/claude-code
[BUG] Weekly limits reset when switching machines
- 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?
I've been using Claude Code for the single user for 9 months. I used it on company's notebook with Windows 10 and on my private PC on Ubuntu.
I don't know exact condition to reproduce the bug, but I guess that all it takes is to run a few sessions on one machine, then have a break like 12 hours without asking Claude for anything and run a session on a different machine. Then for some reason weekly limits reset sooner than they should.
### What Should Happen?
Weekly limits should reset only when it said so under the progress bars on the "Usage" window.
### Error Messages/Logs
```shell
```
### Steps to Reproduce
0. Claude's weekly limit starts.
1. Use Claude on one machine
2. Switch to another machine after a few days.
3. Sometimes limits reset before the date under the progress bars tell.
### Claude Model
Not sure / Multiple models
### Is this a regression?
No, this never worked
### Last Working Version
_No response_
### Claude Code Version
1.260907.19 (26090719)
### Platform
Anthropic API
### Operating System
Other
### Terminal/Shell
IntelliJ IDEA terminal
### Additional Information
_No response_
Contributor guide
No contributing guide indexed for this repository
Research direction
The report names no repository file, test, or code entry point; start by locating the Usage window and weekly-limit handling. Use the reported Windows 10 and Ubuntu machine-switch sequence as the first reproduction path, and consider the work done when the displayed reset date matches the actual limit reset across machines.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100