anthropics / anthropics/claude-code
[BUG] Weekly limits reset when switching machines
- Lenguaje dominante
- Python
- Estrellas
- 145k
- Forks
- 23.1k
- Métricas de merge de PR
- Métricas de PR pendientes
Descripción
### 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_
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Área
- api
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Activo
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 30/100