[BUG] "Your account does not have access to Claude Code. Please run /login."
Resolved 💬 33 comments Opened Mar 4, 2026 by qsimeon Closed May 23, 2026
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
I have an active Max subscription. This is unacceptable. I have run /login many times and selected the account that has the Max subscription. It still says the same thing: "Your account does not have access to Claude Code. Please run /login."
What Should Happen?
I should be able to use Claude Code.
Error Messages/Logs
Steps to Reproduce
>> claude
>> \login
Claude Model
None
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.68 (Claude Code)
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Warp
Additional Information
_No response_
33 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
same issue after upgrade claude code
same issue, does your max plan show up correctly in billing?
<img width="851" height="93" alt="Image" src="https://github.com/user-attachments/assets/f666de69-42ec-416b-b3e8-5a90238d9dc9" />
Also here with the same error. Just checked my invoicing, and there's something due on the 16th of March, issued on the 2nd. No payments have come out of my account, no reason to believe they can't. Max 20.
It's a hard lock considering there's no invoice with no balance to pay.
Same issue here. Suddenly claimed overdue invoice on login attempts, yet status says paid on the website.
This started happening 15 minutes ago maybe, Max account.
For me downgrading the plan and then upgrading back to previously picked plan fixed the issue.
Can confirm, just downgraded to Pro and it's working again. Thanks for the tip @Krizz !
Same issue here. Downgrading the plan, does not change anything
Same issue on Pro.
ping
Same issue on new Pro account. Astoundingly frustrating. Not even an actionable error message.
Hi, I installed Claude Code on a laptop and connected my account.
I worked on coding with Claude Code with that laptop and when I returned to my main desktop PC I had a similar message : "Your account does not have access to Claude. Please login again or contact your administrator."
After trying different things, what allowed me to use Claude Code again was going in Settings → Account → Disconnect so it disconnected my account from both devices and then I logged back in to the app and it worked.
Same issue in Max account. Claude Mac desktop app.
But the bug is not consistent. I was able to get work done in one session, but at the start of another session this starting happening.
There is a little walk through for me with command "$ claude setup-token" [ref], where I reset the env variable "CLAUDE_CODE_OAUTH_TOKEN", and not trying to re-login by "/login" or somewhat related.
It makes me able to operate Claude Code w/ VSC.
But for Claude Code CLI, it still prompts me to login via subscription/console/3rd party, where this might get Claude Code locked.
Same issue pro account. this is annoying.
same issue
I have a Team Plan and Personal max on the same account.
Logging to the max account does not work for me
Claude keeps showing: your account does not have access to claude code
super annoying
same issue on claude code max
Similar issue with Max 20, Claude.ai works fine, Claude chat on desktop app and mobile app work, Claude Code says "Your account does not have access to Claude Code. Please run /login."
same issue with a Pro account... please fix
I have the same issue. It hasn't been working properly since about ten hours ago.
same issue with me, since yesterday
I’m having the same problem on the Pro plan. platform:windows
same issue with me, since today
having same issue here
same issue since yesterday with a Pro account
Same. Re-subscribed to Pro and seeing the issue
i can't use claude code max about 2 days :( pls fix
same issue here
Here's what worked for me:
``
``export CLAUDE_CODE_OAUTH_TOKEN=
``
``claude auth login
I’m having the same problem on the Max 5x plan.
looks like you had different problem/error message maybe?
this is account-level/server-side issue, caused by the outage in April 7th.
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/settingsto fetch your org/subscription info, Anthropic's backend returns403: 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 "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:
request_idvalues from your debug log (e.g.,req_011CZrdLpSysUdXXA3m2APK8). They can look up exactly what's happening with your org on their end.anthropics/claude-codewith the debug output — this gets faster traction than support sometimesconsole.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.
Closing for now — inactive for too long. Please open a new issue if this is still relevant.
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.