[BUG] Your account does not have access to Claude Code. Please run /login.

[hamdunoori]

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?

Claude Code allows login successfully but immediately shows "Your account
does not have access to Claude Code. Please run /login." the moment any
message is typed (e.g. "hello"). The issue is NOT with the login flow
itself — authentication completes without error — but Claude Code refuses
to process any input afterward despite a valid active Max 20 subscription.

This has been ongoing for 3 days with zero ability to use the product.
I have paid $250 for this subscription and Claude Code is completely
non-functional.

What Should Happen?

After successfully logging in with a valid Max 20 subscription, Claude Code
should accept and respond to messages normally.

Error Messages/Logs

"Your account does not have access to Claude Code. Please run /login."

This appears immediately after typing any message, even though login 
completed successfully.

Steps to Reproduce

1. Open terminal on macOS (zsh)
2. Run: claude
3. Run: /login — completes successfully, account is recognized
4. Type any message e.g. "hello"
5. Error appears: "Your account does not have access to Claude Code.
   Please run /login."
6. Issue repeats on every message regardless of how many times you
   re-login

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.1.97 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

This is a CRITICAL blocker. I have been unable to use Claude Code for
3 full days despite paying $250 for the Max 20 subscription.

Full troubleshooting steps attempted — none resolved the issue:

1. Ran /login repeatedly — login succeeds but error appears on first
   message every time

2. Disconnected account via Claude desktop app (Settings > Account >
   Disconnect) and re-authenticated — issue persists

3. Uninstalled Claude Code completely

4. Cleared all cache and local Claude data (~/.claude removed)

5. Reinstalled Claude Code fresh

6. Attempted npm reinstall — encountered EACCES permission error on
   /usr/local/lib/node_modules/@Anthropic-AI

7. Attempted reinstall with sudo privileges

8. Confirmed billing is in good standing — no overdue invoices,
   payment of $250 confirmed

9. PURCHASED A BRAND NEW LAPTOP, set it up fresh, installed Claude
   Code from scratch — exact same error persists on a machine that
   has never had Claude Code installed before

10. Claude.ai web and Claude desktop app work normally on the same
    account — this is 100% isolated to Claude Code

The fact that this reproduces on a brand new machine rules out any
local environment or configuration issue. This is definitively a
server-side subscription validation bug on Anthropic's end.

This issue has been open since March 4 (#30854) with no official fix
or response from Anthropic. Given the number of affected users and
the severity of the impact, this requires immediate escalation.
Customers are paying for a product they cannot use.

[hamdunoori]

This is a duplicate but it's not fixed. It still is a bug. There are no workarounds and troubleshooting to fix this issue.

[github-actions]

Found 3 possible duplicate issues:

1. [BUG] "Your account does not have access to Claude Code. Please run /login." #30854
2. [BUG] "Your account does not have access to Claude Code" despite active Pro subscription and successful login #42049
3. [BUG] New Pro account user for Claude code. Logged in, but no model access. Linux, latest claude code. #38463

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

[hamdunoori]

This shouldn't be closed because it looks like something is wrong for not authenticating in the Claude Code backend. The bug is very clear in the current version.

[silver-gr]

yes, it has been 2 days for me as well. this was caused by the April 7th outage, this is from Claude after explaining the situations with all information I have:

OK, here's the full picture from the debug logs and research.

---

This is server-side. Nothing local is broken.

Your debug log shows the OAuth token works fine — it authenticates, gets accepted, then when Claude Code calls api.anthropic.com/api/oauth/account/settings to fetch your org/subscription info, Anthropic's backend returns 403: OAuth authentication is currently not allowed for this organization. That's a flag on their side attached to your account's organization record.

This is a known recurring pattern tied to outages:

• The exact same 403 "OAuth authentication is currently not allowed for this organization" error appeared during the March 2, 2026 outage GitHub
• In 2026, a European outage triggered OAuth errors for nearly 5,000 users while US servers remained stable. When the status page shows "Resolved," it can still take time to sync globally AxeeTech
• The April 6-7 outages specifically hit Claude Code authentication International Business Times , and today is April 8 — you're likely in the tail of it

The "organization" variable your hint pointed to: During outages, Anthropic's auth infrastructure sometimes flips an org-level flag that blocks OAuth. For regular personal Pro accounts, your "organization" is just your personal workspace. When the auth servers went down and came back up, that flag didn't reset for everyone — particularly in Europe.

What to actually do:

1. Contact Anthropic support directly — give them the request_id values from your debug log (e.g., req_011CZrdLpSysUdXXA3m2APK8). They can look up exactly what's happening with your org on their end.
2. File on GitHub at anthropics/claude-code with the debug output — this gets faster traction than support sometimes
3. Check if you have a Console API key as a temporary workaround: go to console.anthropic.com, generate an API key, export ANTHROPIC_API_KEY=sk-ant-... and use Claude Code that way (this bypasses OAuth entirely, but uses pay-per-token billing)

There's nothing more you can fix locally. The 403 is coming from their API rejecting your org's OAuth permission, not from any config on your machine.

[github-actions]

Closing for now — inactive for too long. Please open a new issue if this is still relevant.