[BUG] macOS v1.0.51: Claude Max users incorrectly treated as Pro users - Cannot access Opus model

Usage has been cut in half and dumbed down. Inside info is they are using their servers to prioritize training for sonnet 4.5 to launch at the same time as xAI dedicated coding model. xAI coding logic is very close to sonnet 4 and has anthropic scrambling. xAI sucks at making designs but codes really well.

What the hell? This and the constant overload errors makes Claude Code a pretty bad deal to me.

Not limited to Claude code. I code with the desktop app plus mcp. The difference now vs a few weeks ago is stark.
1: the amount of tokens for one conversation dropped. Can't quantify it but it's there and it's extremely frustrating. I would bet I spend 25% of each conversation getting Claude back on track.
2: the amount of tokens or time per allowed time period has dropped as well.
What I find disingenuous is that terms say both of these will change with overall use of anthropic AI at any one point in time. This is now across the board meaning anytime I try to code from 8am to midnight I experience this. I don't believe overall usage of anthropic AI increased permanently and drastically all at once. If this felt like a slowly building amount of time and tokens that would feel organic and I would be inclined to believe it. This was immediate.
I would even be okay with anthropic saying "hey we've thankfully experienced a huge influx of users and we're working on expanding our capabilities. Please give us a little grace." But no. So, to me disingenuous is dishonest and I really don't like being lied to.

What I did to fix it...
1- removed completlly cloude-code, includin .claude.json from Users directory
2- reinstalled but choosing the version 1.0.33 npm install -g @anthropic-ai/claude-code@1.0.33
3- loged in normally

By the way, not only Claude Max users, but Pro users as well can access opus-4. I am a pro user, and see the same bug.

At least for me it got fixed on version 1.0.58

______________________________________________
Felipe Castro

Celular: (55) 99156 3083
http://www.linkedin.com/in/felipefcastro

Em sex., 25 de jul. de 2025 às 07:11, yu @.***>
escreveu:

yu-tomori left a comment (anthropics/claude-code#3566) <https://github.com/anthropics/claude-code/issues/3566#issuecomment-3117183799> By the way, not only Claude Max users, but Pro users as well can access opus-4. I am a pro user, and see the same bug. — Reply to this email directly, view it on GitHub <https://github.com/anthropics/claude-code/issues/3566#issuecomment-3117183799>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFUSMIBJ73HZH7SOAMHSBC33KH7DXAVCNFSM6AAAAACBSMO6XSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCMJXGE4DGNZZHE> . You are receiving this because you commented.Message ID: @.***>

I am a Max user and I can no longer access Opus-4.

<img width="977" height="76" alt="Image" src="https://github.com/user-attachments/assets/52902203-1230-43dc-b6d3-a71158a829c2" />

I am a Max user and I can no longer access Opus-4. <img alt="Image" width="977" height="76" src="https://private-user-images.githubusercontent.com/24284329/471174785-52902203-1230-43dc-b6d3-a71158a829c2.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NTM1OTkwMDQsIm5iZiI6MTc1MzU5ODcwNCwicGF0aCI6Ii8yNDI4NDMyOS80NzExNzQ3ODUtNTI5MDIyMDMtMTIzMC00M2RjLWI2ZDMtYTcxMTU4YTgyOWMyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTA3MjclMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwNzI3VDA2NDUwNFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTNmZTNkMGMyYzczNjBmOGViNDhkODEwMzY3ZWIzZTcxMmM3M2I2YzcwM2I1MDc2OGE3MmNmMzdkNzllOWFjYTYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.U0UvU_tGyKYkGPmSdWCzWuzlCxlofiFk-fFtZkFDtHU">

oh this is bug on cc
last time I also facing this issue,relogin will resolve it

oh this is bug on cc last time I also facing this issue,relogin will resolve it

Still getting the same issue.

Whats your cc version?

______________________________________________
Felipe Castro

Celular: (55) 99156 3083
http://www.linkedin.com/in/felipefcastro

Em dom., 27 de jul. de 2025 às 15:50, Sam Lazrak @.***>
escreveu:

samlazrak left a comment (anthropics/claude-code#3566) <https://github.com/anthropics/claude-code/issues/3566#issuecomment-3124657332> oh this is bug on cc last time I also facing this issue,relogin will resolve it Still getting the same issue. — Reply to this email directly, view it on GitHub <https://github.com/anthropics/claude-code/issues/3566#issuecomment-3124657332>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFUSMIDEAIG3IP2UNM2BS433KUNOHAVCNFSM6AAAAACBSMO6XSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCMRUGY2TOMZTGI> . You are receiving this because you commented.Message ID: @.***>

same problem anyone have a solution?? or have they fixed it ??

same problem anyone have a solution?? or have they fixed it ??

Have you tried to cd into ~/.claude and rm -rf .credentials.json and then _after opening a new terminal_ starting claude again and then going thru /login process and then checking /status?

> same problem anyone have a solution?? or have they fixed it ?? Have you tried to cd into ~/.claude and rm -rf .credentials.json and then _after opening a new terminal_ starting claude again and then going thru /login process and then checking /status?

Yes, it appears to only have sonnet and

**Guide: Fixing Claude CLI (Claude Code) Subscription and Model Access Issues on Windows**

The Problem

You have a paid Claude Pro or Max subscription, which should grant you access to premium models like Opus.
However, when you use the claude-code command-line tool, you experience one or more of the following
issues:

• The CLI defaults to the Sonnet model, and you cannot access Opus.
• The CLI gives an error message stating that "Claude Pro users are not currently able to use Opus 4 in

Claude Code."

• The CLI seems to be using a developer API key instead of your subscription, potentially incurring

unexpected costs.

• The login process is confusing and doesn't seem to recognize your subscription tier.

The Root Cause: Credential and Configuration Conflicts

This issue is not a bug in the tool itself but a deep-seated credential conflict on your machine. The
claude-code CLI can authenticate in two different ways:

1. Claude.ai Account (Subscription): This is the method for Pro/Max users. It uses a browser-based login to

link to your claude.ai account.

1. Anthropic Console Account (API Key): This is the method for developers using the API on a pay-as-you-go

basis. It typically relies on an ANTHROPIC_API_KEY set in your system's environment variables.

The problem arises when the CLI finds traces of both authentication methods on your system. It gets
confused and often prioritizes an old, leftover API key or a cached login token over your active
subscription. A standard uninstall/reinstall does not fix this because it fails to remove these residual
configuration files and environment variables.

The Solution: A Complete System Deep Clean

To solve this, you must manually and thoroughly purge every trace of Claude's configuration from your
system before performing a clean installation and a targeted login.

Step 1: Uninstall All Claude-Related Packages

First, remove the official packages to get rid of the main application files.

1 # Uninstall the main CLI tool
2 npm uninstall -g @anthropic-ai/claude-code
3
4 # Uninstall the Python SDK if it exists
5 pip uninstall claude-code-sdk -y

Step 2: Purge All Configuration and Cache Folders

This is a critical step that a standard uninstall misses.

1 # Remove the main Claude Roaming AppData folder
2 Remove-Item -Path "$HOME\AppData\Roaming\Claude" -Recurse -Force -ErrorAction SilentlyContinue
3
4 # Remove the Claude CLI cache in Local AppData
5 Remove-Item -Path "$HOME\AppData\Local\claude-cli-nodejs" -Recurse -Force -ErrorAction
SilentlyContinue
6
7 # Remove the user-level JSON configuration files
8 Remove-Item -Path "$HOME\.claude.json", "$HOME\.claude.json.backup" -Force -ErrorAction
SilentlyContinue
9
10 # Remove any temporary files created by the CLI
11 Remove-Item -Path "$HOME\AppData\Local\Temp\claude-*-cwd" -Force -ErrorAction SilentlyContinue

Step 3: The Most Critical Step - Delete Environment Variables

This is the most common source of the conflict.

1. Press the Windows Key, type env, and select "Edit the system environment variables".
2. In the window that opens, click the "Environment Variables..." button.
3. Carefully inspect both the "User variables" (top section) and "System variables" (bottom section).
4. Select and Delete any variable that starts with ANTHROPIC_ or CLAUDE_. Common culprits include:

• ANTHROPIC_API_KEY
• CLAUDE_CODE_OAUTH_TOKEN
• CLAUDE_CLI_ACTIVE
• CLAUDE_CODE_BIT_BASE

1. Click OK on all windows to save your changes.

Step 4: Restart Your Terminal

This is mandatory. Environment variable changes will not apply until you close your current terminal and
open a brand new one.

Step 5: (Optional) System Integrity Check

To be absolutely sure your environment is clean, you can run Windows' built-in system repair tools from a
new terminal with Administrator privileges.

1 # First, repair the component store
2 DISM /Online /Cleanup-Image /RestoreHealth
3
4 # Then, scan and repair all protected system files
5 sfc /scannow

Step 6: Reinstall the CLI

Now, from your new, clean terminal (preferably from your user home directory C:\Users\<Your-Username>),
reinstall the tool.

1 npm install -g @anthropic-ai/claude-code

Step 7: The Correct Login Procedure

This is the final piece of the puzzle.

1. Run the Claude CLI:

1 claude

1. The tool should now present a clear choice. Select the option for "Claude account with subscription".

1 Select login method:
2
3 > 1. Claude account with subscription
4 2. Anthropic Console account

1. Complete the login process in your web browser as prompted.

Step 8: Verification

Once logged in, you will be in the interactive shell. Run the /status command to confirm your setup.

1 /status

The output should now correctly show:

• Login Method: Claude Max Account (or Pro)
• Model: ... (currently Opus)

You can now use Opus. Congratulations

> oh this is bug on cc > last time I also facing this issue,relogin will resolve it Still getting the same issue.

check at the bottom of this post i found the answer

This bug is still open and I can't use my Max 5x account. It acts like a Pro account and has the same limits with Pro. But when I try to upgrade, I see that I'm already on Max 5x, and my invoice and bank account statements say the same thing. Is there really no solution to this bug? It's a shame.

@MabuhayDesignsandCo Sent me in the right direction. After having run into this on a MAX plan, I simply logged out, ran unset CLAUDE_CODE_OAUTH_TOKEN, then logged back in. This fixed my issue and brought back the Opus model. I believe I set that a couple of days ago when having authentication issues and it was the only way I could get connected.

@MabuhayDesignsandCo Sent me in the right direction. After having run into this on a MAX plan, I simply logged out, ran unset CLAUDE_CODE_OAUTH_TOKEN, then logged back in. This fixed my issue and brought back the Opus model. I believe I set that a couple of days ago when having authentication issues and it was the only way I could get connected.

Above worked for me, thanks

Mine was specifically not working over SSH due to (I believe) Claude Code no longer using the ~/.claude/.credentials.json file, but only the login keychain.

I created a long-lived token & put it in the credentials format in ~/.claude/.credentials.json and also persisted it to the login keychain and it's been working now for me.

Ensure you don't still have the CLAUDE_CODE_OAUTH_TOKEN env var set.

Perhaps they'll fix the issue over SSH, but if not, I made a small script that has you generate the token and then saves it where it's supposed to go.

https://gist.github.com/matthewevans/a1d8b49a02f56aa2d866cc2044af1990

I added a long lived token using

claude setup-token
....
✓ Long-lived authentication token created successfully!

Your OAuth token (valid for 1 year):
...
Store this token securely. You won't be able to see it again.

Use this token by setting: export CLAUDE_CODE_OAUTH_TOKEN=<token>
```` 
and was able to authenticate again after my key had expired and I got 401 errors.  But now I also see

Claude Code v1.0.85
L Session ID: a4eb5d73-f9f7-41fd-a7d0-85de0b94fed7

Working Directory
L /Users/me/code/site/wp-content/themes/theme

IDE Integration • /config
✔ Connected to Visual Studio Code extension
✔ Installed VS Code extension

Account • /login
L Login Method: Claude Max Account
L Email: user@domain.com

Memory • /memory
L project: CLAUDE.md

Model • /model
L sonnet (claude-sonnet-4-20250514)

even though I am on the Pro plan

thank you for the reports! this should be resolved now

I´m having the same issue. log out didnt solve it. what´s the solution?

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.