[BUG] Long-lived token use doesn't recognize Max subscription: "Claude Pro users are not currently able to use Opus in Claude Code. The current model is now Sonnet."

Environment

• Platform (select one):
• [ ] Anthropic API
• [ ] AWS Bedrock
• [ ] Google Vertex AI
• [ x ] Other: Claude Code w/ Long-lived token
• Claude CLI version: 1.0.73 (Claude Code)
• Operating System: MacOS 15.5
• Terminal: Cursor, Warp

Bug Description

Using Claude code with a Long-lived token fails to recognize Claude Max subscription.

Steps to Reproduce

1. Subscribe to Max
2. export $CLAUDE_CODE_OAUTH_TOKEN=<token>
3. Launch Claude
4. See warning: "Claude Pro users are not currently able to use Opus in Claude Code. The current model is now Sonnet."
5. Exit Claude.
6. unset CLAUDE_CODE_OAUTH_TOKEN
7. Launch Claude
8. Max subscription is recognized

Expected Behavior

Since I signed in with my Claude account via OAuth and received a token, I would expect to be authorized for the same level of subscription access as when I sign in normally.

Actual Behavior

I receive the warning: "Claude Pro users are not currently able to use Opus in Claude code. The current model is now Sonnet." And when I run /status, the login method shows "Claude API account".

Additional Context

I don't think that this was happening before this morning's update but I just started using long-lived tokens yesterday.