Multi-CLI

What does this agent do, and when should you use it?

Multi-CLI is a cross-platform command-line manager that gives Claude Code, Codex CLI, Gemini CLI, Cursor CLI and 13 other AI coding tools independent account profiles, so several accounts can stay usable side by side. Isolation is chosen per tool: a file overlay separates only declared credential files, a process secret injects one credential into the child process, and OS-user or isolated tool-home modes go further. Beyond profile creation, it ships session-transfer (continue), credential-free templates, schema-v2 export/import, legacy migration and a doctor diagnostic. It is implemented as Bash and PowerShell scripts installed from install/, stores profiles under ~/MultiCliProfiles by default, and creates per-profile shell aliases such as claude-cli-work. Multi-CLI never calls a model itself — the managed AI tool still performs all model traffic.

Running multi-cli new <tool>/<name> scaffolds a profile using the narrowest isolation the target tool supports (file overlay, process secret, OS user or isolated tool home) and writes a shell alias such as claude-cli-work into ~/MultiCliProfiles/bin/. Invoking multi-cli <tool>/<name> or multi-cli launch <tool>/<name> [-- args...] starts that tool under the selected profile; tools that use a process secret first need multi-cli auth set, which stores the key in the OS credential store. Day-to-day maintenance is covered by list, clone, rename, delete, status and stats. The continue command copies session state between codex, claude-cli, gemini-cli and commandcode profiles (never credentials), template save produces credential-free schema-v2 templates, export/import moves schema-v2 profiles, migrate upgrades legacy profiles, and doctor [--deep] audits the setup and runtimes. Behaviour is tunable through MULTICLI_HOME, MULTICLI_OVERRIDE_BINARY, MULTICLI_REPO and MULTICLI_INSTALL_DIR.

1. A developer holding both a personal and a work Claude Code subscription who wants both signed in at the same time.
2. Someone whose Codex account hits its usage limit and who needs to move the existing conversation to another account.
3. A freelancer using separate Gemini CLI or Cursor CLI accounts per client, with credentials that must not leak between them.
4. A team that wants to distribute credential-free profile templates and let each member fill in their own keys.
5. A developer working across macOS, Linux and Windows who wants one consistent account-management workflow.

How do you install or deploy this agent?

Check prerequisites first: Bash 3.2 or newer on macOS/Linux, Windows PowerShell 5.1 on Windows; jq 1.7.1 is installed automatically when missing. Installing from source requires Git.

macOS / Linux:

git clone https://github.com/Spielewoy/multi-cli.git
cd multi-cli
./install/install.sh --local

Windows PowerShell:

git clone https://github.com/Spielewoy/multi-cli.git
cd multi-cli
.\install\install.ps1 -Local

Restart the terminal if multi-cli or a new profile alias is not found afterwards.

How do you use this agent?

Diagnose the environment, then create and launch your first profile:

multi-cli doctor
multi-cli new claude-cli/work
multi-cli claude-cli/work

Tools that use a process secret (for example cursor-cli) need one extra credential step:

multi-cli new cursor-cli/work
multi-cli auth set cursor-cli/work
multi-cli cursor-cli/work

Request a fully separate tool home when the tool supports it:

multi-cli new codex/personal --isolated

Preview and then perform a session move between accounts:

multi-cli continue codex work personal --dry-run
multi-cli continue codex work personal
multi-cli codex/personal

List every command:

multi-cli help

What are this agent's strengths and limitations?

How does this agent compare with similar options?

Key facts side by side with the most closely related agents.

How does FollowAgents rate this agent?

FAQ