Claude usage limits can display another account's weekly quota

未关闭
#39,770 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
45/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
typescript

调研方向

Start by tracing resolveUsageLimitsAfterProbe and the Claude provider usage probe and cache code named in the report. Check how authenticated account identity is obtained, how snapshots are keyed and invalidated, and how probe failures are propagated. Reproduce the mismatched-account and unavailable-response cases from the issue; done means another account's cached quota is never shown as B's fresh usage and failures remain sanitized.

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

描述

Environment

  • macOS (Apple silicon)
  • T3 Code Nightly 0.1.11-nightly.20261118.4864
  • Claude Code 2.1.328
  • Two or more claudeAgent provider instances using separate Claude Code configurations and macOS Keychain namespaces. Both accounts use Claude subscription OAuth.

Reproduction

  1. Set up two Claude provider instances, A and B, with distinct OAuth accounts and separate Keychain namespaces.
  2. In a disposable configuration for B, retain locally cached account metadata from A. Seed a fresh weekly usage cache whose account key also refers to A. Set the cached weekly utilization to a recognizable synthetic value, such as 37.25%.
  3. Launch a Claude Code Agent SDK probe with B's Keychain namespace and the disposable configuration. Disable tools and hooks, use an empty MCP configuration, and disable session persistence. Send initialize, then get_usage with skip_behaviors: true. No model prompt is needed.
  4. Observe the weekly result. As a control, change only the cache's account key to an unrelated value and rerun the probe.
  5. Separately, after T3 has published a weekly result for B, make the next usage probe return no limits with rate_limits_available: true and rate_limits: null, then refresh the provider. This simulates an unavailable usage response. A transient HTTP 429 was also observed during the real incident.

Expected behavior

The usage row for B should show only data associated with B's active OAuth identity. An identity mismatch or an unavailable usage response should produce a clear, sanitized error. A prior sample may be shown as stale only if it is verified to belong to the same active account. It should never appear as a fresh sample for a different account.

Actual behavior

With matching local account metadata and cache keys, get_usage returned the seeded 37.25% from A even though the Keychain credential belonged to B. The same value disappeared when only the cache key was changed. On the live T3 system, B showed A's weekly utilization and reset time. On a subsequent failed probe, T3's resolveUsageLimitsAfterProbe retained the previously published result, so the earlier attribution persisted.

The observed Claude Code cache lookup compared the cache key with local account metadata. The active OAuth credential was verified independently. The process that originally wrote the crossed metadata was not identified. No account identifiers, credential values, or local paths are included in this report.

Suggested changes

  • T3 Code: bind usage snapshots to an authenticated account identity as well as the provider instance, and invalidate unattributed snapshots. Preserve typed, sanitized failure reasons when refreshing.
  • Claude Code: bind cache reads and writes to the active OAuth account and organization. Treat disagreement between local metadata and the active identity as a cache miss.
主要语言
TypeScript
星标
24.8k
派生
6.4k
平均合并
4 小时 29 分钟
30 天内合并 PR
488

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

pingdotgg/t3code 的其他 Issue

查看 pingdotgg/t3code 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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