Feature Request: Support multiple account login and switching (like `gh auth switch`)

[aice-kazuki-okura]

Feature Request: Multiple Account Support / Account Switching

Problem

Users who work across multiple contexts (e.g., personal, Company A, Company B)
with separate Claude.ai accounts cannot quickly switch between them. There is
no way to see which account is currently active at a glance, and no fast
switching mechanism exists.

This creates real risks:

• Accidentally using a personal account for confidential company work
• Using a company account for personal projects (policy violation)
• No visual indicator of the currently active account in the workflow

Currently, switching requires a full logout → login cycle with browser
authentication every time, making it impractical to switch frequently.

Expected Behavior

Similar to gh auth switch in GitHub CLI:

• Store credentials for multiple accounts locally
• Switch accounts with a single command: claude auth switch
• Show the currently active account clearly (e.g., claude auth status)

Example Workflow

$ claude auth switch
? Select account:
  > personal@gmail.com (Personal - Pro)
    alice@company-a.com (Company A - Teams)
    alice@company-b.com (Company B - Teams)

Current Workaround

claude auth logout && claude auth login --email other@example.com

This triggers a full browser authentication flow every time.

Use Case

Freelancers, contractors, and consultants working across multiple
organizations need reliable, frictionless account switching to avoid
accidental cross-account usage.

[felipearomani]

Feature proposal: /account command for multi-account management

Building on the idea of named profiles, I'd like to propose a /account command (or claude account) that makes multi-account management a first-class experience:

$ claude account

Logged-in accounts:
  * work     →  john@company.com    [default for new instances]
    personal →  john@gmail.com

Switch account for this session:
  > work (current)
    personal
    + Add another account

What this would support:

• List all logged-in accounts — see every authenticated profile at a glance
• Default account — configure which account new Claude Code instances start with
• Per-instance switching — switch the active account for the current terminal session without affecting other running instances

This is especially useful for people who have a company account (restricted to work projects) and a personal account, and need to run both without logging in and out constantly or managing raw CLAUDE_CONFIG_DIR env vars manually.

Multiple terminal instances could each run under a different account simultaneously — great for keeping work and personal projects truly separate.

[diranged]

In the meantime while this isn't built in, CLAUDE_CONFIG_DIR gets you most of the way there. Each config directory gets its own Keychain entry so auth is fully isolated — you can have work and personal running side by side in different terminals without them touching each other.

I got tired of managing the env vars manually so I wrapped it in a small CLI called claude-profile. You create named profiles and launch with the one you want.. each gets its own auth, MCP servers, settings. Not as clean as a native claude auth switch would be, but it works today.

Wrote up the details here: https://blog.wiredgeek.net/tools/claude-code/2026/04/06/managing-multiple-claude-code-profiles.html