aisw CLI
For terminal-first workflows: shell hooks, JSON output, automation, repository guardrails, and exact commands.
Explore the CLISave work, personal, and client accounts as named profiles. Switch Claude Code, Codex CLI, Gemini CLI, or Antigravity CLI deliberately, then verify the account before it touches the repository.
A profile represents one account for one tool. A context groups the profiles that belong to a work, personal, or client setup. A workspace rule binds that context to a repository and can warn or block when the active account is wrong. The sequence is simple: select, verify, then start the agent.
Capture the live login or add a provider account under a name that explains its boundary.
$ aisw add claude work --from-live
$ aisw add claude personalChoose the account for the next session and compare the selected profile with live state.
$ aisw use claude work
$ aisw status --tool claude
$ aisw verifyBind a repository to its expected context and move from warnings to strict enforcement when ready.
$ aisw workspace bind . --context work
$ aisw workspace guard --mode strictAI Switcher uses one profile and context model across the four agents. Credential locations and isolation capabilities still belong to each provider.
| Capability | Claude Code | Codex CLI | Gemini CLI | |
|---|---|---|---|---|
| Named account profiles | Yes | Yes | Yes | Yes |
| Switch one tool at a time | Yes | Yes | Yes | Yes |
| Cross-tool contexts | Yes | Yes | Yes | Yes |
| Repository guardrails | Yes | Yes | Yes | Yes |
| Isolated local state | Yes | Yes | Yes | No |
For terminal-first workflows: shell hooks, JSON output, automation, repository guardrails, and exact commands.
Explore the CLIFor visual account checks: review active profiles, contexts, diagnostics, and backups before changing the live setup.
See Desktop workflowsDirect answers for developers deciding how to manage more than one coding-agent account on one machine.
It is a local tool for saving named accounts for coding agents, selecting the account needed for a session, and checking that the active state matches the project. AI Switcher supports Claude Code, Codex CLI, Gemini CLI, and Antigravity CLI.
Yes. Save work, personal, and client logins as separate profiles, group profiles into contexts when several tools change together, and bind repositories to the context they should use.
Use the CLI for shell hooks, automation, scripting, and repeatable commands. Use Desktop when you want a visual view of active profiles, contexts, diagnostics, and repository bindings. Both interfaces use the same local state.
No. AI Switcher is local-only. It works with the credential files and system keyrings already used by the upstream tools and does not proxy model traffic or sync credentials to a backend.