claude-code - 💡(How to fix) Fix [Feature Request] Distinguish between API key and OAuth subscription billing in startup banner [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

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#54677Fetched 2026-04-30 06:39:04
View on GitHub
Comments
2
Participants
2
Timeline
6
Reactions
0
Author
Timeline (top)
labeled ×4commented ×2

Code Example

[]
RAW_BUFFERClick to expand / collapse

Bug Description ▎ The Claude Code startup banner labels the auth path as "Claude API", which suggests developer-API/credit billing. However, the same wording appears when the session is ▎ authenticated via CLAUDE_CODE_OAUTH_TOKEN (Claude.ai Pro/Max subscription), where usage bills against the subscription plan rather than API credits. ▎ ▎ This is confusing — users can't tell from the banner whether they're consuming API credits or subscription quota. Suggest distinguishing the two (e.g. "Claude API" vs "Claude ▎ subscription / Pro / Max") in the welcome message and/or /status. ▎ ▎ Repro: start claude with only CLAUDE_CODE_OAUTH_TOKEN set (no ANTHROPIC_API_KEY); banner still reads "Claude API".

Environment Info

  • Platform: darwin
  • Terminal: ghostty
  • Version: 2.1.117
  • Feedback ID: a0c2b879-1085-460e-acfe-5ffde6bfba23

Errors

[]

extent analysis

TL;DR

Update the Claude Code startup banner to distinguish between API credit and subscription-based authentication methods.

Guidance

  • Verify the current authentication method (API key or OAuth token) to determine the correct label for the startup banner.
  • Consider adding a conditional statement to display "Claude API" when authenticated via API key and "Claude subscription / Pro / Max" when authenticated via OAuth token.
  • Review the /status endpoint to ensure it also accurately reflects the authentication method.
  • Test the updated banner with both authentication methods to ensure correct labeling.

Example

if auth_method == "API_KEY":
    banner = "Claude API"
elif auth_method == "OAUTH_TOKEN":
    banner = "Claude subscription / Pro / Max"

Notes

This solution assumes that the authentication method can be determined programmatically. If this is not possible, alternative solutions may be necessary.

Recommendation

Apply workaround: update the startup banner to distinguish between API credit and subscription-based authentication methods, as this will provide clarity to users without requiring a full version upgrade.

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

claude-code - 💡(How to fix) Fix [Feature Request] Distinguish between API key and OAuth subscription billing in startup banner [2 comments, 2 participants]