claude-code - 💡(How to fix) Fix Misleading "Claude API" banner when authenticating via CLAUDE_CODE_OAUTH_TOKEN from a Max subscription [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#50786Fetched 2026-04-20 12:13:03
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
Timeline (top)
labeled ×4commented ×1

Code Example

Sonnet 4.6 · Claude API
RAW_BUFFERClick to expand / collapse

When using a long-lived OAuth token generated via claude setup-token (token format sk-ant-oat01-...) and exported as CLAUDE_CODE_OAUTH_TOKEN, the Claude Code startup banner displays:

Sonnet 4.6 · Claude API

…even though the token is subscription-scoped (Max plan) per the authentication docs, and billing actually goes against the subscription, not Console API credits.

Why this matters: The "Claude API" label strongly implies API/Console billing, which is significantly more expensive than subscription quota. Users (myself included) reasonably conclude their SSH sessions are burning API credits and spend time debugging a non-issue. I went through regenerating the token, switching accounts, and inspecting /status before discovering via Anthropic docs that the label is purely cosmetic.

Steps to reproduce:

  1. On a GUI macOS session with an active Max subscription, run claude setup-token
  2. Export the token as CLAUDE_CODE_OAUTH_TOKEN in a non-GUI shell (e.g., over SSH)
  3. Start claude — banner reads "Claude API" instead of the subscription label shown in GUI sessions

Expected: Banner should reflect the actual billing source — e.g., "Claude Max" — when the credential is a subscription-scoped OAuth token.

Environment: Claude Code v2.1.114, macOS (Darwin 25.4.0), SSH session.

extent analysis

TL;DR

The issue can be mitigated by understanding that the "Claude API" label in the startup banner is cosmetic and does not reflect the actual billing source for subscription-scoped OAuth tokens.

Guidance

  • Verify the billing source by checking the Claude documentation and Anthropic docs, which clarify that the label is purely cosmetic.
  • Inspect the token format (sk-ant-oat01-...) to confirm it is a subscription-scoped token.
  • Consider submitting a feature request to update the banner to reflect the actual billing source for clarity.
  • Review the authentication documentation to ensure understanding of how billing is handled for different types of tokens.

Example

No code snippet is necessary for this issue, as it is related to the interpretation of the startup banner.

Notes

The solution to this issue is primarily about understanding the current behavior of the Claude Code startup banner and its implications. The actual fix would involve changing the banner to accurately reflect the billing source, which is not currently possible without updates to the Claude Code application itself.

Recommendation

Apply workaround: Understand and communicate that the "Claude API" label is cosmetic and does not affect billing for subscription-scoped tokens, to avoid unnecessary debugging and concern about API credit usage.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING