[BUG] "Claude will return soon" Claude-code down?
Status Fixed / completed
Reported on v2.1.112
Maintainer reply None cached
Activity 8 comments · opened Apr 30, 2026 · closed Apr 30, 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?
claude status page states claude-code is operational whilst i got hit with this error?
is anyone else experiencing the same thing? or is it just my account auth issue?
What Should Happen?
Operational claude code contradicts error message 403 error
Error Messages/Logs
Please run /login · API Error: 403 {"type":"error","error":{"type":"permission_error","message":"Account is no longer a member of the organization associated with this token."},"request_id":"**REDACTED**"}
Steps to Reproduce
Use claude-code in cli
Claude Model
Sonnet (default)
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
2.1.112
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Warp
Additional Information
<img width="1673" height="953" alt="Image" src="https://github.com/user-attachments/assets/6b436124-9726-4e1d-9360-15484dd8dd8e" />
8 Comments
yes.
<img width="1013" height="346" alt="Image" src="https://github.com/user-attachments/assets/4b067eb0-1c39-444e-bf41-821bc380f096" />
Mb i thought my account got banned or smth
I've run into this problem now, too—it scared me to death! I thought my account had been banned.
<img width="419" height="236" alt="Image" src="https://github.com/user-attachments/assets/93e4659f-bc71-43ed-ba42-f9cd6c734126" />
The 403 "no longer a member of the organization" message reads like an account ban, but in most threads I've seen it isn't one — it's the CLI's cached OAuth token losing its org membership association. Common triggers: token rotation, being removed-then-readded to a workspace (old token still cached), or a plan/seat change on the org side.
Things that have typically cleared it:
/logininside the CLI — drops the cached token and refetches a fresh one tied to current membership.If
/logindoesn't clear it and the admin confirms you're still a member, that's a deeper revocation worth raising with support rather than a CC bug per se.(Not affiliated with Anthropic — sharing what's worked across similar 403-org-member threads.)
So sorry about this!! The issue should be resolved now.
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.