Thread details shows the local Claude login's usage for a Claude instance routed through a custom ANTHROPIC_BASE_URL

Offen
#39,737 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

@shivamhwp arbeitet bereits daran.

Seit 20.11.2026.

  • #39793 von @shivamhwp — offen

Bewertung

Schwierigkeit
2/5
Geschätzter Aufwand
1-3 Stunden
Anfängerfreundlichkeit
35/100
Issue-Typ
Bug
Klarheit
Klar beschrieben
Aktivitätsstatus
Veraltet
Tech-Stack
typescript

Rechercherichtung

Read apps/server/src/provider/ClaudeProvider.ts where customApiEndpoint is computed and usageLimits is built from capabilities.usage; compare how the custom endpoint is represented with the proposed unavailable reason. Check apps/web/src/components/chat/ThreadDetailsUsage.tsx to confirm the displayed fallback behavior. Done means custom endpoint threads no longer show the local OAuth account’s limits; an open pull request is already linked.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

via-triage
What happened

Thread details → Usage limits always shows Weekly 100% and Weekly · Fable 100% (full bars, % left) and no Session row, in every Claude thread. It never changes as I use Claude. The main limits view shows real, non-zero usage for the accounts that actually serve my requests.

Diagnosis

My Claude requests go through a CLIProxyAPI hub: ~/.claude/settings.json sets env.ANTHROPIC_BASE_URL to the hub. The claude CLI is also signed in with an OAuth Claude subscription that the hub doesn't use for these requests.

ClaudeProvider.ts sees the non-Anthropic base URL and marks the instance as customEndpoint ("First-party account fields cannot verify custom endpoint credentials"). It still publishes capabilities.usage (the CLI's get_usage result) as the instance's usageLimits. get_usage reports the local OAuth login, not the account the custom endpoint routes to. That login is unused, so the instance gets valid-looking limits at 0% used:

"five_hour": null,
"seven_day": { "utilization": 0, "resets_at": "2026-11-26T06:00:00Z" },
"model_scoped": [{ "display_name": "Fable", "utilization": 0 }]

(claude 2.1.329, get_usage control request, captured while the hub accounts were in active use.)

ThreadDetailsUsage renders only the instance's own snapshot, so it shows 100% left for Weekly and Weekly · Fable and drops Session (five_hour: null). The streamed rate_limit_events through the proxy carry no numbers ({"status":"allowed","isUsingOverage":false}), so nothing corrects it during a turn.

This differs from #30990. There the CLI has no OAuth login, so the probe fails and the card says Unavailable. Here the CLI returns a different account's numbers, which look valid. The fallback proposed in #27740 runs only when the instance's limits carry a notice, so it would not trigger here.

Suggested fix: when the Claude instance resolves to customEndpoint, don't attribute the CLI's get_usage result to it. Publish unavailable limits with a reason, so the card reads as unavailable or falls back to the usage hub as in #27740, instead of showing another account's numbers.

Steps to reproduce
  1. Sign the claude CLI in to Claude subscription account A (claude auth login).
  2. In ~/.claude/settings.json, set env.ANTHROPIC_BASE_URL to a CLIProxyAPI hub that serves Claude through other accounts. (My config also sets _CLAUDE_CODE_ASSUME_FIRST_PARTY_BASE_URL=1; I haven't tested without it.)
  3. Use the default claudeAgent instance, with no T3-level env overrides. Add the hub as a cliproxy usage limit source.
  4. Use Claude in a few threads, then open Thread details with Usage limits enabled.

Expected: the limits of the account serving the requests, or Unavailable.
Actual: account A's limits (Weekly 100%, Weekly · Fable 100%, no Session). They never move.

Version

0.1.11-nightly.20261120.4979 (desktop app and local server). Source read at main @ df09ced7.

Environment

macOS (Darwin 27.0), T3 Code (Nightly) desktop app against its local server, Claude Code CLI 2.1.329, CLIProxyAPI hub on the LAN configured as a cliproxy usage limit source.

Evidence
  • Thread details card: Weekly ▬▬▬ 100%, Weekly · Fable ▬▬▬ 100%, no Session row.
  • get_usage output above (trimmed).
  • apps/server/src/provider/ClaudeProvider.ts: customApiEndpoint is computed, then usageLimits is still built from capabilities.usage.
  • apps/web/src/components/chat/ThreadDetailsUsage.tsx: uses the account matching instanceId, else provider.usageLimits.
Related issues

#30990 (same setup, but the card shows Unavailable), #27740 (hub fallback, which only runs when the limits carry a notice), #36297.

Workaround

None in T3. Use Usage → Limits for the hub accounts' real numbers.


Produced by Opus 5.5 (Claude Code) following the T3 Code triage playbook.

Vorherrschende Sprache
TypeScript
Sterne
24.8k
Forks
6.4k
Ø Merge
4 Std. 29 Min.
Gemergte PRs (30 T.)
488

Entwicklungsumgebung

In Codespaces öffnen

Startet den Dev-Container des Projekts im Browser, mit Ihrem eigenen GitHub-Konto.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus pingdotgg/t3code

Alle Issues in pingdotgg/t3code

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.