Feature request: concurrent personal + work account sessions

Problem

Today Claude Code is signed into exactly one Anthropic account at a time. Switching accounts requires /logout → /login, which:

• Loses the current session's working context (open conversation, in-flight tool calls)
• Forces re-authentication every time you cross the personal/work boundary
• Makes it impractical to keep a personal-account session running alongside a work-account session

Use case

Many developers have both:

• A personal Claude account (Pro/Max subscription, used for personal projects, side work, learning)
• A work Claude account (Team/Enterprise subscription tied to their employer)

Each codebase wants the right account for billing + data-handling reasons:

• Personal repos → personal subscription
• Work/client repos → work subscription (so usage shows up on the right plan, and conversations stay under the org's data agreements)

Right now this means flipping accounts every time you switch repos, with all the friction above. In practice, devs end up just using one account for everything — which either burns personal allowance on work tasks or routes work conversations through a personal account.

What "in parallel" could mean

A few shapes that would solve this — listing options, not prescribing:

1. Per-project account binding — claude reads a project-level config (e.g. .claude/account or a key in .claude/settings.json) that names which signed-in account to use. Multiple accounts can be signed in simultaneously; the per-project setting picks one. No re-auth on directory change.
2. Per-terminal/session account — env var like CLAUDE_ACCOUNT=work selects among signed-in accounts. Lets devs run two terminals, two accounts.
3. Profiles — claude --profile=work / claude --profile=personal. Each profile holds its own login state + settings dir.

Today the closest workaround is ANTHROPIC_API_KEY per-project via .envrc, but that switches you off subscription billing entirely onto pay-per-token, which is a different cost model and often defeats the point of having the subscription.

Why now

As Claude Code adoption grows in workplaces, more devs are hitting this. Mixing personal coding time with work coding time on the same machine is the normal pattern, not the exception.