anthropics / anthropics/claude-code

[BUG] Weekly limits reset when switching machines

未关闭
#93,551 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
area:cost bug
主要语言
Python
星标
145k
派生
23.1k
PR 合并指标
PR 指标待抓取

描述

### 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_

贡献指南

这个仓库没有索引到贡献指南

调研方向

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.

由索引模型根据 Issue 内容生成。

评估

领域
api
Issue 类型
缺陷
难度
4/5
预计耗时
3-5 天
活跃度
活跃
描述清晰度
需要澄清
新手友好度
30/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。