[FEATURE] Support for multiple accounts / profiles

[AlbertoGarau]

Preflight Checklist

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

Problem Statement

I have a work account (managed by my company) and a personal account. Currently I need to run claude logout / claude login every time. I want to switch between them, which is tedious and time-consuming.

Proposed Solution

A flag like --profile or --user to switch between accounts:

claude --profile=work
claude --profile=personal

Each profile would store its own credentials separately, so login is only needed once per profile.

Alternative Solutions

Alternatively, supporting a CLAUDE_CONFIG_DIR environment variable to point to separate credential directories would also work.

Priority

Low - Nice to have

Feature Category

CLI commands and flags

Use Case Example

As a developer, I use Claude Code at work on company projects with a company-managed account, and at home for personal side projects with my own personal account — both on the same machine.
Currently my workflow is:

1. claude logout
2. claude login (with the other account)
3. Work
4. claude logout
5. claude login (back to the first account)

Desired workflow:

1. claude --profile=work (for work projects)
2. claude --profile=personal (for personal projects)

No logout/login needed after initial setup.

Additional Context

No response

[maxklimen]

Running two separate paid subscriptions just because there's no profile support. Web switching is manual, mobile has no workaround at all. This is pushing me toward other tools for separate use. Named profiles with per-profile connector configs would fix this.

[Seungwoo321]

+1 for this feature!

I'm paying $330/month for two Max Plan subscriptions (personal + work accounts).

The current experience is very frustrating:

1. No per-session account binding - Cannot assign different accounts to different terminal sessions
2. Global credential sync - Changing account in one session affects ALL other sessions
3. Mass re-login required - When one session hits its limit, ALL sessions require re-authentication

I investigated implementing a workaround using CLAUDE_CONFIG_DIR, but since credentials are stored in macOS Keychain globally (not per config directory), true multi-account support requires official implementation.

This is critical for developers who have both personal and work subscriptions on the same machine.

[prodan-s]

Concrete use case: I'm on a Team plan through my org (which has Remote Control disabled), and I have a personal Max subscription for Remote Control. On macOS, there's no way to run both simultaneously:

• CLAUDE_CODE_OAUTH_TOKEN env var is silently ignored on macOS — CC always reads from Keychain
• CLAUDE_CONFIG_DIR redirects ~/.claude/ but doesn't isolate the Keychain entry (Claude Code-credentials)
• The Keychain entry is a global singleton — switching accounts affects all terminals

Current workaround: A Keychain swapper script (security delete-generic-password + security add-generic-password) that saves/restores tokens per profile. Running sessions survive the swap (CC loads auth into memory at startup), so you can have one terminal on Team and launch a second on Personal — but you can't start new sessions while the swap is active.

What would fix this: Either (a) --profile <name> flag that reads from a named Keychain entry, or (b) make CLAUDE_CODE_OAUTH_TOKEN actually work on macOS (it currently doesn't override Keychain auth). Option (b) would also unblock CI/CD and automation use cases.