[BUG]

Status Open
Reported on v2.1.126
Maintainer reply None cached
Activity 0 comments · opened Aug 20, 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?

Title: Active Pro subscription not recognized — /login ends with "Claude Max or Pro is required to connect to Claude Code" (server-side entitlement, status shows Pro)

What's wrong:
I have an active, paid Claude Pro subscription that works normally on claude.ai. The same account has been in continuous use with Claude Code for 12+ months with no change on my end. Claude Code now blocks access despite /status showing the Pro plan.

/status output:

  • Login method: Claude Pro account
  • Email: brittobj@mail.uc.edu
  • Organization: brittobj@mail.uc.edu's Organization

Steps to reproduce:

  1. Run /login
  2. Select "1. Claude account with subscription"
  3. Browser OAuth flow completes successfully
  4. Result: "Claude Max or Pro is required to connect to Claude Code" with an "Upgrade to Max or Pro" button

Troubleshooting already done (none resolved it):

  • /logout, /login repeatedly
  • claude update to latest version
  • Full terminal restart
  • Confirmed no ANTHROPIC_API_KEY set in shell profile or environment
  • Subscription confirmed active on claude.ai under the same email

This matches the pattern in several open issues where the entitlement/access-control layer doesn't sync with an active subscription. The block occurs server-side during OAuth, before any client-side change can affect it. Happy to provide claude doctor output, session IDs, HAR files, or a screen recording.

Environment:

  • Claude Code version: [run claude --version and paste]
  • OS: [your OS]
  • Login method per /status: Claude Pro account

What Should Happen?

Claude Code should recognize my active Pro subscription and let me send messages normally, as it has for the past 12+ months.

Error Messages/Logs

On /login, OAuth completes in browser, then returns: "Claude Max or Pro is required to connect to Claude Code" with an "Upgrade to Max or Pro" button. No local error logs are generated — the block happens server-side during the OAuth entitlement check.

Steps to Reproduce

  1. Open Claude Code
  2. Run /login
  3. Select "1. Claude account with subscription"
  4. Complete OAuth flow in browser
  5. Result: "Claude Max or Pro is required to connect to Claude Code" — despite active Pro subscription

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

Worked on this same account for 12+ months; broke suddenly today, same version, no change to my setup.

Claude Code Version

2.1.126

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Other

Additional Information

Subscription is confirmed active and working on claude.ai right now; issue is isolated to Claude Code. Also affects /mcp auth and normal messages, not just /login.

View original on GitHub ↗