Account panel shows mixed identity: bogus "Claude team" plan label + usage meter tracking a different account

Environment

• Claude Code version: 2.1.220
• Platform: macOS 26.5.1 (Darwin 25.5.0), VS Code extension + CLI
• Auth method: Claude AI (claude.ai OAuth subscription login)

Summary

The account panel (/status → Account section) shows a mixed identity: the email/organization of one account, a plan label that belongs to neither of my accounts, and a usage meter that appears to track the other account.

Setup

I have two separate claude.ai accounts that I switch between on the same machine:

• Account A (personal): Max 20x plan, individual organization ("<email>'s Organization")
• Account B (work): Max 10x plan, company organization

Observed behavior

1. The Account panel shows:

• Email: Account A's email
• Organization: "Account A's Organization"
• Plan: "Claude team" — neither account is on a Team plan (they are Max 20x and Max 10x respectively), so this label matches nothing that exists.

1. The usage meter shows the identical percentage (2%) when viewed from either account, which suggests both views are reading the same underlying account — i.e. usage/rate-limit accounting is attributed to one account while the profile display shows the other.
2. Local ~/.claude.json → oauthAccount is internally consistent for Account A (organizationType: claude_max, organizationRateLimitTier: default_claude_max_20x, billingType: stripe_subscription), so the bogus "Claude team" label does not come from this cached profile — it appears to be resolved elsewhere.
3. After logging in as Account B on claude.ai, the local oauthAccount in ~/.claude.json still shows Account A's profile.

Expected behavior

• The Plan label should reflect the actual plan of the logged-in account (Max 20x or Max 10x — "Claude team" should be impossible here).
• Email / Organization / Plan / usage meter should all describe the same account.
• Usage consumed by sessions on this machine should be attributed to the account shown in the panel.

Impact

Because profile and usage attribution disagree, it is impossible to tell which account's quota is actually being consumed when switching between a personal and a work account on the same machine. Token consumption may be billed to the wrong organization without any visible indication.

I can privately provide account UUIDs / org UUIDs from ~/.claude.json to help correlate, but I'm not posting them in a public issue.