Support multiple account profiles for seamless switching

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Users who belong to multiple Claude organizations (e.g., personal Max plan + enterprise Team plan) must run /logout and /login each time they want to switch accounts. This requires re-authenticating through the browser and SSO provider on every switch. There is no way to store multiple authenticated sessions or quickly toggle between them, creating significant friction for users who need to move between contexts throughout the day.

Proposed Solution

Support named authentication profiles that persist multiple login sessions simultaneously:

claude profile add work # one-time login with work account
claude profile add personal # one-time login with personal account
claude profile use work # instant switch, no re-auth
claude profile use personal # instant switch, no re-auth
claude profile list # show available profiles and active one

Alternative Solutions

1. Environment variable override — Allow ANTHROPIC_API_KEY or a new CLAUDE_PROFILE env var to override the active OAuth session, enabling switching via shell aliases or direnv.
2. Separate config directories — Support a CLAUDE_CONFIG_HOME env var so users can point to isolated config directories per account, each maintaining its own auth state.
3. Session multiplexing — Allow multiple concurrent authenticated sessions and prompt the user to select which account to use at launch via a flag (e.g., claude --profile work).

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

An engineer has a personal Max plan for side projects and an enterprise Team premium seat provided by their employer. During the workday, they use the enterprise seat for company repos. In the evening, they switch to their personal plan for open source work. Currently, this requires a full logout/login cycle (including browser-based SSO) every time — often multiple times per day. With profiles, they would authenticate once per account and switch instantly.

Additional Context

• Both personal and enterprise plans use OAuth-based subscription login, so there is no env var or API key workaround available today
• This friction may discourage adoption of org-provided seats if users already have a personal subscription
• Similar multi-account switching patterns exist in AWS CLI (named profiles), gcloud (configurations), and kubectl (contexts)
• Privacy/data boundary concern: Users switching between personal and organizational accounts have different privacy expectations for each context. On Team/Enterprise plans, org admins may have visibility into usage and conversations. Clear profile separation would reinforce data boundaries, ensuring personal conversations are never inadvertently routed through an org account (and vice versa). Without profiles, the manual logout/login flow increases the risk of unintentionally using the wrong account.