Switch Claude, Codex, and Gemini Together

If you use Claude Code, Codex CLI, and Gemini CLI together on the same project, say, for a client engagement where all three need to authenticate as that client, switching each one individually after every context change gets old fast. A context collapses that into one command.

Set it up

1. Make sure you have a profile per tool for this setup.

aisw add claude client-acme --from-live
aisw add codex client-acme --api-key "$CLIENT_ACME_OPENAI_KEY"
aisw add gemini client-acme

2. Group them into a context.

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

The context name and the profile names don’t have to match, using the same name for both here is just convenient, not required.

3. Switch everything at once.

aisw context use client-acme

4. Switch back just as easily.

aisw context use personal

(Assuming a personal context exists with the same structure.)

Desktop method

The current public AI Switcher Desktop release covers macOS, Windows x64, and Linux x64. Download the matching build from /download/, then create and activate the context through the desktop flow below.

1. Open Contexts in AI Switcher Desktop.
2. Click New context, name it, and map a profile from each tool.
3. Click Activate to switch all mapped tools together.

Verify the result

aisw status

Confirms the active profile for each tool and, if they match a defined context, names it, so you can tell at a glance the whole setup switched correctly.

Common problems

If aisw context use only switches some of the tools, check that the context actually maps a profile for each one with aisw context show client-acme, a tool left out of the mapping is left untouched by design, not a bug.