claude-code - 💡(How to fix) Fix [BUG] Claude Code shows "Auth token: none" after successful OAuth login — hasAvailableSubscription stays false despite active Pro subscription (macOS) [3 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#51971Fetched 2026-04-23 07:40:01
View on GitHub
Comments
3
Participants
2
Timeline
8
Reactions
1
Author
Timeline (top)
labeled ×4commented ×3subscribed ×1

Error Message

Error Messages/Logs

Fix Action

Fix / Workaround

Troubleshooting attempted (all failed):

  • Reinstalled Node.js (v18 → v22) and Claude Code via npm
  • Deleted ~/.claude.json multiple times
  • security unlock-keychain ~/Library/Keychains/login.keychain-db
  • Cleared browser cookies for anthropic.com
  • Deleted all Claude Code tokens in claude.ai Settings → Claude Code
  • Deleted Claude Console organization (had both Pro + Console on same email)
  • Reinstalled VS Code extension
  • Opened VS Code via code . from authenticated terminal session
  • Manually patched hasAvailableSubscription to true in ~/.claude.json

Code Example

Terminal output:
> /status
  Auth token: none

> (any prompt)
  Not logged in · Please run /login

VS Code extension:
  Failed to retrieve auth status after login
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

After successfully completing OAuth login via "Claude account with subscription" on macOS, Claude Code shows "Login successful" but the token is never persisted. /status shows "Auth token: none". The VS Code extension is completely unusable — it shows "Failed to retrieve auth status after login" in an infinite loop.

My account had both an active Pro subscription AND a Console organization on the same email. Deleting the Console organization did NOT resolve the issue — this appears to be a server-side entitlement flag that's stuck.

~/.claude.json contains: "hasAvailableSubscription": false "billingType": "stripe_subscription" "hasExtraUsageEnabled": false

Manually setting hasAvailableSubscription to true does not help — "Auth token: none" persists.

Header shows "Opus 4.7 (1M context) · API Usage Billing" despite selecting sub

What Should Happen?

After completing OAuth flow with "Claude account with subscription":

  1. Token should be persisted (/status should show a valid Auth token, not "none")
  2. hasAvailableSubscription should be set to true
  3. Header should show "Pro subscription" instead of "API Usage Billing"
  4. VS Code extension should inherit the authenticated session
  5. Commands should execute without "Not logged in" errors

Error Messages/Logs

Terminal output:
> /status
  Auth token: none

> (any prompt)
  Not logged in · Please run /login

VS Code extension:
  Failed to retrieve auth status after login

Steps to Reproduce

  1. Run claude /login in Terminal.app
  2. Select "1. Claude account with subscription"
  3. Complete OAuth flow in browser (shows "Build something great. You're all set up for Claude Code")
  4. Terminal shows "Login successful"
  5. Run /status → shows "Auth token: none"
  6. Any command returns "Not logged in · Please run /login"
  7. Open VS Code — extension shows "Failed to retrieve auth status after login"

Troubleshooting attempted (all failed):

  • Reinstalled Node.js (v18 → v22) and Claude Code via npm
  • Deleted ~/.claude.json multiple times
  • security unlock-keychain ~/Library/Keychains/login.keychain-db
  • Cleared browser cookies for anthropic.com
  • Deleted all Claude Code tokens in claude.ai Settings → Claude Code
  • Deleted Claude Console organization (had both Pro + Console on same email)
  • Reinstalled VS Code extension
  • Opened VS Code via code . from authenticated terminal session
  • Manually patched hasAvailableSubscription to true in ~/.claude.json

Claude Model

Not sure / Multiple models

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

v2.1.112

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

Plan: Claude Pro (active, $24/month, renews Apr 19, 2026) Had both Pro subscription AND Console organization on same email. Console org deleted (pending permanent deletion on Apr 23, 2026).

Node.js: v22.22.2 VS Code extension: v0.40.2

Support ticket submitted to Anthropic support chat 5 days ago — no response. Subscription is active and paid, but Claude Code is completely unusable. This is a critical blocker for paid Pro subscribers.

extent analysis

TL;DR

The issue is likely due to a server-side entitlement flag not being updated after deleting the Console organization, causing the authentication token to not be persisted.

Guidance

  • Verify that the subscription status is correctly reflected in the Anthropic API by checking the account settings and ensuring that the Pro subscription is active and not conflicting with any other organizations or subscriptions.
  • Try resetting the Claude Code configuration by deleting the ~/.claude.json file and restarting the application to see if the issue persists.
  • Check the Anthropic API documentation to see if there are any specific requirements or restrictions for using the Claude Code with a Pro subscription and multiple organizations.
  • Consider reaching out to Anthropic support again to request assistance with updating the server-side entitlement flag, as this may be a critical issue for paid Pro subscribers.

Example

No code snippet is provided as the issue seems to be related to the Anthropic API and server-side configuration.

Notes

The issue may be specific to the Anthropic API and Claude Code configuration, and further investigation may be required to determine the root cause. The fact that deleting the Console organization did not resolve the issue suggests that there may be a server-side flag or setting that needs to be updated.

Recommendation

Apply workaround: Reach out to Anthropic support to request assistance with updating the server-side entitlement flag, as this may be a critical issue for paid Pro subscribers.

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