[BUG] Claude VSCode Extension loses Authorization Info

[rangothedog]

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?

My VS Code extension started failing with API Rate Limit errors. Examining .credentials.json my plan has been set to 'null' instead of 'pro'. Logging out of Claude Code and logging in again resets the error, but if you select the 1M token context limit it returns. Selecting the regular Opus option it fixes the problem.

What Should Happen?

Claude Code should properly handle my login and Pro usage limits when running under the 1M token Opus model.

Error Messages/Logs

Steps to Reproduce

Start a Claude Code session in VSCode.
Select Opus model with 1M token context.
Observe your get API Rate Limit errors and your .credentials.json file gets rewritten with a null plan type.
Select Opus model with regular context limit.
Observe your API rate limit errors disappear.

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.63 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

No response

[github-actions]

Found 3 possible duplicate issues:

1. [BUG] API Error: Rate limit reached despite Claude Max subscription and only 16% usage #29579
2. Opus/Sonnet 1M context variants broken on Max 20x — misleading 'Rate limit reached' error #30163
3. Account switches from subscription (i16@i16.jp) to API billing (old account) when tools are used in VS Code extension #28318

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[github-actions]

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.