How to Run Two Claude Accounts on Mac

Q: Is CLAUDE_CONFIG_DIR the same as Power Claude account groups?

No. Config dirs separate logins. Groups separate persona membership + optional local projects/memory isolation and an explicit active selection. Use both for a clean Mac setup.

Q: Do I need a second Desktop app if I only use VS Code and Claude Code?

Usually no. Dual CLAUDE_CONFIG_DIR profiles plus Power Claude groups cover most engineering workflows without maintaining a second signed Desktop bundle.

Q: Where is group state stored on Mac?

Group definitions live under ~/.power-claude/state/account-scopes.json (restricted permissions). Isolated trees live under ~/.power-claude/claude-shared/scopes//.

Q: How do I clear the active group?

Dashboard Clear active group or pc scope use none.

Guides

Neural-LLM Admin 16 July 2026 9 min read

Yes — you can run two Claude accounts on a Mac at the same time without logging out every time. Use separate CLI config dirs (and optional dual Desktop), then Power Claude account groups to pool seats for Work, Job A, or Client B and isolate memory per engagement.

TL;DR

Goal	What to do
Two logins that stay signed in	Separate Claude Code profiles (`CLAUDE_CONFIG_DIR`) per account; login once each
Two Desktop apps side by side	Optional: second `.app` + own data dir (Electron `--user-data-dir`) — fragile on updates
Work ≠ personal memory / projects	Power Claude account groups (Work / Personal), isolation on, Use this group when you switch roles
VS Code / Claude Code daily driver	Link both profiles in Power Claude → drag into groups → activate before work

Why people search “two Claude accounts Mac”

Claude Code stores auth, session history, memory, and project settings under a config directory (default ~/.claude). Claude Desktop uses Application Support. One shared tree means switching accounts often means /login and a context mess: work design notes show up in a personal side project, or a personal experiment inherits company conventions.

People search for “two Claude accounts Mac” because they want simultaneous personal + work use — not a ritual of logging out.

What “two accounts” actually means

There are three different problems. Solving the wrong one still hurts.

Layer	Question	Typical tool
Login / billing seat	Which Anthropic account is authenticated?	Separate config dirs / profiles
Desktop UI process	Can two Desktop windows stay logged into different seats?	Second app bundle + data dir
Local memory & persona	Which projects tree and group of seats am I “being” right now?	Power Claude account groups

Mac dual-install guides solve layers 1–2 well for Desktop. They do not automatically give you a named Work vs Personal boundary inside VS Code with isolated Claude Code project memory. That is what groups are for.

Power Claude is independent third-party software — not approved, endorsed, or authorized by Anthropic. Prefer the official Claude Code client path (Architecture B / official profiles), not a subscription OAuth relay.

Option A — Claude Code CLI: two config directories (recommended baseline)

This is the durable Mac baseline for terminal + anything that respects CLAUDE_CONFIG_DIR.

1. Create two homes

mkdir -p ~/.claude-personal ~/.claude-work

2. Shell aliases (zsh)

Add to ~/.zshrc:

alias claude-personal='CLAUDE_CONFIG_DIR=$HOME/.claude-personal claude'
alias claude-work='CLAUDE_CONFIG_DIR=$HOME/.claude-work claude'

source ~/.zshrc

3. Login once per profile

claude-personal   # then /login with personal seat
claude-work       # then /login with work seat

Each directory keeps its own tokens, history, and project notes. Both can stay logged in. Use /status inside the CLI to confirm which plan/email is active.

4. Watch for API keys that bypass the subscription

If ANTHROPIC_API_KEY (or similar) is set in the shell, the CLI may bill that key instead of the subscription you just logged into:

echo "API key set? ${ANTHROPIC_API_KEY:+YES}"
# [ai] If YES and you want subscription billing:
unset ANTHROPIC_API_KEY

5. Optional: direnv per repo

In a work checkout .envrc:

export CLAUDE_CONFIG_DIR=$HOME/.claude-work

In a personal project:

export CLAUDE_CONFIG_DIR=$HOME/.claude-personal

That reduces “wrong account on this repo” mistakes. It still does not name a group of seats or isolate a Power Claude dashboard persona — next section.

Option B — Claude Desktop: second app (optional, higher maintenance)

If you also use the Claude Desktop Mac app and need two windows with two logins, the usual pattern is:

Duplicate Claude.app (e.g. Claude Work.app).
Give the copy its own identity (CFBundleIdentifier, name, optional icon).
Launch with Electron --user-data-dir pointed at e.g. ~/Library/Application Support/Claude-Work.
Wrap the executable so Dock/Finder launches pass that flag.
Re-sign the modified bundle (nested helpers; avoid sloppy --deep-only re-signs).
Re-clone after Desktop auto-updates (the copy goes stale).

That path works for many people and is well documented in the Mac dual-install community. It is also brittle: signatures, updates, deep links during /login, and icon caches. Treat it as Desktop isolation, not as your whole multi-account engineering system.

If you only need dual Claude Code in terminal/VS Code, Option A + Power Claude is usually enough without maintaining a second signed Desktop bundle.

Option C — Power Claude on Mac: manage both logins and isolate with groups

Once both seats exist as Claude Code profiles on the Mac, Power Claude is the layer that:

Surfaces every linked login under Your Profiles
Lets you name groups (Work, Personal, Client-Acme, …)
Lets you drag any accounts into those groups
Optionally hard-isolates Claude projects/memory per group
Makes “who I am right now” explicit via Use this group / pc scope use

Credentials stay private per account. Groups do not become an OAuth vault or a multi-tenant relay. Isolation re-points local project/memory layout; it does not delete history or copy secrets.

Step 1 — Install and link accounts

Install Power Claude from the VS Code Marketplace (publisher neural-llm) or download.
Ensure Claude Code works for each profile (claude-personal / claude-work as above).
In Power Claude → Your Profiles, add/link both accounts (each points at its own Claude Code profile / config dir as you already set up).

Step 2 — Create Work and Personal groups

Dashboard:

Your Profiles → Account groups → + New group → Work (isolation on by default).
+ New group → Personal.

CLI:

pc scope create Work
pc scope create Personal
pc scope list

Names are free-form. Agencies often use Client-North; freelancers use Day-job / Side-projects.

Step 3 — Put each login in the right group

Dashboard: drag account chips from Ungrouped onto Work or Personal.

CLI:

pc scope add <work-scope-id> you+work@company.com
pc scope add <personal-scope-id> you@personal.com

Rule of thumb: one account → one group when you care about isolation. Use tags if you only need labels without dual isolation.

Step 4 — Activate the persona before you work

Moment	Action
Starting the workday	Use this group on Work / `pc scope use <work-id>`
Side project at night	Use Personal
Client monorepo day	Use that client group first
Done	Clear active group / `pc scope use none`

Activating applies the group’s projects layout when isolation is on. OAuth tokens are not shared across groups.

Step 5 — Verify separation on the Mac

pc scope list
ls ~/.power-claude/claude-shared/scopes/

Practical check:

Use Work → leave a distinctive note or memory in a short work session.
Use Personal → open Claude Code on a personal repo.
Confirm you are not continuing the Work memory tree.

Layout apply fails closed rather than clobbering a non-empty tree. Details: docs — account groups.

How the options fit together

Mac dual login (CLAUDE_CONFIG_DIR / optional Desktop copy)
        │
        ▼
  Two authenticated seats on disk
        │
        ▼
Power Claude: link profiles → Account groups (Work / Personal / …)
        │
        ▼
  Active group + isolated projects/memory when isolation is ON

Approach alone	Good for	Weak for
`CLAUDE_CONFIG_DIR` only	Terminal dual login	Named persona, dashboard, isolated memory sets of seats
Second Desktop app only	Two Desktop UIs	VS Code workflow, group isolation, update pain
Power Claude groups only (one shared config)	Persona isolation if multiple logins already linked	Creating the second login if you never set a second config dir
A + C (recommended for engineers)	Dual login and Work/Personal boundaries in daily coding	People who only use Desktop chat with no Claude Code

Daily Mac habit that keeps separation real

Morning → pc scope use Work (or dashboard Use).
Work repos only while Work is active.
Evening learning / side projects → Use Personal.
Optional: direnv sets CLAUDE_CONFIG_DIR and you run pc scope use for the matching group.
Optional Auto-Rotation Engine is a separate opt-in product choice (limits continuity). Groups organize seats and memory; they do not “bypass” Anthropic limits. See product rotation policy docs if you enable automation.

What stays separate vs shared

Data	Separate with dual config dirs?	Separate with Power Claude isolated groups?
OAuth / login tokens	Yes (per config dir)	Yes (per account; groups never copy secrets)
CLI session history	Yes (per config dir)	Group isolation re-homes projects/memory trees for members
MCP / hooks in that config	Yes	Per profile + group layout rules
Claude Code binary	Shared	Shared
Power Claude dashboard “active group”	N/A	Yes — explicit selection

Common Mac gotchas

Wrong account in this terminal: run /status or check which CLAUDE_CONFIG_DIR the shell exported.
API key steals billing: unset ANTHROPIC_API_KEY when you intend subscription billing.
Desktop deep link login hits the wrong window: quit the other Desktop instance while signing into a fresh profile.
Second Desktop app broke after update: re-duplicate/re-wrap; auto-update only refreshes the original bundle.
Groups created but memory still mixed: isolation must be isolated (not global), and you must Use this group after membership changes.
Only one login linked in Power Claude: dual config dirs do not auto-import; link both profiles under Your Profiles first.

Frequently asked questions

Can you run two Claude accounts at the same time on a Mac?

Yes. Give each account its own Claude Code config directory (CLAUDE_CONFIG_DIR), login once per directory, and keep both signed in. Optionally run a second Claude Desktop app with its own data directory. For coding in VS Code, link both in Power Claude and use account groups for Work vs Personal isolation.

How do I switch without logging out every time?

You do not switch one shared profile. You run each account from its own config dir (aliases or direnv) and, in Power Claude, Use the group that matches the role you are in.

Is CLAUDE_CONFIG_DIR the same as Power Claude account groups?

No. Config dirs separate logins. Groups separate persona membership + optional local projects/memory isolation and an explicit active selection. Use both for a clean Mac setup.

Do I need a second Desktop app if I only use VS Code and Claude Code?

Usually no. Dual CLAUDE_CONFIG_DIR profiles plus Power Claude groups cover most engineering workflows without maintaining a second signed Desktop bundle.

Can I put any accounts in any group?

Yes. Membership is free-form. Name groups anything useful (Work, Personal, Client-Acme) and drag or pc scope add any linked login.

Will account groups delete my old sessions?

No. Isolation re-homes context roots for members; it does not wipe history. Apply fails closed on conflicts.

Does this bypass Anthropic rate limits?

No. Limits remain per Anthropic account and plan. Groups organize seats and local memory only. Optional rotation features, if enabled, are a separate product decision with their own warnings.

Where is group state stored on Mac?

Group definitions live under ~/.power-claude/state/account-scopes.json (restricted permissions). Isolated trees live under ~/.power-claude/claude-shared/scopes/<id>/.

How do I clear the active group?

Dashboard Clear active group or pc scope use none.

Where is the full groups model documented?

Account groups deep dive, work vs personal how-to, and setup docs.

Setup checklist (Mac)

Create ~/.claude-personal and ~/.claude-work (or your preferred names).
Add shell aliases; login once per profile; confirm with /status.
Unset stray ANTHROPIC_API_KEY when you want subscription billing.
Install Power Claude; link both profiles under Your Profiles.
Create isolated groups Work and Personal (or your names).
Drag each login into the correct group.
Use Work before work sessions; Use Personal before personal sessions.
Verify with pc scope list and a quick memory-tree check.
Optional: second Desktop app only if you need dual Desktop UIs.
Optional: direnv + pc scope use per repo for habit automation.

Independent third-party software. Not affiliated with Anthropic.

{{{_source.title}}} {{#_source.showPrice}} {{{_source.displayPrice}}} {{/_source.showPrice}}