[FEATURE] Add the ability to manage multiple Claude accounts within the Claude Desktop app with easy switching between profiles.

Found 3 possible duplicate issues:

1. https://github.com/anthropics/claude-code/issues/261
2. https://github.com/anthropics/claude-code/issues/12810
3. https://github.com/anthropics/claude-code/issues/3835

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

This is not a duplicate of the referenced issues. Those issues (#261, #12810, #3835) are specifically about Claude Code (CLI), whereas this feature request is for Claude Desktop (the GUI application).

Key differences:

Different products:

Issues #261 and #12810 address the command-line tool and already have workarounds using CLAUDE_CONFIG_DIR environment variable
Issue #3835 is about switching between payment methods (Max vs API), not different accounts
This issue is specifically for the Claude Desktop GUI app, which is a separate product
Different user experience:

CLI users can use environment variables and shell functions to manage profiles
Desktop app users have no equivalent workaround and must manually sign out/in through the GUI
Different use case:

This request is for graphical multi-account management in the Desktop application, not CLI profile switching
The Claude Desktop app needs its own implementation of account switching that's appropriate for a GUI application (similar to how Slack, Discord, or Chrome handle multiple accounts/profiles in their desktop apps).

Please keep this issue open as it addresses a genuine gap in the Claude Desktop application's functionality.

+1

my main use case is running parallel projects across two different GitHub accounts from the desktop GUI. I've looked through existing issues and tried various workarounds (separate CLAUDE_CONFIG_DIR profiles, GH_TOKEN in cloud environments) but nothing provides a clean solution.

the Connectors feature only supports one GitHub account at a time, which forces constant disconnecting and reconnecting when switching contexts.

Please add this!

+1 — This is a significant adoption blocker.

What I've already solved in the terminal:

I run a multi-workspace Claude Code setup with 5 separate API workspaces (work org + personal + consulting), hierarchical 4-tier configs, and automatic API key selection per directory via apiKeyHelper. Full context isolation, separate cost tracking, bidirectional config sync — it all works beautifully in the terminal.

The terminal proves this workflow is technically feasible and highly productive. But it runs on API billing, which adds up fast.

Where it breaks down:

The Desktop app (with Pro/Team/Max subscriptions) is the cost-effective path — and it's required for Cowork and Desktop-based Code. But it only supports one logged-in account at a time. No browser workaround covers Code or Cowork since they need local file system access through the Desktop app.

My current situation: I have a Team account for work and want a personal Pro account — same machine. Right now, that's impossible without constant logout/login.

The competitive angle:

I'm currently considering consolidating from multiple AI tool subscriptions (ChatGPT for personal, Claude Team for work) into Claude for everything. Multi-account Desktop support would remove the last friction point. I suspect there are many others in the same position — people ready to go all-in on Claude if this basic workflow is supported.

Suggested approach (from terminal experience):

• Profile-based sessions (like Slack workspaces), not just account switching
• Each profile maintains its own conversation history, projects, memory, and MCP configs
• Visual indicator for active profile (color-coded sidebar or avatar)
• Keyboard shortcut for quick switching (Cmd+Shift+] as OP suggested)
• Bonus: directory-aware profile auto-switching (like how apiKeyHelper works in the terminal)

Related issues: #12810 #20549 #261

+1 — this is a daily pain point for me.
I work in IT for an organization and also run my own consulting business on the side. I use Claude heavily for both — enterprise security research, documentation, and project work during the day, then personal projects and business development in the evenings and weekends. All on the same Mac.

Right now I’m doing exactly what the OP describes:
Claude Desktop for one account, browser for the other. It works, but it defeats the purpose of having the desktop app and Cowork/MCP integrations if I can only use them for one identity at a time.

The Slack-style workspace switcher model is the right call. Separate conversation history, separate MCP configs, separate memories — just a quick Cmd+Shift+] to flip between them. The browser profile workaround shouldn’t be the long-term answer when every other productivity tool has solved this already.

This would also be huge for consultants and MSP techs who manage multiple client environments.
The use case goes well beyond just “work and personal.“​​​​​​​​​​​​​​​​

+1 on this feature — enterprise/corporate use case

I'm an IT administrator and network engineer working in a managed enterprise environment. I maintain two Claude accounts: a corporate account provisioned and managed by my organization, and a personal Max plan I pay for out of pocket.
Because these accounts are on different email addresses, there's no way to switch between them without fully signing out and back in. In practice, this means I keep the desktop app logged into one account and a browser window open for the other — a clunky workaround that defeats the purpose of having a native app.

The friction is real and daily. My corporate account is appropriate for work tasks within my organization's acceptable use policies, while my personal Max account is what I reach for outside that scope. Having to juggle two separate surfaces constantly breaks flow.

A profile switcher — even just a simple drop-down from the avatar menu like Slack uses for work spaces — would be a meaningful quality-of-life improvement for anyone operating in environments where work and personal accounts need to stay separated. This is an especially common scenario in enterprise settings where organizational accounts are managed externally and can't simply be merged with a personal subscription.

Add me to the list requesting this. I am a web developer on a Team account for work and want to be able to cleanly switch between work and side gig accounts, including to use Code. Being able to run both at the same time would be great, but I would settle for a clean switch where my Claude Desktop doesn't show the wrong Code sessions. Simply put: Desktop Code view should respect per-account session storage, not a single shared Windows config directory.

adding myself to the request list here too. desktop switching between my work and personal accounts would be incredibly valuable.

I want to pass along to those of you who are looking to do this that if you already run Windows and WSL, a workaround that allows you to run both is to install the Ubuntu version of Claude Desktop and the windows version of Claude Desktop, one for work and one for personal. You have to write a launch script to pick up the correct config on the Ubuntu side, or it will pick up the config from the Windows version, but it works - two fully functional versions of Claude, one computer. They'll even run at the same time if your machine will handle it.

If you need this feature, your upvote is the only thing that matters. Don't just read and leave. React.

Every single thumbs-up on this issue is a signal to the team that this is not a nice-to-have. It is a workflow blocker. A productivity killer. A daily source of frustration for people who are paying customers and loyal advocates of this product. Right now, this issue has a fraction of the votes it deserves given how many people are silently suffering through the same pain.

The problem is universal. If you use Claude for work, you almost certainly maintain more than one account. A personal Max plan and a corporate Team seat. A consulting gig and a side project. Multiple client environments you have to juggle. This is not some niche edge case. This is the default reality for any serious professional user. Look at the comments here. Developers, consultants, enterprise users, IT professionals. We are all hitting the same wall.

The workarounds are embarrassing for a product this good. Think about that for a second. Claude is one of the most capable AI tools on the planet, and to switch between two accounts you have to sign out, sign back in, and lose your entire flow state. Or run a janky setup with Desktop for one account and a browser tab for the other. Or create separate macOS user profiles like it's 2005. Slack, Chrome, Notion, Discord, VS Code, and virtually every modern multi-user application solved this years ago. This is table stakes. We should not still be asking for it.

But here is the hard truth: silent agreement does not ship features.

I know exactly what happens. You found this issue, you read through it, you thought "yes, I need this too," and you kept scrolling. I get it. Someone already said what you were going to say. The issue exists. Surely the team knows. But that is not how prioritization works. Product teams allocate resources based on measurable demand. And the single most important metric on a GitHub issue is the thumbs-up reaction count on the original post. Not a "+1" comment. Not a bookmark. The reaction. It is the difference between "a few people mentioned this" and "our users are overwhelmingly asking for this."

37 upvotes is not enough. Not for a feature this fundamental. Not when thousands of people use Claude Desktop across multiple accounts every single day. That number should be in the few thousands. The only reason it is not is because people assume someone else will do it. That their one vote will not matter. But it does. Every single one adds up. Every single one makes this harder to deprioritize.

What to do right now (it takes 5 seconds):

1. Scroll to the very top of this issue
2. Click the smiley face reaction button on the original post (not this comment)
3. Hit the thumbs-up

That is it. You do not need to write anything. You do not need to subscribe. Just one click.

If switching accounts wastes even five minutes of your day, that is over 20 hours a year of lost productivity you are quietly accepting. Twenty hours of broken focus, interrupted workflows, and unnecessary friction. All because you did not click a button.

Be the vote you wish someone else would cast. Let's get this on the roadmap.

+1

I am also looking to have a personal usage account and then a work account. Needing a virtual machine or even a completely separate local machine for this feature would be exceptionally tedious...

Same here in the need of running multiple accounts in claude code session or desktop app.

This is my only barrier remaining to make a personal subscription of Claude. I’m currently using ChatGPT for my personal use.

Big +1 as well. I'm trying to switch from other providers for my personal LLM use cases to Claude for everything, and I have work accounts already. I need the ability to switch between work and personal contexts and keep a hard wall between them both for billing and privacy/legal reasons. This is pretty important if I ever want to use Claude for my personal use and pay for a subscription in addition to my work usage - which I would love to do!

In particular this matters for both desktop and mobile.

I REALLY want to switch. But I do need to keep my work & personal separate. Please consider adding this ability so that those of us wanting to make the change to Claude can do so. Adding friction means fewer people may capitalise on the current environment!

+1, I was already paying for a personal Claude subscription for personal projects, then work bought a Claude subscription today and I need to run both in Mac Desktop app for Cowork. This definitely makes it harder for people paying for personal subscriptions to get the full benefit and I can see some people discontinuing their personal subscription if they can't switch easily.

The ability to give separate, mutually exclusive folder access permissions to each Claude account is also extremely important to keep sensitive personal data + confidential work data isolated.

Passo da hora, 3 contas e não posso alternar no Claude Desktop.

+1

Please do this!

We should already have this. I have a business account managed by the company and my personal account. I would like to be able to use both without having to log out of my account all the time.

+1 This is very annoying to not be able to switch. There are many use cases to having multiple accounts, and needing to keep data and usage separate.

+1, i need to seperate my business consumption with my personal one and currently it´s blocking me to do this without additional effort

🙏🏻... on iOS too.

+1, I have a personal account and a different one for a business I work for.

I built an open-source CLI that solves this for Claude Code (terminal):

npm install -g @synth1s/cloak

cloak create work        # save current session
cloak create home        # save another
cloak switch work        # instant switch, no logout needed

Each account gets its own isolated directory. Sessions, tokens, MCP servers, and settings are fully preserved across switches. Supports concurrent sessions in different terminals.

Shell integration adds claude -a work as a one-step shortcut.

https://github.com/synth1s/cloak

Note: This works with Claude Code CLI only, not the Desktop app. For Desktop app multi-account support, we still need Anthropic to implement it natively.

I built an open-source CLI that solves this using CLAUDE_CONFIG_DIR: npm install -g @synth1s/cloak cloak create work # save current session cloak create home # save another cloak switch work # instant switch, no logout needed Each account gets its own isolated directory. Sessions, tokens, MCP servers, and settings are fully preserved across switches. Supports concurrent sessions in different terminals. Shell integration adds claude -a work as a one-step shortcut. https://github.com/synth1s/cloak

Ok, nice, but this thread is about the desktop app, not the CLI.

I built an open-source CLI that solves this for Claude Code (terminal): npm install -g @synth1s/cloak cloak create work # save current session cloak create home # save another cloak switch work # instant switch, no logout needed Each account gets its own isolated directory. Sessions, tokens, MCP servers, and settings are fully preserved across switches. Supports concurrent sessions in different terminals. Shell integration adds claude -a work as a one-step shortcut. https://github.com/synth1s/cloak > Note: This works with Claude Code CLI only, not the Desktop app. For Desktop app multi-account support, we still need Anthropic to implement it natively.

This is a well documented and understood workaround for the CLI and has no part in the solution for the client issue this feature request is trying to resolve.

Why we already don't have this feature?
commmmmon this switching is killing me.

Workaround: Profile switching via credential files + directory auto-detection

I needed to switch between a personal (Claude Pro) and a work (Claude Team) account depending on the project I'm working on. Since native multi-account support isn't available yet, I implemented a workaround using credential
file swapping + a shell wrapper that auto-selects the profile based on the current directory.

How it works:

• Credentials are saved per profile under ~/.claude/profiles/<name>/.credentials.json
• claude-switch <profile> copies the right credentials file to ~/.claude/.credentials.json
• A claude() wrapper checks the current directory and auto-activates the correct profile before launching
• A manual override ($env:CLAUDE_MANUAL_PROFILE) prevents the auto-switch from overriding an explicit user selection
• Works on both Git Bash (.bashrc) and PowerShell ($PROFILE)

Core functions (PowerShell version):

function claude-switch {
param([string]$profile)
$creds = "$HOME\.claude\profiles\$profile\.credentials.json"
Copy-Item $creds "$HOME\.claude\.credentials.json" -Force
$env:CLAUDE_MANUAL_PROFILE = $profile
Write-Host "Profile '$profile' activated."
}

function claude {
if (-not $env:CLAUDE_MANUAL_PROFILE) {
# auto-switch based on directory
if ((Get-Location).Path -like "C:\Projects\work*") {
claude-switch work | Out-Null
}
}
& "$env:APPDATA\npm\claude.ps1" @args
}

It works reliably, but it's clearly a hack. Native support with something like claude --profile work or a CLAUDE_PROFILE env var would be a much cleaner solution. +1 on this request.

Similar Feature request on Mobile
https://github.com/anthropics/claude-code/issues/36151

Please add this!! I'm collaborating with more and more teams, and switching is more friction than expected.

+1 please add this

+1 please add this.

Really need this!

pls- super important now that Microsoft 365 connector is only available on Claude Teams/Enterprise! need to be able to get one personal daily digest using context from work and personal, and keeping sensitive data where it belongs!

+1 Add this feature

+1

Seems like they could just use Claude to implement this constantly requested feature in about 37 seconds.

+1 It seems currently there is already support for multiple plans on one account (Personal and Team) but only if they are on the same email. Please add the ability to login to a personal (different email) and team (work email) with the sidebar switcher!

+1

+1 (work + personal accounts different emails)

+1, needed for work and personal use

+1

+1 def need this for work

+1

+1

+1 this should absolutely be a priority.

+1

This would be great - and really prevents potential revenue for pro accounts. Since desktop already allows a "Personal" plan when you have a corporate team plan, maybe by adding the ability to specify an account email for the "Personal" plan, it can separate the necessary memory and connectors.

Please.

+1 on this request. I’d like to extend the scope to also cover a few missing areas:

Claude Code (CLI)
Beyond the Desktop app, the CLI has the same problem. A dedicated /accounts slash command for interactive account switching mid-session would be ideal, along with a --account <name> flag for scripting and automation workflows. The groundwork already exists in ~/.claude/.credentials.json — named profile support could be layered on top without a major architectural change.

Claude.ai — Web & Mobile
The same account switcher concept should extend to the web app and mobile apps (iOS/Android), not just Desktop. Users shouldn’t need to fully sign out on any platform.

Freelancer / contractor use case
Beyond the personal vs. work split, many developers maintain completely separate accounts per client for confidentiality and billing reasons. Quick switching between 3+ accounts would make this workflow viable without juggling multiple browsers, terminals, or devices.

I can understand why there is apprehension on Anthropic's side to add this feature due to the current landscape around unofficial wrappers, third party harnesses, etc. However... the enterprise need for this is strong.

+1 -- specifically need this for Cowork

I have a personal (Pro/Max) and a work (Team) Claude account. I need Cowork on both: personal for my side projects, work for company tasks.

Since Cowork is desktop-only with no web fallback, there is currently no clean way to use both accounts. The only workaround is launching a second instance with --user-data-dir, which works but feels like a hack.

A simple account switcher (like Slack workspaces) would solve this completely.

+1 on this request. I have multiple subscriptions through various client projects. Need an account or profile switcher inside of Claude Desktop to use Cowork with local files and connectors.

+1. preventing me from recommending my workplace acquire an additional account for me - too hard to manage in addition to my personal account

+1

+1 - really want this!!

+1

Worth noting OpenAI and Gemini both have this feature.

+1 - This is a significant friction point between adoption between home and work.

+1 I have workplace-managed claude subscription that I use for work projects and personal subscription that powers my claude-based personal assistant and I'd like to be able to switch between them

+1

+1 — being able to switch between personal and enterprise accounts seamlessly would be fantastic. Signing out and back in every time I move between contexts is real friction.

+1, x20 is not enough for full week of work, I would like to be able to easily switch between multiple subs without losing the history and in progress items just like I can do in CLI

+1

+1

+1

I have a personal and a work claude account, this would be a massive win for my workflows.

I've tried experiments like isolating a 2nd installation of the claude app but that messes with the bundle too much and things break (like the VMs in cowork). I wish some hacks were possible but they're too brittle.

+1

+1

+1

+1

+1

+1

+1

I have a personal Max plan and I have pushed to get a work Max plan for security reasons. Running into issues effectively using them both. This seems like the type of use you would want to encourage!

I have a personal Max and our org has a Team plan. Having to keep one open in the browser and one on the app is just a poor experience. Make it happen! +1

Guys, please stop spamming this thread. If your comment is just another "+1", a thumbs-up reaction on the first message is more than enough. I can relate to your pain, but comments like these don't add any value to the conversation.

Guys, please stop spamming this thread. If your comment is just another "+1", a thumbs-up reaction on the first message is more than enough. I can relate to your pain, but comments like these don't add any value to the conversation.

I rather disagree, this is very annoying to work around and the louder people are about it, the more attention it will get

> Guys, please stop spamming this thread. If your comment is just another "+1", a thumbs-up reaction on the first message is more than enough. I can relate to your pain, but comments like these don't add any value to the conversation. I rather disagree, this is very annoying to work around and the louder people are about it, the more attention it will get

What about those of us that want a real update when/if it ever happens, without getting 87 spam messages every single day?

This would need to be extended to Claude code cli and the mobile apps too.

+1 from another paying-on-both-sides user.
Two paid plans — Team Premium through my employer for daily Claude Code work across multiple repos and customers, personal Max 5x for independent consulting and personal projects. Different emails, deliberately separated for IP and Commercial Terms vs Consumer Terms reasons. Sign-out / sign-in every switch is real friction.
One thing worth adding to the OP’s request: this should cover the VS Code Claude Code extension too, not just Claude Desktop. The extension has the same pain — one logged-in account at a time, each VS Code window inherits the global login. Being able to set the account per-window (or per-workspace via .claude/settings.json) would let a single VS Code instance host work and personal repos cleanly without launching separate browser-based workarounds.
The community has already shipped working approaches via CLAUDE_CONFIG_DIR (see jean-claude, claude-swap) — would be great to have first-party support so it’s not an env-var hack.

+1

+1 but I would that there should be configurable profiles within a single Claude account. They share plan usage and billing but everything else acts as if they were two separate accounts. This would allow a user to have a work profile and personal profile without having to purchase two claude plans.

+1

+1

+1

+1 to this issue as well. I have an Claude Team plan on my work email address; mainly used for work matters, and I also do have Claude Pro plan on my personal account; used for side-projects. Currently for Claude Code CLI I follow this a reply from #261 for my claude accounts and setting aliases to switch between them: https://github.com/anthropics/claude-code/issues/261#issuecomment-2701757283

However, there are some tasks I would use Claude Desktop and it doesn't natively support the switching of accounts. I have to log out and log in to another account just to research on something or ask an enquiry.

+1

It causes major friction to have to log in and log out of work and personal accounts when I need desktop access for both. Please add this feature Anthropic!

+1

+1

+1

+1

+1
Really needed, I have a personal Max account and an Enterprise account at work and it's really frustrating to log in and out several times a day

+1
Competitors like ChatGPT already have this basic feature.
The obvious use-case is work/personal account switch

Partial workaround for a subset of users — useful if your two accounts can live in different interfaces rather than two profiles inside Desktop itself.

If you have Claude Desktop (Team) + Claude Code CLI (Max) and want them on the same Windows machine running in parallel, you can use NTFS junctions + CLAUDE_CONFIG_DIR to give each its own config dir, MCP roster, memory graph, and session history. The two run simultaneously, no sign-out/sign-in churn.

Doesn't address the in-Desktop profile switcher this issue is asking for — that still needs Anthropic to ship it. But unblocks the Team-at-work + Max-for-personal scenario today.

Full writeup with reproducible scripts: https://github.com/MankhongGarden/claude-code-multi-context-windows

+1

For anyone who needs Claude CLI multi-account on Windows in the meantime (this issue asks for Desktop, but CLI is where most of the heavy quota gets burned anyway), the workaround that holds up well:

1. Per-account config directory — set CLAUDE_CONFIG_DIR to a different folder for each account, e.g. D:\ClaudeData\.claude-work and D:\ClaudeData\.claude-personal.
2. Each folder gets its own .credentials.json, settings.json, MCP config, skills set, memory directory.
3. Wrapper scripts (one .cmd per account) that set CLAUDE_CONFIG_DIR then invoke claude. Put both on PATH so you launch with claude-work vs claude-personal.

This doesn't address the Desktop ask in the OP (UI account switcher, separate conversation history within a single Desktop instance), but it solves the CLI side completely — two independent Claude sessions with no auth cross-talk, no /logout/login required, each context with isolated MCP / skills / memory.

The mobile (#36151) and VSCode (#55621) sister issues look like they need the same primitive (per-account config dir) plumbed through their host apps.

+1 on this, personal and work account switching would be a boost. I use them for different tasks, don't want to conflate the two nor create any conflict of interest in the content or actions

+1
Use-case: Enterprise/Personal account switch

Also, switching between accounts (logout/login) makes the grouping of conversations get lost — the sessions themselves are still on disk, but the custom groups in the sidebar are reset.

Adding my support for this.

The sign-out and sign-in cycle is genuinely disruptive. Every switch means losing conversation context and going through re-authentication, which adds up fast when bouncing between personal and work throughout the day.

The bigger pain for me has been accidentally using my personal account for work tasks, and the other way around, because I forgot which account was signed in. By the time I notice, the usage is already counted against the wrong account. A built-in profile switcher would prevent these mix-ups entirely.

Would love to see this land.

+1

On the same page here with everyone

+1
Use-case: Enterprise/Personal account switch

In the end the only viable solution that I have found was switching to codex for personal projects 🤣

I guess I'm not the only one who came to the same conclusion. Anthropic really shoots itself in the leg by ignoring this issue. People using multiple accounts for economy are doing it anyway using routers. Mostly legitimate users suffer.

Operator-side workaround for those who can't wait on the desktop fix: the same multi-account pain shows up identically in the Claude Code CLI, and the cluster of three related filings (this one, #27302, #36151) now has ~1,178 cumulative reactions across the three platforms.
For the CLI specifically, two new hooks shipped this week in cc-safe-setup (MIT, no telemetry) that address the audit and refusal sides of multi-account CLI workflows:

• account-routing-preflight.sh — SessionStart hook that refuses the session with exit 2 when ANTHROPIC_ACCOUNT_LABEL doesn't match the per-project declaration in .claude/expected-account. Catches the "I forgot to switch accounts before launching" failure mode at session start rather than at the billing dashboard at month-end.
• account-billing-log.sh — Stop hook that appends one pipe-separated line per session to ~/billing-logs/sessions.log capturing timestamp, account label, cwd, session ID, and turn count. For consultants invoicing clients off the same machine.

Important constraint documented in both hooks: a SessionStart hook cannot set the parent claude process's env vars (hooks run as subprocesses). Account switching itself still happens via shell alias or direnv before launch. The hooks are the safety net.
Companion long-form for the five-pattern field guide (shell alias / direnv / ~/.claude symlink / SessionStart preflight / billing log): https://gist.github.com/yurukusa/d880ecc984af5d664f003daf85f956e3 — covers the three personas (work+personal / consultant / enterprise multi-org).
None of this replaces the desktop UX fix this issue is asking for. The hooks are CLI-only and only help the cohort that's already in the terminal. For the desktop, web, and mobile surfaces, the cluster's combined 1,178-reaction signal seems like the relevant case for prioritization.
— independent operator; not affiliated with Anthropic

Until/unless this lands, here are five operator-side paths I documented after running into the same pain across personal + consulting contexts. The right one depends on how you switch (and how often).
1. shell alias / wrapper — alias claude-work='ANTHROPIC_API_KEY=$WORK_KEY claude'. Fastest setup. Right for daily switchers who already have terminal muscle memory.
2. direnv — .envrc per project sets the credential. Switching is automatic by cd. Right for users with one folder per account context (e.g. work-projects/ vs personal-projects/).
3. .claude/ symlink — ~/.claude is a symlink to either ~/.claude.work or ~/.claude.personal. Switching script swaps the link. Right for users where the session state (not just the API key) needs to switch — separate caches, separate logs, separate hooks.
4. SessionStart hook — At session boot, read a marker file (e.g. .cc-account in the project root) and reject the session if the wrong credential is loaded. Right for production-ish setups where the wrong-account risk is a financial / data-leak concern, not a convenience concern.
5. Per-shell PROMPT marker — Display the active account in the prompt so you always know which one is loaded. Combines well with any of the above; reduces "I thought I was on personal" mistakes.
A free 7-question interactive self-audit classifies your persona (work+personal / consultant / enterprise multi-org) and recommends a pattern combination in five minutes. No signup.
The five patterns with worked examples + cross-cluster references (this issue connects to ~1,178 cumulative reactions across #18435 here + #27302 connectors + #36151 mobile) are in the multi-account operator field guide (日本語版).
Two cc-safe-setup hooks shipped specifically for the wrong-account risk:

• account-routing-preflight.sh — SessionStart preflight refusal on mismatch
• account-billing-log.sh — Stop hook per-session billing log for consultants invoicing clients

These are advisory-level operator-side defenses; they don't replace the native multi-account feature this issue is asking for, but they keep the wrong-account category from becoming an incident while we wait.

+1
This is a very basic feature that most compatible tools already provide. It’s a mess that I manage daily, and it wastes a lot of time.

+1
I would also like this feature, but here is a working around that i'm using at the moment with Google Chrome feature of creating web apps:

1. Create a google chrome profile for your personal use
2. Access claude.ai and login with your personal account
3. In Google Chrome settings, you can create a web app for the current page (in this case, claude.ai): settings > Cast, save and share > Install Claude...
4. Optionally you can go to the folder where these chrome apps are installed and edit the file to change its name (this will change how the app name is displayed in your application launcher). For instance, in Linux chrome apps are stored in ~/.local/share/applications. In macOS i believe they're located in ~/Applications/Chrome Apps. In windows i believe it is in %appdata%\Microsoft\Windows\Start Menu\Programs\Chrome Apps (but i didn't check since there is quite some time i dont use windows)
5. Repeat for other profiles (e.g: your work profile)

In the end of the road its just a web page being rendered as it was a standalone app; but tbh it is already good enough for me (i do the same thing for notion in linux since they do not offer a desktop app for the OS, and it was never a problem for me).

Here is an example on how i can launch it in my OS:

<img width="582" height="331" alt="Image" src="https://github.com/user-attachments/assets/46ff07bd-dcee-406f-98d6-7921ee406d07" />

<img width="405" height="241" alt="Image" src="https://github.com/user-attachments/assets/45f306fa-5d86-4759-9443-122ce2ea6a98" />

And here is how they'll look like after this process

<img width="1435" height="828" alt="Image" src="https://github.com/user-attachments/assets/e4198f9e-5f2b-4512-ad76-f625b85dafd2" />

Adding another +1, with one important workflow requirement: switching accounts must not kill or suspend work running under the other account.

My concrete use case is having both a corporate Anthropic account and a personal Anthropic account. I may want to start Claude Code work under the corporate account, quickly switch Claude Desktop to my personal account, start or monitor personal work there, and then switch back to the corporate account to check progress.

Expected behavior:

• Claude Desktop can keep multiple Anthropic accounts signed in at the same time.
• Each account keeps its own Claude Code sessions, auth state, settings, and history.
• Switching the visible account is fast and does not terminate active work from the previous account.
• There is a clear account/profile indicator so I know whether I am operating in personal or corporate context.

This is especially important as Claude Desktop becomes a control plane for Claude Code/Remote Control/Cowork-style workflows. A single-account Desktop app is too limiting for people who split work and personal usage or operate across multiple orgs.

This is a must add with running a business and working for an agency and having a personal account - I need a way to switch between them or have a few instances of the app running alongside each other. Please add this feature I know others having similar issues.

I made a free VS Code extension to switch between multiple Claude Code accounts without logging out

If you use Claude Code with separate work and personal accounts, you know the pain: logging out, logging back in, losing your place every time you switch.

So I built Account Switcher for Claude Code (unofficial, open source). It snapshots each account's local state into named profiles and swaps them with one click from the status bar:

🔄 Switch accounts in seconds — both stay logged in
🔒 Sessions and chats stay fully isolated per account
💾 Automatic timestamped backup before every switch
↩️ Failed switch? It rolls back automatically — plus a "Restore Last Backup" command
🧪 Open source with a full test suite, so you can verify it never touches or logs your tokens
Works in VS Code, code-server, and VSCodium.

VS Code Marketplace: https://marketplace.visualstudio.com/items?itemName=faisalsannan.account-switcher-for-claude-code
Open VSX (code-server/VSCodium): https://open-vsx.org/extension/faisalsannan/account-switcher-for-claude-code
Source + docs: https://github.com/FaisalSannan/account-switcher-for-claude-code

It's completely free — if it saves you time, a ⭐ on GitHub helps others find it. Feedback and issues welcome!
And if it really saves your day, you can buy me a coffee ☕

Hi guys, I had the same issue I decided to create this cli tool https://github.com/yarikleto/claude-profile

It can help you too

For anyone on Windows who needs this today, there’s an open-source workaround worth trying: ai-multi-instance 🛠️

It allows you to launch multiple Claude Desktop instances with a separate --user-data-dir per profile, so you can run multiple accounts side by side with isolated auth, history, and settings. It also solves the OAuth callback problem: normally the claude:// redirect after sign-in lands in whichever install owns the protocol, not the profile you’re trying to log into. The tool optionally registers itself as the claude:// handler (an HKCU registry entry with a valid UserChoice hash, reversible from the menu) and routes the callback to the last profile you launched. MIT licensed, Python standard library only.

This is a real pain point for anyone that uses Claude at work and on their own time. Employers regularly expected employees to use their personal phones for work, which means if you want to remote control your professional work and your personal work, you can't do it.
This doesn't seem like a particularly complicated ability to provide

+1 to this. Native profile switching would still be the best solution, especially for work/personal or client-separated setups.

For anyone on macOS who needs something today, the lightweight workaround is to create a second Claude Desktop app and run it with its own data directory.

Simple version:

cp -R "/Applications/Claude.app" "/Applications/Claude Work.app"
open -n "/Applications/Claude Work.app" --args --user-data-dir="$HOME/Library/Application Support/Claude-Work"

That gives the second app its own local profile data instead of sharing the default Claude Desktop state.

For daily use, there is also a small helper script and Mac-specific write-up that makes the copied app open normally from Finder, Dock, or Spotlight with the separate data dir already wired in.

Still agree this should be native. A built-in profile switcher would be much cleaner than asking users to manage separate app copies.

+1 looking forward

For GUI version I use Claude Desktop Manager (claudeprofiles.com). Does the job for me. Same approach as ai-multi-instance I guess but as a native Windows desktop app instead of a CLI menu.
+1 for the native feature anyway

+1 please do this!!

+1 please do this!!!

I built a free app that does exactly this — Multi Instance for Claude Desktop.

It lets you run multiple isolated Claude Desktop instances side by side. Each instance gets its own profile, session, account, and color. One click to create, one click to launch. No command line, no --user-data-dir flags, no manual setup.

Available now, free, on the Microsoft Store:
👉 https://apps.microsoft.com/store/detail/9NG247TJ47P0

How it works: the app copies the Claude Desktop portable binary and launches each instance with its own --user-data-dir, so profiles are fully isolated (MCP servers, config, auth tokens — all separate). You get a dashboard to create, launch, and delete instances.

Known limitation (same as all workarounds): each instance needs a one-time manual sign-in because Claude's claude:// deep link is global. You sign in once per instance and it persists.

Built by Carlos De La Torre — feedback welcome.
LinkedIn: https://www.linkedin.com/in/carlosdelatorre-ai/

I built a free app that does exactly this — Multi Instance for Claude Desktop. It lets you run multiple isolated Claude Desktop instances side by side. Each instance gets its own profile, session, account, and color. One click to create, one click to launch. No command line, no --user-data-dir flags, no manual setup. Available now, free, on the Microsoft Store: 👉 https://apps.microsoft.com/store/detail/9NG247TJ47P0

My work account for Claude only supports SSO sign-in. I tried your desktop app, but it seemed like it wouldn't open a separate instance when signing in with SSO? Correct me if I'm wrong.

It might be possible that they don't want to implement this lest users abuse this feature by using multiple subscriptions plans.

https://apps.microsoft.com/store/detail/9NG247TJ47P0

@radelqui is it possible to have this on mac as well?

I just created a launcher app that lets you run multiple instances simultaneously with different accounts. You can use it until Anthropics releases an official update.
Claude Desktop Profiles

+1 — strong enterprise need on Windows. Related to the now-closed #36821, which captured the same desktop multi-account pain.

I run a work and a personal Claude account and need both with full Desktop features (Cowork, local MCP, local-folder access). Every current workaround falls short:

• The web app has no local-filesystem access.
• The CLI works (via CLAUDE_CONFIG_DIR) but isn't the Desktop GUI.
• --user-data-dir is silently ignored by the MSIX build, so the second-instance trick no longer works.
• On a managed device (Entra/Intune, ISO 27001), the second-Windows-user / Fast-User-Switching workaround is a compliance problem, not a real solution.

This is partly a regression: the earlier standalone (non-MSIX) Electron/Squirrel Windows build honored --user-data-dir, which allowed running fully isolated instances/profiles side by side. Moving the Windows app to MSIX packaging (single-instance lock + per-user provisioning + sandbox) removed that capability — so behavior that previously enabled multi-profile use is now blocked.

Ask: native in-app ability to run two profiles concurrently in one Windows session. I understand MSIX makes true concurrency non-trivial — but even restoring isolated-instance support (or non-concurrent native account switching without a full sign-out/in) would be a major improvement.

Context: Windows 11, enterprise-managed (Entra/Intune) device.

Personally I think there should be 2 separate apps too. i would like both running so scheduled tasks can always run for each instance. Switching profiles stops anything from continuing on the previous profile. There must be something in works for this, so many people use 1 machine for work and personal.

+1 on this. I regularly switch between a personal Claude account and a client organization's account, and having to sign out/back in each time is a real friction point. A first-class profile switcher (like Chrome or Slack) that keeps both sessions live would be a _massive_ improvement, especially for anyone doing consulting/contractor work across multiple orgs.

Would be just great if switching accounts didn't b0rk / interrupt running sessions in the account being switched away from.

For anyone on Windows landing here while this stays open. A workaround that's held up well for me:

You can launch a second isolated instance with Electron's --user-data-dir flag (separate login, history, MCP config). The one thing that flag doesn't fix on Windows is the taskbar. Both instances share the same icon and Alt-Tab entry, so you can't tell work from personal at a glance.

I put together a small free/open-source launcher that does the --user-data-dir isolation and stamps each instance with its own Windows taskbar identity (separate icon, separate Alt-Tab entry, independently pinnable) via per-window AppUserModelID. MIT licensed: https://github.com/GiovanniTrevisan/claude-multi-account

Not a replacement for native account switching (still hoping for that!), but it makes running two accounts side by side genuinely usable day to day.

I hit this daily, so I built a workaround and open-sourced it: [Lanes](https://lanes.synthetixis.com), a macOS menu-bar launcher that opens Claude Desktop with a separate profile per account. Work and personal run side by side, no signing out.

This removes the compromise you described. Both accounts are the real desktop app now, not one in a browser.

What it isn't: the in-app switcher this issue asks for. No Cmd+Shift+], no single window with a dropdown, it launches separate instances. Parallel windows work better for me, but this doesn't replace the feature request.

How it works: each profile gets its own --user-data-dir. Electron's single-instance lock lives inside that directory, so separate dirs give you genuinely independent parallel sessions — separate login, history, and settings each.

It never touches your auth tokens. No credential copying, no session-file swapping. It only decides which directory each instance writes to. No network calls, no telemetry, no auto-updater.

• https://lanes.synthetixis.com
• https://github.com/synthetixis/lanes (MIT)
• macOS 13+, Apple silicon. Not notarized, so first launch needs "Open Anyway", documented on the page.

Unofficial, not affiliated with Anthropic. Happy to answer questions on the approach. Still want to see this land natively.

Waiting for it since last year 😢

I've tried a couple of the workarounds on this thread, but I need something that supports SSO for my work account for Claude. Has anyone found a multi-instance workaround that supports SSO login for one of the instances?

It this request already on the roadmap? Antropics? Any estimated release date?