Claude usage limits can display another account's weekly quota
Maintainer antworten meist innerhalb von 1 Tag
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Anfängerfreundlichkeit
- 45/100
- Issue-Typ
- Bug
- Klarheit
- Größtenteils klar
- Aktivitätsstatus
- Aktiv
- Tech-Stack
- typescript
- Bereich
- authentication, backend
Rechercherichtung
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.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Environment
- macOS (Apple silicon)
- T3 Code Nightly
0.1.11-nightly.20261118.4864 - Claude Code
2.1.328 - Two or more
claudeAgentprovider instances using separate Claude Code configurations and macOS Keychain namespaces. Both accounts use Claude subscription OAuth.
Reproduction
- Set up two Claude provider instances, A and B, with distinct OAuth accounts and separate Keychain namespaces.
- 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%.
- 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, thenget_usagewithskip_behaviors: true. No model prompt is needed. - Observe the weekly result. As a control, change only the cache's account key to an unrelated value and rerun the probe.
- Separately, after T3 has published a weekly result for B, make the next usage probe return no limits with
rate_limits_available: trueandrate_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.
- Vorherrschende Sprache
- TypeScript
- Sterne
- 24.8k
- Forks
- 6.4k
- Ø Merge
- 4 Std. 29 Min.
- Gemergte PRs (30 T.)
- 488
Entwicklungsumgebung
Startet den Dev-Container des Projekts im Browser, mit Ihrem eigenen GitHub-Konto.
- Kein Dockerfile und keine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus pingdotgg/t3code
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100
Maintainer antworten meist innerhalb von 1 Tag
-
needs more info
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
pingdotgg/t3code#39400 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
[Bug]: Wrapped PR titles lose bottom padding in the thread details panelEvtl. vergeben @iamdatvt94 hat das vor 1 Tag übernommen. Offenbug needs-triage
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
Maintainer antworten meist innerhalb von 1 Tag
-
bug needs-triage
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 66/100
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 73/100
Maintainer antworten meist innerhalb von 1 Tag
Alle Issues in pingdotgg/t3code
Ähnliche Issues
-
area:plugins kind:bug priority:p2 ready
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 90/100
Maintainer antworten meist innerhalb von 1 Tag
-
Escaped `*` followed by `*` (`\**`) never matchesEvtl. vergeben @bardrop hat das heute übernommen. Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 71/100
editorconfig/editorconfig-core-js#172 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
vega/vega-webgpu#40 ·
-
type: bug 🐛
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 63/100
puckeditor/puck#1929 ·
Maintainer antworten meist innerhalb von 1 Tag
-
compression() compresses every response at Brotli quality 11Evtl. vergeben @staylor hat das heute übernommen. Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
Maintainer antworten meist innerhalb von 1 Tag