Claude Code Login: Manage Multiple Accounts

The short answer

For a one-time sign-in, use Claude Code’s native /login command. For work, personal, or client accounts that you will reuse, save each login as a named profile with AI Switcher:

aisw init
aisw add claude work
aisw add claude personal
aisw list claude

The provider still owns authentication. AI Switcher does not create Claude accounts, bypass login, or proxy model traffic; it gives each local account a name and a repeatable boundary.

Sign in through Claude Code

Start Claude Code and use its native /login flow when the current account is missing, expired, or needs to change. Complete the provider’s browser or terminal prompts, then confirm that the session is usable before saving it as a profile. Native login is the right first step because it keeps the account and credential format controlled by Claude Code.

If the account is already active and you only need to start managing it, import the live state instead of signing in again:

aisw add claude work --from-live
aisw status --tool claude
aisw verify

--from-live captures what the installed Claude Code build is already using. It does not turn a shared upstream Keychain credential into an independently isolated account owner.

Save a second account for repeatable switching

Run the native login flow for the second account, then save it under a name that describes its boundary:

aisw add claude personal
aisw list claude
aisw use claude personal
aisw status --tool claude
aisw verify

Start a new Claude Code process after the switch. A process that is already running can retain the old environment even when the profile registry has changed.

Keep work and personal accounts separate

When one repository must use one identity, bind it to a context and enable a workspace guard:

aisw context create work --claude work
aisw workspace bind . --context work
aisw workspace guard --mode strict

Use the Claude Code account-switching guide for the full switching workflow, or the repository guide when the account boundary belongs to a project.

When login appears stuck

Check the selected profile and live state from the same terminal that will launch Claude Code:

aisw status --tool claude
aisw verify

If the provider login succeeded but Claude Code still uses the old account, close the agent, open a fresh terminal or VS Code integrated terminal, select the intended profile, and launch a new process. Claude Code installations can also differ in whether OAuth is scoped by CLAUDE_CONFIG_DIR or backed by a shared live Keychain entry; AI Switcher reports that limitation instead of pretending the state is isolated.

For the upstream authentication behavior, follow Claude Code’s official documentation. For several accounts on one computer, continue with the work and personal account guide.