Claude Code account switchers compared

Running a work account alongside a personal one gets old when you have to sign out to switch. Several tools handle this now, and they take different approaches under the hood.

Updated

When you only need one account active at a time, a sign-in swapper keeps a single setup, and claude-swap lets a running session follow the switch. To keep two accounts open at once on the same setup, use a tool that gives each account its own config directory, like clausona or ccam. For Codex CLI, clausona and aisw support it alongside Claude Code, while codex-auth targets Codex alone.

How they compare

Each row covers one tool or one way to set this up by hand.

How each one switches

ToolWorks withHow it switchesTwo accounts at once
clausonaClaude Code, Codex CLIA config directory per accounta shell hook sets CLAUDE_CONFIG_DIR or CODEX_HOMEYesclausona run claude:work
ccamClaude CodeA config directory per accountstarted with ccam <name> or a shortcutYes
claude-swapClaude CodeSwaps the sign-in in ~/.claudecswap run gives an account its own config directoryYes, with cswap run
ClaudeCodeMultiAccountsClaude CodeSwaps the sign-in in ~/.claudeand ~/.claude.jsonNo, one active sign-ina switch waits until every Claude Code window closes
ccswitchClaude CodeWrites the sign-in into the shared configor exports it for one shellYes, per shella subscription sign-in needs a token from claude setup-token
aiswClaude Code, Codex CLIand Gemini CLI, Antigravity CLIWrites the saved sign-in where each tool reads itisolated mode, the default, also gives each profile its own directoryNo, one active sign-in per tool
codex-authCodex CLIand the VS Code extension, Codex AppCopies the account's auth.json into ~/.codexNo, one active sign-inrestart Codex after a switch
OrcaClaude Code, Codex CLIand other agentsA desktop app that starts agents on the account you pickYesrunning sessions keep their account when you switch
/logout and /loginClaude CodeCodex: codex logout, then codex loginSign out, sign in againin the browser, every timeNo
CLAUDE_CONFIG_DIR by handClaude CodeCodex: CODEX_HOMEA config directory per accountwith an aliasYes

Conversations and setup

ToolSame conversation on another accountSkills, plugins and settings
clausonaYes, once history is shared--merge-sessions, then claude --continue; codex resume on macOS and LinuxSharedskills, hooks, plugins, settings and CLAUDE.md; servers from claude mcp add stay per account
ccamYes, with history in a groupccam next --continueShared per groupMCP servers, settings, CLAUDE.md, extensions
claude-swapYesa session carries on after a switch; cswap run shares history by defaultShared, one ~/.claudecswap run links settings, CLAUDE.md, skills, commands and agents, copies MCP servers, and leaves out plugins
ClaudeCodeMultiAccountsOne historyone ~/.claudeShared, one ~/.claude
ccswitchOne historyunless a profile has its own config directoryShared, one ~/.claudeunless a profile has its own config directory
aiswSeparate in isolated modeone history in shared modeNot in isolated modeshared mode uses one directory
codex-authOne historyone ~/.codexShared, one ~/.codex
Orca—Codex settings, mirroredfrom ~/.codex/config.toml
/logout and /loginOne historyone ~/.claudeShared, one ~/.claude
CLAUDE_CONFIG_DIR by handIf you link projects/together with jobs/ and teams/What you link yourself

Usage and picking an account

ToolUsage of each accountPicks an account by usage
clausonaYes, clausona listweekly, and 5-hour on plans that have oneWhen a run startsdynamic routing, clausona run --route main; a running session never moves
ccamYes, ccam usage5-hour, weekly and per modelWhen you askccam next --auto, ccam pick, --fallback for -p runs; optional auto_switch on Linux and macOS
claude-swapYes, cswap list5-hour and 7-daySwitches the sign-in at a thresholdcswap auto, 90% by default; cswap switch --strategy best
ClaudeCodeMultiAccountsYes, ccs5-hour and 7-day, cached for accounts not in use—
ccswitch——
aisw——
codex-authYes, codex-auth list5-hour and weekly—the README points to its fork, codext, for automatic switching
OrcaYes, in the status bareach account's usage in the switcher—
/logout and /login/usagefor the account signed inNo
CLAUDE_CONFIG_DIR by hand/usagein each sessionNo

Platforms and install

ToolPlatformsInstall and licenseRuns in the background
clausonamacOS, Linux, Windowsinstall.sh, install.ps1 or npm, MITneeds Node.js 20 or laterNo daemon or proxya short step records token use after claude exits
ccamLinux, macOS, Windowsinstall.sh or install.ps1, a .deb or go install, MITone Go binaryNothing by defaultwith relay or auto_switch on, it waits beside the session
claude-swapmacOS, Linux, WindowsPyPI, with uv or pipx, MITPython 3.12 or laterOnly what you startcswap auto, or the macOS menu bar app
ClaudeCodeMultiAccountsWindows, WSL, macOS, Linuxnpm, with npx, MITNode.js 18 or laterA watcher while a switch waitsand a sign-in hook in settings.json
ccswitchmacOS, Windows, Linuxnpm, MITNode.js 18 or later—
aiswmacOS, Linux, WindowsHomebrew, a shell script or cargo, MITWindows builds on the releases pageNo
codex-authmacOS, Linux, Windowsnpm, MITNone of its ownreloads or restarts Codex's app-server daemon on a switch
OrcamacOS, Windows, LinuxA desktop download, Homebrew or the AUR, MITThe app itself runs the agents

Both manual setups need no extra install and leave nothing running in the background.

Compared from each project's README and docs in November 2026. A dash in a cell means we found no mention. Corrections are welcome: open an issue.

Swap one sign-in

Most switchers take this approach. Claude Code keeps one sign-in per config directory, so the tool keeps a saved copy for each account and writes the one you pick into place when you switch.

Everything else stays in that single folder. Because both accounts read the same settings and history, your two setups never drift apart.

The trade-off is that you can only use one account at a time. Every terminal and editor on the machine shares that active sign-in.

Active sessions behave differently depending on the tool. According to claude-swap, a running session picks up the new account on the next message on Linux and Windows, or within about 30 seconds on macOS. ClaudeCodeMultiAccounts waits until every Claude Code window closes before switching, while aisw and codex-auth require starting a new session.

Saved credentials also have to stay valid while Claude Code renews tokens in the background. The claude-swap README warns that running /logout may revoke the stored refresh token for the account you leave. To avoid writing in the middle of a token refresh, claude-swap acquires Claude Code's own credential locks during a switch.

Running /logout and /login does the same thing without an extra tool. You just have to go through the browser sign-in flow every time you switch.

A directory per account

Claude Code documents this method directly. Point CLAUDE_CONFIG_DIR at a separate folder for each account, and each folder holds its own sign-in. Codex works the same way with CODEX_HOME.

Both accounts stay signed in at once. You can run a work session in one terminal and a personal session in another, and Claude Code renews each token inside its own directory.

The catch is that a fresh directory starts empty. None of your settings, skills, plugins or history exist there until you symlink them from your main directory, and a Claude Code update can add a new folder that your links miss. The Claude Code guide covers setting those links up by hand.

Tools built around this model differ in what they link for you.

clausona links everything from your main directory except the sign-in and account-specific state. If a Claude Code update adds an unlinked folder, clausona doctor flags it. Conversation history stays separate per account until you turn on sharing.

ccam organizes accounts into groups. Each group defines what to share, like MCP servers or history, so two work accounts can share history while a personal account stays separate.

In claude-swap, cswap run links settings, CLAUDE.md, skills, commands and agents from ~/.claude, while sharing history by default. It leaves plugins out.

aisw defaults to isolated mode, giving each profile its own directory without sharing files between them.

MCP servers added via claude mcp add are written to .claude.json alongside account-specific state, so that file cannot be symlinked across accounts. clausona leaves those servers per account. ccam passes shared servers at launch using --mcp-config, while claude-swap copies them in on each run.

An app that launches agents

Orca is a desktop app for running coding agents side by side. Its status bar includes an account switcher for Claude Code and Codex that displays usage for each account.

Selecting an account in the status bar applies to the next agent Orca launches. Any session already running stays on the account it started with.

That switcher only affects sessions inside Orca. Codex accounts added in Orca use their own home directories and leave ~/.codex untouched, so running codex in an outside terminal still uses the ~/.codex sign-in.

If you already launch all your agents from Orca, its built-in switcher may cover what you need. You can also use clausona inside an Orca terminal: running clausona run claude:work starts Claude Code on that account, and the Orca guide walks through running a fleet there.

When clausona isn't the right pick

Because this is clausona's site, it is worth being direct about when another tool fits your setup.

If you only switch once a week and never run both accounts at the same time, /logout and /login handles it without installing anything.

If you want an active session to switch accounts mid-run when usage runs low, clausona won't do that. Its dynamic routing picks an account only when a run starts, and a running session never moves. Instead, claude-swap's cswap auto swaps the active sign-in at a usage threshold while Claude Code is running, and ccam can move a session after Claude Code hits a limit if auto_switch is enabled.

If you don't want Node.js on the machine, skip clausona, which requires Node.js 20 or later. ccam ships as a single Go binary, and aisw installs via Homebrew or cargo.

If you are on Windows and want zero new dependencies, the PowerShell steps in the Claude Code guide set up a second account using directory junctions and a shell function.

If you also switch accounts in Gemini CLI or Antigravity, aisw supports both alongside Claude Code and Codex.

If you only use Codex and also work in the Codex App or the VS Code extension, codex-auth lists both alongside the CLI.

Keep the accounts to what they're for, such as work and personal use, within Anthropic's and OpenAI's terms.

Questions

What is the best Claude Code account switcher?

That comes down to how you run your accounts. For using one account at a time where an open session follows the switch, look at claude-swap. For running two accounts side by side on a shared setup, clausona and ccam each give every account its own config directory. If Codex CLI is part of your workflow too, clausona and aisw handle both tools, while switching once a week only takes /logout and /login.

Can I keep the same conversation when I switch accounts?

Yes, provided both accounts read from the same session history. Tools that swap credentials inside a single ~/.claude folder share one history automatically, and claude-swap states that an active session can continue right after a switch. When each account has its own config directory, history stays separate unless you share it. In clausona, running clausona config claude:work --merge-sessions links session history so claude --continue resumes the latest conversation in that project regardless of which account started it. In ccam, accounts in a group can share history, and ccam next --continue resumes the conversation on the next account.

Can two Claude Code accounts run at the same time?

Yes, by giving each account its own config directory, as described in Claude Code's docs. You can launch an isolated session in one terminal with clausona run claude:work or ccam <name>, and claude-swap offers cswap run for the same purpose without touching other open terminals. With ccswitch, you can export an account per shell after generating a token via claude setup-token. Tools that only overwrite the main sign-in file limit you to one active account at a time.

Do any of these work for Codex CLI too?

clausona supports Codex CLI by setting a separate CODEX_HOME per account through the same shell hook, and clausona list reports Codex usage alongside Claude Code. aisw handles both Codex and Claude Code as well as Gemini CLI and Antigravity. For a Codex-only tool, codex-auth swaps the account's auth.json into ~/.codex, while Orca switches Codex accounts for the agents it launches. The docs for claude-swap, ccam, ClaudeCodeMultiAccounts and ccswitch do not mention Codex.

Will a switcher move my session when an account runs low?

A couple of them do. In claude-swap, cswap auto swaps the sign-in when the active account hits a usage threshold (90% by default), and the running session continues on the new account. On Linux and macOS, ccam can move a session after Claude Code stops at its limit when auto_switch is enabled. clausona never moves a running session; instead, its dynamic routing selects an account with remaining usage at launch when you run clausona run --route main. Keep the accounts to what they're for, such as work and personal use, within Anthropic's and OpenAI's terms.

Try clausona

clausona is free and open source. If it saves you a few sign-ins a day, starring the repo on GitHub helps other developers find it.

macOS and Linux curl -fsSL https://github.com/larcane97/clausona/releases/latest/download/install.sh | bash
Windows PowerShell irm https://github.com/larcane97/clausona/releases/latest/download/install.ps1 | iex
Any OS, with npm npm install -g clausona

npm doesn't edit your shell profile. If you install with npm, add the shell hook yourself as shown in the README.

Ready to set up a second account? Check the guides for multiple Claude Code accounts or multiple Codex CLI accounts.