[BUG] Pro subscription not recognized — OAuth login redirects to Upgrade page (Windows)
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?
What's wrong?
I have an active, paid Claude Pro subscription (annual plan, billed to mok4da@bellsouth.net), but Claude Code will not recognize it. When I attempt to log in via the "Claude account with subscription" flow, the OAuth link opens directly to an "Upgrade to Max or Pro" page — there is no login/sign-in option, and I cannot proceed to authenticate.
Environment:
- OS: Windows
- Claude Code version: 2.1.218
- Install method: native installer (irm install.ps1)
- ANTHROPIC_API_KEY: not set
Steps to reproduce:
- Fresh native install of Claude Code on Windows
- Fixed PATH issue (added C:\Users\home\.local\bin per install output)
- Ran
claudein a new PowerShell window - Selected subscription login (not API key)
- Browser opens directly to "Upgrade to Max or Pro" page — no login option present
Troubleshooting already attempted:
- Full PowerShell restart (multiple times)
- Confirmed Pro subscription is active and paid (invoice confirms, billed June 30 2026 – June 30 2027)
- Verified no ANTHROPIC_API_KEY environment variable is set
- Attempted OAuth link in fresh browser session logged into the correct account (mok4da@bellsouth.net)
Expected behavior:
Claude Code should recognize the active Pro subscription and allow login without prompting to upgrade.
What Should Happen?
it should let me sign in
Error Messages/Logs
goes straight to upgrade page.
Steps to Reproduce
welcome to Claude Code
c to copy
place in browser
straight to upgrade page
Claude Model
Sonnet (default)
Is this a regression?
No, this never worked
Last Working Version
_No response_
Claude Code Version
- 1. 218
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Windows Terminal
Additional Information
_No response_
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗