[BUG] Claude Code shows "Auth token: none" after successful OAuth login — hasAvailableSubscription stays false despite active Pro subscription (macOS)

Found 3 possible duplicate issues:

1. https://github.com/anthropics/claude-code/issues/35877
2. https://github.com/anthropics/claude-code/issues/46847
3. https://github.com/anthropics/claude-code/issues/45922

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

Found 3 possible duplicate issues: 1. [[BUG] hasAvailableSubscription: false despite active Max subscription #35877](https://github.com/anthropics/claude-code/issues/35877) 2. [[BUG] Claude Code on macOS does not recognize active iOS Apple-billed Max subscription, login succeeds but CLI says account has no access #46847](https://github.com/anthropics/claude-code/issues/46847) 3. [[BUG] Active Max subscription not recognized — subscriptionType: null, cannot authenticate #45922](https://github.com/anthropics/claude-code/issues/45922) This issue will be automatically closed as a duplicate in 3 days. If your issue is a duplicate, please close it and 👍 the existing issue instead To prevent auto-closure, add a comment or 👎 this comment 🤖 Generated with Claude Code

Not a duplicate of the suggested issues. Key distinguishing factors:

• #35877 and #45922 describe accounts with a single subscription. My case involves an account that had BOTH an active Pro subscription AND a separate Console (API) organization on the same email — the OAuth flow always defaulted to the Console org, not the Pro subscription. Deleting the Console organization did not resolve the issue, indicating a stuck server-side entitlement flag.

• #46847 is specific to Apple App Store-billed (iOS) subscriptions. My subscription is Stripe-billed via web (billingType: "stripe_subscription" in ~/.claude.json), not Apple.

The closest match is #39445, which describes the same root cause (wrong OAuth client_id for accounts with both Max subscription and Console org) but is Windows-specific. My issue confirms the same bug affects macOS.

Additionally, unlike the suggested duplicates, my issue has a concrete reproducible side effect on the VS Code extension: it shows "Failed to retrieve auth status after login" in an infinite loop, making the extension completely unusable.

Please keep this issue open — it captures a macOS + Pro + Console-org combination that is not represented in the suggested duplicates.

Update with deep diagnostics:

~/.claude/.credentials.json file is NOT created during OAuth (same as #34262)
Token IS stored in macOS Keychain as "Claude Code-credentials"
Keychain entry contains valid OAuth token with subscriptionType: "pro" and rateLimitTier: "default_claude_pro" (after manual correction from default_claude_ai)
Despite correct local state, CLI still returns "Not logged in" and header shows "API Usage Billing"
Server-side token validation appears to reject the token entirely, not a client config issue

Conclusion: purely server-side entitlement sync bug. Local troubleshooting exhausted.

Same issue here. credentials.json shows subscriptionType: "pro"
but UI displays "API Usage Billing" and all models fail.
Account: ander.jbc115@gmail.com
Platform: Windows 11, Claude Code v2.1.119
Worked on another laptop April 21-22, broken on new laptop.

Update: Account banned for attempting workaround to Anthropic's own server-side bug
After nearly 2 weeks without any resolution from Anthropic support (no human response to support tickets, GitHub issue auto-closed as duplicate), I cancelled my Pro subscription and received a refund.
Following advice from other users in similar GitHub issues and discussions, I attempted to work around the server-side entitlement bug by creating a fresh subscription on a secondary email address — hoping that a clean account without the Console organization history would authenticate properly.
Result: immediate account ban after payment.
I am now in a catch-22:

Original account ([sulya2690@gmail.com](mailto:sulya2690@gmail.com)): Claude Code authentication broken due to Anthropic's server-side entitlement sync bug. Subscription cancelled, refund issued.
New account ([alexander.ulian@gmail.com](mailto:alexander.ulian@gmail.com)): Banned immediately after Pro subscription payment — presumably flagged as a duplicate/suspicious account.

I cannot use the service due to a technical issue on Anthropic's side that they have failed to fix despite extensive troubleshooting and multiple support requests. I cannot create a new subscription to work around the bug because doing so violates platform policies and triggers an automatic ban.
Money spent. No working service. No support response. Just an automated refund and a ban.
I genuinely enjoy working with Claude Code. This is the most frustrating user experience I have ever had with a paid software product. The tool itself is excellent — but Anthropic's complete lack of human support for a known, documented, reproducible server-side bug affecting paying subscribers is unacceptable.
To Anthropic engineering:
Please either:

Fix the server-side entitlement sync bug that affects accounts with both Pro subscriptions and former Console organizations (issues #17402, #35877, #39445, #46847, #34262), OR
Provide a supported way for affected users to migrate to a clean account without triggering anti-fraud bans, OR
At minimum, respond to support tickets with actual troubleshooting steps or timeline estimates instead of radio silence

This issue has now cost me 2 weeks of time, $24 in wasted subscription fees (refunded), frustration with a second banned account, and complete loss of trust in Anthropic's customer support.

UPDATE — Resolved! Root cause found.

After ~2 weeks of debugging including a full subscription cancellation, refund, and creating a brand new Pro account on a different email — the issue is not a server-side entitlement bug. It's a duplicate of #49659.

Root cause: the env block in ~/.claude/settings.json containing
CLAUDE_CODE_* variables completely breaks OAuth on macOS:

{
  "env": {
    "CLAUDE_CODE_AUTO_COMPACT_WINDOW": "400000",
    "CLAUDE_CODE_SIMPLE": "1"
  },
  "model": "opus[1m]",
  "theme": "dark"
}

I never set these manually — they appeared from a Claude Code beta/onboarding flow at some point. They are unrelated to authentication, but they silently break it.

Fix: remove the env block from ~/.claude/settings.json:

python3 -c "
import json
p = '$HOME/.claude/settings.json'
d = json.load(open(p))
d.pop('env', None)
json.dump(d, open(p, 'w'), indent=2)
"

After this — auth worked instantly on first try, both in CLI (claude --print "hi" returned "Hi") and in the VS Code extension. No re-login needed.

What was misleading along the way

1. /status showing Auth token: none made it look like a Keychain/token-persistence problem. The token was correctly stored in Keychain — Claude Code just wasn't reading it because the env block somehow broke the auth flow before it ever got there.

1. hasAvailableSubscription: false and "API Usage Billing" header — red herrings. They reset to false on every launch but are not the cause; the real cause was upstream of subscription detection.

1. Reproduces on a completely fresh account (different email, no Console org, no prior config) — which is why I initially concluded it must be server-side. It wasn't. It was the same settings.json (carried across both accounts because ~/.claude/settings.json is per-machine, not per-account).

1. /doctor reports the install as healthy. There is no diagnostic that points at settings.json.

Suggestion to Anthropic

Please consolidate this with #49659 and prioritize. The failure mode is brutal:

• No error message mentions settings.json
• The variables involved have nothing to do with auth
• Keychain looks fine, install looks fine, OAuth flow completes successfully
• I cancelled my Pro subscription, requested a refund (granted), opened a new Pro on a second email — and the new account banned within minutes (separate issue), all because the actual one-line fix was hidden in a config file no one mentioned.

Two weeks of debugging, two subscription cycles, support tickets, and a banned account — for a config file env block.

Environment for completeness:

• macOS Apple Silicon (Sonoma)
• Claude Code v2.1.123 (also reproduced on v2.1.112)
• Node.js v22.22.2
• VS Code extension v0.40.2

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.