What each coding agent supports.

OAuth and API-key profiles, state-mode behavior, and platform support differ slightly by provider. This page reflects the current aisw CLI implementation.

Capability Claude Code Codex CLI Gemini CLIAntigravity CLI
OAuth profilesYesYesEnterpriseYes
API key profilesYesYesYesYes, GEMINI_API_KEY
Import current loginYesReadable auth.json onlyYesYes
Isolated stateWhere auth is profile-scopedYesYesNo
Shared stateYesAPI-key profiles onlyNoYes
macOSYesYesYesYes
WindowsYesYesYesYes
LinuxYesYesYesYes

Credential locations

Claude Code stores credentials in the macOS Keychain or local files, depending on how it was installed. Codex CLI stores credentials in auth.json or a system keyring. Gemini CLI stores credentials in files under ~/.gemini. Antigravity CLI uses a system-keyring-backed live session and provider selection in ~/.gemini/antigravity-cli/settings.json. Antigravity switching preserves global preferences, MCP integrations and updater state rather than restoring entire configuration trees. For exact paths and keyring specifics per tool, see the CLI reference for supported tools.

Keyring behavior

Where a tool uses a system keyring, AI Switcher talks to the platform-native backend directly: Keychain on macOS, Credential Manager on Windows, and Secret Service on Linux. No credential passes through a third-party service to reach the keyring.

For Codex, native keyring-only and ephemeral sessions are not imported. The CLI captures readable auth.json; native auto storage is importable only when it has produced that file. An aisw-managed profile may store its secret in the OS keyring and apply it through Codex file storage. That is separate from Codex's native keyring.

Fail-closed cases

Importing a live account fails with an explicit error rather than silently succeeding when the source credential can't be read cleanly, for example, when a Codex auth.json can't be parsed, or when adding a profile would collide with an existing one without--force. AI Switcher does not guess at ambiguous credential state.

State-mode differences

Claude Code supports isolated state where authentication is scoped to the profile'sCLAUDE_CONFIG_DIR. Legacy shared macOS Keychain OAuth requires shared mode. Codex ChatGPT-managed accounts require their own isolated CODEX_HOME and independent sign-in; imported ChatGPT credentials are bootstrap copies. Codex shared mode supports API-key profiles only. Gemini CLI keeps authentication and local state together under ~/.gemini, so it always runs isolated. A shared mode isn't structurally possible for Gemini today. Antigravity CLI is the inverse case: upstream does not currently expose a documented isolated auth root, so AI Switcher supports it through shared live switching only.

Gemini account eligibility

Google ended Gemini CLI access for individual free, Pro and Ultra sign-ins on June 18, 2026. Enterprise Code Assist, API-key and supported Vertex AI paths remain available. Use Antigravity CLI for individual Google accounts. An aisw profile changes local credentials, not upstream account eligibility.

Antigravity API-key profiles

Antigravity API-key profiles use GEMINI_API_KEY and selectmodelProvider: gemini. Use the shell hookor --emit-env so the key reaches the next agy process. OAuth switching restores the live keyring credential and removes that provider override.

Known limitations

AI Switcher Desktop v0.2.1 is publicly downloadable as an alpha release for macOS, Windows x64, and Linux x64. This page only claims desktop platform support where a public artifact exists. The aisw CLI remains available for macOS (Apple Silicon and Intel), Linux (ARM64 and x64), and Windows x64, with Antigravity CLI support included in the current matrix.

Release scope

This matrix describes the released aisw CLI contract reviewed against v0.3.11. The current CLI download is v0.3.11. Desktop v0.2.1 bundles its own runtime; see its release notes for scope. New CLI authentication fixes do not establish Desktop parity or fresh provider acceptance on every operating system.

Last verification date

CLI contract reviewed on October 31, 2026.

Supported-tools FAQ

This page answers compatibility-oriented searches from developers who want to know whether account switching is actually supported before they adopt the workflow.

Does AI Switcher support switching multiple accounts for Claude Code?

Yes. Claude Code supports saved profiles in AI Switcher, including importing a live login, switching between work and personal accounts, and participating in cross-tool contexts and repository guardrails.

Does AI Switcher support switching multiple accounts for Codex CLI?

Yes. Codex CLI accounts can be saved as named profiles, activated individually, and grouped into contexts with other tools. The exact behavior varies by auth backend and state mode, which is why this matrix documents the details.

Does AI Switcher support switching multiple accounts for Gemini CLI?

Yes, for eligible enterprise sign-ins, API-key and Vertex AI profiles. Individual free, Pro and Ultra Google sign-ins no longer work through Gemini CLI; use Antigravity CLI for those accounts. aisw restores Gemini-owned state while preserving Antigravity directories.

Can I use one switching workflow across all four tools?

Yes. Profiles are saved per tool, and contexts let you group those tool-specific profiles under one workspace or client name so you can switch the complete setup together, including Antigravity CLI where it is part of the workflow.

Does AI Switcher support switching multiple accounts for Antigravity CLI?

Yes. The aisw CLI supports saved OAuth and API-key profiles for Antigravity CLI. Switching applies credentials and provider selection while preferences, MCP integrations and runtime state remain shared. API-key profiles require GEMINI_API_KEY through the shell hook or --emit-env.