Manage Multiple Client Accounts Across Claude Code, Codex CLI, and Gemini CLI

Freelancers and consultants juggling several clients face the same problem from three directions at once: separate Claude Code accounts, separate Codex CLI accounts, separate Gemini CLI accounts, and separate repositories that must never cross-contaminate. This guide combines contexts and workspace guardrails into one setup built specifically for that.

Set up a context per client

Repeat this for each client:

aisw add claude acme --api-key "$ACME_CLAUDE_KEY"
aisw add codex acme --api-key "$ACME_OPENAI_KEY"
aisw add gemini acme

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

Bind each client’s repositories

cd ~/code/acme-webapp
aisw workspace bind . --context acme

cd ~/code/acme-api
aisw workspace bind . --context acme

Repeat for every repository tied to that client. Multiple repositories can bind to the same context.

Turn on enforcement once

aisw workspace guard --mode strict

This applies to all bound repositories across all clients — you only need to set it once, not per client.

Daily use

Switching to a client’s full setup, whether or not you’re currently in one of their repositories:

aisw context use acme

Or just cd into a bound repository and let the shell hook catch a mismatch automatically before it launches a coding agent with the wrong account.

Desktop method (coming soon)

AI Switcher Desktop is currently in private testing and not yet available for public download. The steps below reflect the current build; use the CLI method above until it ships.

The Contexts list in AI Switcher Desktop shows every client at a glance, including how many repositories each is bound to and when it was last active — useful for a quick sanity check before a call or a handoff.

Verify the result

aisw context list
aisw workspace status

Confirms every client context exists with all three tools mapped, and that the repository you’re currently in (if any) matches its expected context.

Common problems

If two clients’ repositories are accidentally bound to the same context, aisw workspace status will show both under one context name — re-bind the misassigned repository with the correct --context value to fix it.