/status shows wrong email when pane is authenticated to a Team org via a different login identity

Summary

/status displays the same email in two panes even when they are authenticated
to different Anthropic accounts (e.g. a personal Max subscription and a Team
membership that is accessible only via a different login identity). The "Login
method" field and rate-limit quotas correctly differ — confirming the tokens
really are for different accounts — but the email string misrepresents one pane.

Setup

• Two Anthropic identities: A (personal) and B (work).
• A has a Max subscription on its own org.
• B has Team access to an org; A does NOT have access to that Team org

(verified by signing into claude.ai separately with each — only B sees the
Team org in the org-picker).

• macOS, Claude Code 2.1.112.
• Goal: run two panes in parallel, each authenticated to a different account.
• Implementation: per-pane CLAUDE_CONFIG_DIR (~/.claude-A, ~/.claude-B),

each with its own .credentials.json obtained via /login in that pane.

Reproduction

1. Sign into claude.ai as identity A in the browser.
2. Start a shell with CLAUDE_CONFIG_DIR=~/.claude-A, run claude, /login.
3. Sign out of claude.ai, sign in as identity B.
4. Start a shell with CLAUDE_CONFIG_DIR=~/.claude-B, run claude, /login.
5. Keep both panes open concurrently. Run /status and /usage in each.

Expected

• Pane A /status shows email A.
• Pane B /status shows email B.

Actual

• Both panes show email A in /status.
• Login method correctly differs: "Claude Max account" vs "Claude Team account".
• Organization field is identical in both (also suspicious — if these are

different accounts, the org string should differ).

• /usage shows different weekly reset times in the two panes, confirming

the backend treats them as distinct accounts with independent quotas.

Why it matters

Users rely on /status to confirm which account is active. A wrong email
display silently obscures misconfiguration — e.g. a user may believe they're
on account B while actually billing account A. This is especially confusing
when setting up dual-account parallel workflows.

Workaround

None at the Claude Code level. Users can infer the real account only by
comparing /usage reset times across panes, or by cross-referencing the
active org in claude.ai browser.