[BUG] /status displays wrong account/email — session actually authenticated and billed against a different (Enterprise) org

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?

/status showed my session as logged in with my personal email (personal@example.com, org displayed as my own name, "[REDACTED - personal account display name]"), but the session was actually authenticated against a completely different account: my work Enterprise seat (work@company-enterprise.example) in our company's Claude Enterprise org.

All usage was billed against the Enterprise seat's spend limit. I only discovered this when I hit the error "You've hit your org's monthly spend limit" and could not find any spend on either of the two profiles associated with personal@example.com (a personal Max 20x plan and a Team org) — both showed $0.00 spent. The Enterprise org's admin console later confirmed my Enterprise seat (work@company-enterprise.example) was at $200.12 of a $200 custom spend limit.

The only hints in /status that something was off were "Login method: Claude Enterprise account" and "Setting sources: ... Enterprise managed settings (remote)" — while Email showed personal@example.com and Organization showed "[REDACTED - personal account display name]".

This is a serious issue for anyone with access to multiple accounts/orgs: usage silently bills a different organization than the one /status reports, and troubleshooting is very confusing because the displayed account's admin/usage pages show nothing wrong.

What Should Happen?

/status should always display the actual account, email, and organization that the session is authenticated with and billing against. If the credentials belong to a different account/org than expected, that must be visible. Ideally, Claude Code should also warn when the billing org changes or when the logged-in identity differs from the previously displayed one.

Error Messages/Logs

You've hit your org's monthly spend limit · run /usage-credits to raise it, or visit claude.ai/admin-settings/usage

/status output at the time (abridged):
Version: 2.1.199
Session ID: 352ea81c-819d-4028-bba5-daef515d0815
Login method: Claude Enterprise account
Organization: [REDACTED - personal account display name]   <-- personal account name (wrong)
Email: personal@example.com        <-- personal email (wrong; actual billing was work@company-enterprise.example Enterprise seat)
Model: claude-fable-5[1m] (claude-fable-5)
Setting sources: User settings, Enterprise managed settings (remote)

Steps to Reproduce

Exact reproduction is difficult since it involves account state, but this is the sequence that led to it:

1. Have one email (personal) with two claude.ai profiles: a personal Max plan and a Team org.
2. Have a second email (work) that is a member of a Claude Enterprise org.
3. Log in to Claude Code — at some point the stored credentials ended up authenticated against the Enterprise account (work email) while /status displayed the personal email and personal org name.
4. Run /status: it shows Email = personal email, Organization = personal account name, but Login method = "Claude Enterprise account" and Setting sources include "Enterprise managed settings (remote)".
5. Use Claude Code until the Enterprise seat's custom spend limit is hit → error: "You've hit your org's monthly spend limit · run /usage-credits to raise it, or visit claude.ai/admin-settings/usage" — but the displayed (personal) account's admin/usage pages show $0.00 spent and no such limit reached.
6. Confirm in the Enterprise org's admin console that the work-email seat is at its custom spend limit (in my case $200.12 of $200).

Logging out completely (/logout) and logging back in resolved the mismatch.

Claude Model

Other

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.199 (Claude Code)

Platform

Other

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_