People searching for a Claude Code account switcher usually have a work account and a personal account on the same computer. The problem is not choosing a label in a menu. It is making sure Claude Code, the terminal, and the repository all agree about which account is active.
Save the accounts you want to switch between
Install aisw, initialize its local store, and capture the account that Claude Code is already using. Add another account through Claude Code's normal sign-in flow, then list the saved profiles before switching.
aisw init
aisw add claude work --from-live
aisw add claude personal
aisw list claudeProfile names are local labels. AI Switcher does not create Claude subscriptions, proxy prompts, or upload credentials. It manages the local credential and configuration boundary that Claude Code already expects.
Switch before opening a new Claude Code session
Activate the account that matches the task, confirm the state, and then launch Claude Code. A running process may retain its old environment, so changing the selected profile is not a hot swap inside an existing conversation.
aisw use claude work
aisw status
aisw verify
claude
aisw use claude personal
claudeSwitch Claude Code accounts without logging out
You do not need to repeatedly sign out and sign back in just to move between saved accounts. Activate the intended profile, verify it, and start a new Claude Code process. Use the provider's normal login flow only when adding a new account or refreshing one.
aisw use claude personal
aisw verify
claudeUse a Windows or VS Code account-switcher workflow
The commands are the same on Windows. The --credential-backend flag controls where aisw stores the managed profile secret; it does not change Claude Code's own live authentication backend. Start a new PowerShell or VS Code terminal after switching so the process receives the selected environment.
aisw add claude work --credential-backend system-keyring
aisw add claude personal --credential-backend system-keyring
aisw use claude work
aisw verifyMake the repository choose the expected account
Manual switching is easy to forget. For client or production repositories, bind the directory to a context and begin in warn mode. Once the mapping is correct, strict mode stops a launch under the wrong Claude Code account.
aisw context create client-acme --claude client-acme
aisw workspace bind . --context client-acme
aisw workspace guard --mode warn
aisw workspace guard --mode strictWhen Claude Code says the old account is still active
Quit and relaunch Claude Code after an account switch. Then run aisw status andaisw verify. If the installed Claude build uses a shared Keychain entry that cannot be isolated, aisw reports that limitation instead of pretending the profile is durable. Follow the provider's normal sign-in flow and use the supported storage mode.
CLI or Desktop?
Use the CLI when switching belongs in a shell hook, script, or repository setup. Use AI Switcher Desktop when you want to inspect the active Claude Code profile visually before activating it. Both operate on the same local profile model.
For the shortest command-by-command walkthrough, read How to Switch Claude Code Accounts. For the broader one-computer workflow, see how to use multiple Claude Code accounts.