[FEATURE] multi-account concurrent sessions in Claude Code

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

I work across multiple Claude accounts at the same time: my own personal account for my own projects, plus separate work accounts for 2-3 different employers/clients. Each employer requires that I use their Claude account for their work, not my personal one — so I can't just consolidate everything under one login. Today, Claude Code only supports one active account per session/login at a time, so switching between my personal work and a given employer's work means logging out and back in every time I context-switch. When I'm juggling 2-3 employers plus my own projects in the same day, this turns into constant re-authentication just to move between sessions, and I can't have sessions from different accounts open and active side by side.

This affects every surface I use Claude Code from, not just one: the VS Code extension, the Desktop app, and the web app (claude.ai/code). Right now each of these is also single-account per instance, so the same multi-employer friction shows up whichever surface I'm working in — I need this to work consistently across all three, not just on the CLI.

Proposed Solution

Add support for multiple concurrently-authenticated accounts in Claude Code, consistently across the CLI, the VS Code extension, the Desktop app, and the web app, with the ability to:

• Log in to several accounts at once (personal + N work accounts) without one login invalidating another — on any of the four surfaces.
• Switch the active account for a given terminal/IDE session/window/browser tab with a quick command or UI control (e.g. claude account switch <name> on the CLI; an account picker in the VS Code extension's and Desktop app's title bar/sidebar; an account switcher in the web app, similar to how Google/Slack let you run multiple logged-in accounts side by side).
• Keep separate sessions running per account in parallel — e.g. a VS Code window open against Employer A's account, a Desktop app window open against Employer B's account, and a web app tab open against my personal account, all authenticated and active at the same time.
• See, at a glance, which account a given project/session/window/tab is currently authenticated as, to avoid accidentally doing employer work under the wrong account (or vice versa) — on whichever surface I'm using.

Alternative Solutions

Currently I work around this by fully logging out and logging back in every time I need to switch accounts, which breaks flow and is disruptive when I'm moving between employers multiple times a day. I've also considered running separate machines/VMs per employer purely to keep accounts isolated, but that's a heavy workaround just to get account isolation that the tool itself could provide directly.

Priority

High - Significant impact on productivity

Feature Category

Other

Use Case Example

Example scenario:

1. I start my day working on my own personal project under my personal Claude account, in VS Code.
2. Employer A pings me with an urgent request — I open a Desktop app window authenticated as Employer A's account, working in Employer A's project, without logging my personal VS Code session out.
3. While that's running, Employer B also has an open task — I open a web app tab (claude.ai/code) authenticated as Employer B's account, working in Employer B's project, at the same time as the other two.
4. With this feature, I could keep all three accounts (personal, Employer A, Employer B) logged in simultaneously across VS Code, Desktop, and web, each tied to its own project/session, and switch or work across them without re-authenticating every time — satisfying each employer's requirement that their account be used for their work, without losing my own concurrent work or being tied to a single surface.

Additional Context

• This is about concurrent, isolated authentication — not just "remembering multiple saved logins," but actually being able to have active sessions under different accounts running at the same time (e.g. one background task per employer account, running in parallel), on whichever surface (CLI, VS Code, Desktop, web) I happen to be using at that moment.
• Should work the same way across all four surfaces so switching surfaces doesn't also force a re-login or an account mismatch.
• Related to the previously-drafted "Background Tasks window" request — a multi-account-aware version of that panel would ideally also show which account each visible session/task belongs to.