Open source. Local first.

Switch accounts across Claude Code, Codex CLI, Gemini CLI and Antigravity CLI.

AI Switcher gives work, personal and client accounts clear names. Switch one coding agent, an entire work context, or the expected account for each repository from the terminal or a desktop app.

Install aisw CLI Download desktop alpha

View source on GitHub

No cloud account
No telemetry
Native system keyrings
Atomic switching and rollback

Desktop alpha AI Switcher Desktop overview screen showing multiple coding-agent profiles with one tool selected and a healthy live-match state.

AI Switcher Desktop overview screen showing multiple coding-agent profiles with one tool selected and a healthy live-match state.

$ aisw context use client-acme
✓ Claude  acme-claude
✓ Codex   acme-codex
✓ Gemini  acme-gemini
✓ Agy     acme-antigravity

Works with

Claude Code
Codex CLI
Gemini CLI
Antigravity CLI

See the full compatibility matrix →

Four coding agents. Four different account systems.

Claude Code, Codex CLI, Gemini CLI, and Antigravity CLI store authentication in different files, keyrings, and configuration directories. Switching between work, personal, and client accounts often means logging out, copying hidden files, or wondering which account is still active.

AI Switcher turns each account into a named profile and gives you one place to switch and verify it.

Claude CodemacOS Keychain or local files
Codex CLIauth.json or system keyring
Gemini CLIfiles under ~/.gemini
Antigravity CLIsystem keyring and ~/.gemini config roots

AI Switcher profiles

Use the desktop app or stay in the terminal.

aisw CLI

Add profiles, switch accounts, bind repositories, verify state, and automate workflows with a fast Rust command-line tool.

Explore the CLI →

AI Switcher Desktop Alpha

See active profiles, switch contexts, review diagnostics, restore backups, and use Quick Switch without editing configuration files.

Download desktop alpha →

Give every account a clear name.

Save the account already in use, sign in through the provider's native flow, or add an API key. Profiles can be named work, personal, client-acme, or anything that matches how you actually work.

$ aisw add claude work --from-live$ aisw add claude personal$ aisw use claude work

Switch a complete work setup.

A context combines the right profile for each coding agent under one name. Use one command or one desktop action to move from personal work to a client project, even when profile names differ across providers.

$ aisw context create client-acme \    --claude acme-claude \    --codex acme-codex \    --gemini acme-gemini$ aisw context use client-acme

Keep the right account with the right repository.

Connect a repository, path, or Git remote to an expected context. AI Switcher can warn or block when the active accounts do not match the project you opened.

$ aisw workspace bind . --context client-acme$ aisw workspace guard --mode strict

Know what is active before you start coding.

AI Switcher checks the recorded profile, live provider state, context, local configuration, and workspace expectation. When something has drifted, it explains what changed and offers a deliberate repair path.

$ aisw verify

Built for the account-switching searches people actually make.

Most developers do not search for a profile manager. They search for concrete problems: how to switch between two Claude Code accounts, how to keep a personal Codex CLI account separate from a client one, how to stop the wrong Gemini CLI login from touching the wrong repository, or how to move Antigravity CLI between separate local accounts cleanly. AI Switcher is built around those exact workflows.

The core pattern stays simple: save an account once, give it a stable name, then switch to it deliberately. When one project needs three tools at once, save a context instead of repeating the switch per tool. When the risk is opening the wrong repository under the wrong account, bind that repository to its expected context and let guardrails enforce it.

How to switch Claude Code accounts How to switch Codex CLI accounts How to switch Gemini CLI accounts Manage client accounts across all three tools Prevent the wrong account in a repository Common switching situations

Common account-switching questions

These are the broad questions people ask before they decide whether a switching workflow is safe enough to rely on every day.

How do I switch between Claude Code, Codex CLI, Gemini CLI, or Antigravity CLI accounts?

Save each account as a named AI Switcher profile, then activate the one you need with one command. You can switch one tool at a time, switch all tools that share the same profile name, or switch a saved cross-tool context that maps different profiles together.

Can I keep work, personal, and client accounts separate on one machine?

Yes. AI Switcher is built for exactly that setup. You can keep separate named profiles per tool, group them into a work or client context, and bind repositories to the context they should use so the wrong account is caught before you start coding.

Does AI Switcher require a cloud account or proxy my prompts?

No. AI Switcher is local-only. It uses the credential files and system keyrings the upstream tools already use, without routing model traffic, inspecting prompts, or syncing credentials to a backend.

What if my profile names do not match across tools?

Use a context. A context lets Claude Code, Codex CLI, Gemini CLI, and Antigravity CLI each keep their own profile names while still switching as one saved setup, such as a personal workspace or a client account bundle.

Local credentials. Native provider behavior.

AI Switcher works with the credential locations and operating-system keyrings the upstream coding agents already use. It does not route model requests, inspect prompts, or upload credentials. Sensitive files use owner-only permissions, and switching snapshots the previous state before applying changes.