claude-code - 💡(How to fix) Fix [BUG]Claude Code shows "Login successful" with valid Max plan but all requests fail with "Your account does not have access to Claude Code" [1 comments, 1 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#52955Fetched 2026-04-25 06:16:15
View on GitHub
Comments
1
Participants
1
Timeline
5
Reactions
0
Author
Participants
Timeline (top)
labeled ×4commented ×1

Error Message

Running /login repeatedly shows "Login successful" each time, but the next message fails with the same error. This appears to be the same backend entitlement bug as issue #47130. Claude Code should process my requests normally using my active Max plan, the same way Claude.ai web chat does. Login status and request authorization should be consistent — if login shows "successful" with an active Max subscription, requests should not be rejected with an access error.

Error Messages/Logs

  1. Error: "Your account does not have access to Claude Code. Please run /login."
  2. Send another message → same error repeats indefinitely

Code Example

Your account does not have access to Claude Code. Please run /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?

Claude Code recognizes my Max plan and confirms "Login successful," but every request fails with: "Your account does not have access to Claude Code. Please run /login."

Running /login repeatedly shows "Login successful" each time, but the next message fails with the same error. This appears to be the same backend entitlement bug as issue #47130.

What Should Happen?

Claude Code should process my requests normally using my active Max plan, the same way Claude.ai web chat does. Login status and request authorization should be consistent — if login shows "successful" with an active Max subscription, requests should not be rejected with an access error.

Error Messages/Logs

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

Steps to Reproduce

  1. Open Claude Code in desktop app
  2. Send any message (e.g., "hi")
  3. Error: "Your account does not have access to Claude Code. Please run /login."
  4. Run /login → shows "Login successful"
  5. Send another message → same error repeats indefinitely

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.119

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Other

Additional Information

<img width="866" height="208" alt="Image" src="https://github.com/user-attachments/assets/d730561b-36e9-4e7f-ab6f-9c851dcada2f" />

extent analysis

TL;DR

The issue may be related to a backend entitlement bug, similar to issue #47130, causing inconsistent login status and request authorization.

Guidance

  • Verify that the issue is indeed related to the backend entitlement bug by checking if other users with Max plans are experiencing the same issue.
  • Try clearing cache and cookies, or resetting the Claude Code app to its default state, to see if it resolves the issue.
  • If the issue persists, provide more information about the previous version where the issue was not present, to help identify the regression cause.
  • Check the Anthropic API documentation to see if there are any specific requirements or changes for handling login and request authorization.

Example

No code snippet is provided as the issue seems to be related to a backend bug and not a code-specific problem.

Notes

The issue may be specific to the Opus model or the Windows platform, and more information about the previous working version and the regression cause would be helpful to provide a more accurate solution.

Recommendation

Apply workaround: Given the similarity to issue #47130, it's likely that the issue is related to a backend entitlement bug, and applying a workaround, such as using a different model or platform, may help mitigate the issue until a fix is available.

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