Account switching failure: Server-side session caching prevents switching from Team to personal account

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?

Platform: Cursor IDE (VSCode fork)
Extension: Claude Code for VS Code
OS: macOS (Darwin 23.4.0)
Date: November 2025

Steps to Reproduce
Use Claude Code in Cursor with Team account until credits exhausted
See "used up credits, available November 22" message
Log out of Team account in Cursor
Log in with personal Max account
Open new Claude Code session
Expected Behavior
Claude Code should authenticate with personal Max account and have full credits available
Actual Behavior
Claude Code still reports "used up credits" from old Team account, despite being logged into personal Max account
Troubleshooting Attempted (All Failed)
❌ Logged out and back in multiple times
❌ Deleted Claude Code for VS Code extension completely
❌ Ran rm commands to delete ALL Cursor cache files (not just Claude-related)
❌ Reinstalled Claude Code for VS Code
❌ Essentially reinstalled entire Cursor IDE
❌ Still reports old Team account credit exhaustion
Key Evidence of Server-Side Bug
Claude Code CLI works perfectly with the same personal Max account:
✅ CLI recognizes personal Max account immediately
✅ CLI has full credits available
✅ CLI has been maintaining a single conversation for 3+ days without issues
This proves the credentials are correct and the personal Max account is active. The VSCode/Cursor extension appears to send some persistent identifier (machine ID? extension installation ID? browser fingerprint?) that Anthropic's servers permanently associate with the old Team account session.
Impact
High severity - Users cannot switch accounts even after complete reinstallation, making the extension unusable if they exhaust Team credits and want to use personal account.

(if you can't tell, I used Claude to generate this text! lol.. awesome LLM btw... Anthropic you guys KICK ASS over ChatGPT!)

What Should Happen?

When I un-installed Claude Code for VS Code extension, deleted all my claude and cursor caches, restarted Cursor, re-installed Claude Code for VS Code, logged in (/login) into my personal Max account, and opened a new Claude tab, Claude should have be available to respond to my prompts (as a check, Claude Code CLI was working just fine, able to respond to my prompts; CC CLI was using my login to my personal Max account). Instead Claude returns the message of not being available until some 3 days later (because I've run out of credits) which occurred when I was logged into Claude with my Teams account (which I had used up my credits). (i.e. Claude Code Cursor extension should have recognized and used my personal Max account, not effectively get "stuck" on my Team account (or at least not have your servers clear out that credits exceeded message when I switch accounts).

Error Messages/Logs

See my description of what should happen. it's the message of Claude not being available until some future date because I ran out of credits on that Teams account, even though I switched to my personal Pro account.

Steps to Reproduce

1. Within a Claude tab in Cursor (using the Claude Code in Cursor (CC4VSC) extension) logged into your Claude Team account, use up all your credits on a Team account until CC no longer responds to your prompts except with the message that the service will not be available until some future date.
2. do everything under the sun to clear out all caches and the CC4VSC extension so that neither Cursor nor the CC4VSC has any awareness of the current history (make sure you expend the requisite 2-3 hours figuring out (with claude.ai btw using my personal Max account) all possible methods of getting CC4VSC to recognize a different Claude login)
3. re-launch Cursor, re-install the CC4VSC extension, re-login with /login (actually I think the login page pops up automatically at this point), log into your brand new (just subscribed mucho dinero) personal Max account. and then then provide Claude Code any prompt (like "Are you available?")
4. observe that Claude Code continues to not respond to your prompts except with the message that the service will not be available until the same future date.
5. launch a new terminal, run Claude to open up the Claude Code CLI, login to the personal Max account (again, freshly subscribed), and put in any prompt... and see that Claude Code responds as expected (i.e. it's not out of credits, i.e. using the correct account)

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.0.53 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

You probably don't want pictures of my damaged drywall. J/K