multi-cli

multi-cli

Run multiple account profiles for AI coding tools simultaneously.

By default, each profile gets separate account credentials while conversations, configuration, agents, skills, and plugins stay shared where the tool allows it. Use --isolated when you want the entire tool home separated. Tools whose login cannot be separated safely use OS-user isolation instead. See the support matrix for per-platform requirements.

Profiles created by older multi-cli versions keep their whole-root behavior until migrated — see Legacy Profiles.

Supported Tools

17 adapters ship in this repository. Status is per operating system and binary: supported means multi-cli provides account isolation on that OS (any mode requirements are noted), and unsupported means no isolation mode works there. The authoritative source is docs/support-matrix.md.

Tool	Kind	Windows	macOS	Linux
Claude Code	CLI	supported (file overlay)	supported for API-key profiles only; subscription OAuth is unsupported	supported (file overlay)
OpenAI Codex CLI	CLI	supported (file overlay; file credential store mode)	supported	supported
Gemini CLI	CLI	supported (file overlay)	supported	supported
OpenCode	CLI	supported (`--isolated` whole-root)	supported (`--isolated` whole-root)	supported (`--isolated` whole-root)
Command Code	CLI	supported (file overlay; use `commandcode`, bare `cmd` collides with cmd.exe)	supported	supported
Cursor Desktop	IDE	supported (`--isolated` whole-root)	supported (`--isolated` whole-root)	supported (`--isolated` whole-root)
Cursor CLI	CLI	supported (process token via `multi-cli auth set`)	supported	supported
Antigravity	IDE	supported (OS-user isolation; elevated terminal)	unsupported (owned-user GUI/Keychain session not proven)	unsupported (owned-user GUI/Secret Service session not implemented)
AGY CLI	CLI	supported (OS-user isolation; elevated terminal)	unsupported (owned-user Keychain isolation not proven)	unsupported (owned-user Secret Service session not implemented)
Kiro	IDE	supported (OS-user isolation)	supported (`--isolated` whole-root)	supported (`--isolated` whole-root)
Zed	IDE	supported (OS-user isolation; elevated terminal)	unsupported (owned-user GUI/Keychain session not proven)	unsupported (owned-user GUI/Secret Service session not implemented)
Devin Desktop / Windsurf	IDE	supported (OS-user isolation; elevated terminal)	supported (`--isolated` whole-root)	supported (`--isolated` whole-root)
GitHub Copilot CLI	CLI	supported (process token via `multi-cli auth set`)	supported	supported
Copilot in VS Code	IDE	supported (OS-user isolation; elevated terminal)	unsupported (owned-user GUI/Keychain session not proven)	unsupported (owned-user GUI/Secret Service session not implemented)
Kimi Code CLI	CLI	supported (process token via `multi-cli auth set`)	supported	supported
Codex Desktop App	IDE	supported (OS-user isolation when the Store app is installed)	unsupported (owned-user GUI/Keychain session not proven)	unsupported (no desktop app)
Grok Build CLI	CLI/TUI	supported (process token via `multi-cli auth set`)	supported	supported

Each tool has its own folder at the repo root with an adapter.json describing the account boundary, the shared normal state, and the per-OS support status.

Install

macOS / Linux

curl -fsSL https://raw.githubusercontent.com/Spielewoy/multi-cli/main/scripts/install.sh | bash

Windows — open PowerShell:

irm https://raw.githubusercontent.com/Spielewoy/multi-cli/main/scripts/install.ps1 | iex

After install, restart your terminal for PATH changes to take effect.

From source

git clone https://github.com/Spielewoy/multi-cli.git
cd multi-cli
./scripts/install.sh --local        # macOS/Linux
.\scripts\install.ps1 -Local        # Windows

After install, restart your terminal for PATH changes to take effect.

jq is installed automatically by the installer on all platforms — no manual setup required.

Quick Start

# Create a profile
multi-cli new claude-cli/work

# Launch it
multi-cli launch claude-cli/work

# Or use the shorthand
multi-cli claude-cli/work

Each profile gets an automatic shell alias:

Platform	Location
macOS / Linux	`~/MultiCliProfiles/bin/` (add to `PATH`)
Windows	CLI aliases in `~/MultiCliProfiles/bin/`; Start Menu shortcuts for GUI profiles

Commands

Profile Management

Command	Description
`multi-cli new <tool>/<name>`	Create an account profile (credentials separate; normal state shared)
`multi-cli new <tool>/<name> --isolated`	Fully isolated schema-v2 profile — shares nothing (whole tool root inside the profile)
`multi-cli new <tool>/<name> --shared`	Legacy schema-v1 shared profile; schema-v2 profiles already share declared normal state by default
`multi-cli new <tool>/<name> --from <tpl>`	Create from a saved template
`multi-cli <tool>/<name>`	Launch a profile (shorthand)
`multi-cli launch <tool>/<name>`	Launch a profile
`multi-cli list [<tool>]`	List all profiles
`multi-cli status`	List profiles with their type and disk size
`multi-cli clone <tool>/<src> <tool>/<dest>`	Copy an existing profile
`multi-cli rename <tool>/<old> <tool>/<new>`	Rename a profile
`multi-cli delete <tool>/<name>`	Delete a profile and all its data

Account Authentication & Migration

Command	Description
`multi-cli auth set <tool>/<profile>`	Store the profile's process-secret credential in the OS credential store (prompts interactively, or reads one line from stdin)
`multi-cli auth status <tool>/<profile>`	Report whether a credential is stored for the profile
`multi-cli auth clear <tool>/<profile>`	Remove the stored credential
`multi-cli migrate <tool>/<name> [--dry-run] [--prefer-profile]`	Migrate a legacy schema-v1 profile to schema-v2

auth applies only to adapters that use the processSecret mechanism (cursor-cli, copilot-cli, kimi-cli, grok-cli). Launch stays disabled until a credential is stored. See Legacy Profiles for migrate.

Templates

Command	Description
`multi-cli template save <tool>/<profile> <name>`	Save a profile as a reusable template
`multi-cli template list`	List saved templates
`multi-cli template delete <name>`	Remove a template

Backup & Transfer

Command	Description
`multi-cli export <tool>/<name> [path]`	Archive a profile to `.tar.gz` (`.zip` on Windows)
`multi-cli import <archive> <tool>/<name>`	Restore a profile from an archive

Sessions

Command	Description
`multi-cli continue <tool> <src> <dest>`	Copy conversation state (sessions/transcripts/history) from one profile to another — never credentials
`multi-cli continue <tool> <src> <dest> --no-merge`	Overwrite destination files instead of keeping newer ones
`multi-cli continue <tool> <src> <dest> --dry-run`	Preview what would be copied, change nothing

base works as a profile name on either end and means the tool's real home dir (~/.codex, ~/.claude, …). Supported for codex, claude-cli, gemini-cli, and commandcode. See Continue a Chat Across Accounts.

Utilities

Command	Description
`multi-cli tools`	List all supported tools and their install status
`multi-cli stats`	Show disk usage per profile
`multi-cli doctor`	Diagnose your environment
`multi-cli completion {bash\|zsh\|powershell}`	Set up shell tab-completion
`multi-cli help`	Show help
`multi-cli version`	Show version

How Isolation Works

Schema-v2 adapters declare an account mechanism separately from normal state:

Mechanism	How it works
`fileOverlay`	Credentials stay under the profile; declared normal state links to the native shared tool home.
`processSecret`	A per-profile, highest-precedence credential is injected into only the child process. Launch remains disabled until secure secret storage is configured.
`osUserCredentialStore`	Fixed keychain identities are separated with a multi-cli-owned OS user. Provisioning requires an elevated terminal on Windows.
`inseparable`	The vendor combines auth and normal state; compliant launch fails closed and the limitation is shown.

Version-1 profiles retain the earlier whole-root env, userDataDir, redirectHome, appdata, and sandboxUser behavior for compatibility. Each <id>/adapter.json states product/platform capabilities and per-OS support status.

Shared vs Isolated Profiles

Profiles are shared by default: account credentials are separate, while conversations, configuration, and skills use the tool's normal shared location. --isolated puts the tool's entire home/config directory inside the profile, so nothing is shared. Isolated profiles can still be used with continue to copy supported conversations between accounts. For tools whose login cannot be split from normal state, --isolated is the direct whole-root option and avoids creating a separate OS user.

multi-cli new codex/acme --isolated   # CODEX_HOME is the profile dir; ~/.codex is never touched

Continue a Chat Across Accounts

Hit a rate limit on account A mid-conversation? Switch to a profile logged into account B and pick the chat up where it stopped. multi-cli continue copies the portable conversation state — sessions, transcripts, history — between profiles. Credentials are never copied.

# You were working in codex/work (account A) and got rate-limited.
# codex/personal is logged into account B.
multi-cli continue codex work personal          # copy the conversation state
multi-cli continue codex work personal --dry-run  # preview first, if you like

codex-personal                                  # launch account B's profile
codex resume <session-id>                        # resume the same chat (codex ≥ 0.30)

Run codex resume with no argument to open an interactive picker of past sessions, so you never have to look up an id. If you do need it, the session id is the UUID in the rollout filename under sessions/YYYY/MM/DD/.

base is a valid profile name on either end and refers to the tool's real home dir (~/.codex, ~/.claude, …), so you can continue to or from your default install.

By default, files are merged — newer files in the destination are kept. Pass --no-merge to overwrite the destination instead, or --dry-run to preview without changing anything.

After copying, resume inside the destination profile with the tool's own command:

Tool	Resume command
codex	`codex resume <session-id>` (≥ 0.30)
claude-cli	`claude --resume <session-id>` (run from the same project directory)
gemini-cli	`gemini --resume` (auto-saved last session) or `/chat resume <tag>` for saved checkpoints
commandcode	launch from the same working directory

Not supported: opencode (sessions and credentials live in one shared SQLite database) and cursor (chats are stored in SQLite keyed to the workspace path).

Legacy schema-v1 profiles are seeded from base by default. Schema-v2 account profiles already read declared conversations and configuration from the shared native root; isolated profiles start empty. Use multi-cli continue to copy supported conversations into or out of an isolated profile.

Profile Types

Flag	Meaning
(none)	Account profile — separate credentials with declared conversations/config shared through the native tool root.
`--isolated`, `--isolate`, `-i`	Whole-root isolated — shares nothing with the native tool root.
`--shared`	Legacy shared profile — links settings/extensions for schema-v1 adapters; cannot be combined with `--isolated`.
`--cli`	CLI — marks the profile for terminal-only launch (skips GUI discovery).
`--from <tpl>`	Create from a validated, credential-free template.

Environment Variables

Variable	Default	Purpose
`MULTICLI_HOME`	`~/MultiCliProfiles`	Where all profiles are stored
`MULTICLI_OVERRIDE_BINARY`	(unset)	Force a specific binary path for the next launch
`MULTICLI_REPO`	(unset)	Git URL for remote install
`MULTICLI_PLATFORM`	(auto)	Override platform detection (`darwin`, `linux`)

Legacy Profiles

Profiles created before schema-v2 are legacy whole-root profiles: they keep the earlier env, userDataDir, redirectHome, appdata, and sandboxUser behavior for compatibility. A profile directory without a .profile.json file is treated as legacy.

multi-cli migrate <tool>/<name> converts a legacy profile to schema-v2: declared credentials move into the profile, and declared normal state links to the shared tool home. Use --dry-run to preview the move plan without changing anything, and --prefer-profile to replace conflicting shared files with the profile's copy — credential targets are never overwritten. Profile storage and the shared state root must be on the same volume, because migration uses atomic same-volume moves.

Diagnostics

multi-cli doctor

Checks that your profile storage exists, alias directory is in PATH, and each tool's binary is detected (or shows an install hint).

Shell Completion

multi-cli completion bash   # or zsh, powershell

Follow the instructions to add it to your .zshrc, .bashrc, or PowerShell $PROFILE.

Uninstall

macOS / Linux

curl -fsSL https://raw.githubusercontent.com/Spielewoy/multi-cli/main/scripts/uninstall.sh | bash

Windows

irm https://raw.githubusercontent.com/Spielewoy/multi-cli/main/scripts/uninstall.ps1 | iex

You'll be asked whether to remove your profile data — nothing is deleted without confirmation.

Links

Support matrix — per-product, per-OS isolation status and mode requirements
Security policy
License
GitHub repository

Credits

Creator — Spielewoy

License

MIT

Name		Name	Last commit message	Last commit date
Latest commit History 37 Commits
.github/workflows		.github/workflows
agy-cli		agy-cli
antigravity		antigravity
claude-cli		claude-cli
codex-gui		codex-gui
codex		codex
commandcode		commandcode
copilot-cli		copilot-cli
copilot-vscode		copilot-vscode
cursor-cli		cursor-cli
cursor		cursor
docs		docs
gemini-cli		gemini-cli
grok-cli		grok-cli
kimi-cli		kimi-cli
kiro		kiro
lib		lib
opencode		opencode
schema		schema
scripts		scripts
tests		tests
windsurf		windsurf
zed		zed
.gitattributes		.gitattributes
.gitignore		.gitignore
.simplecov		.simplecov
LICENSE		LICENSE
README.ar.md		README.ar.md
README.es.md		README.es.md
README.he.md		README.he.md
README.md		README.md
README.ru.md		README.ru.md
README.zh.md		README.zh.md
SECURITY.md		SECURITY.md
multi-cli		multi-cli
multi-cli.ps1		multi-cli.ps1

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Repository files navigation

multi-cli

Supported Tools

Install

From source

Quick Start

Commands

Profile Management

Account Authentication & Migration

Templates

Backup & Transfer

Sessions

Utilities

How Isolation Works

Shared vs Isolated Profiles

Continue a Chat Across Accounts

Profile Types

Environment Variables

Legacy Profiles

Diagnostics

Shell Completion

Uninstall

Links

Credits

License

About

Releases

Packages

Contributors

Languages

Folders and files

Latest commit

History

Repository files navigation

multi-cli

Supported Tools

Install

From source

Quick Start

Commands

Profile Management

Account Authentication & Migration

Templates

Backup & Transfer

Sessions

Utilities

How Isolation Works

Shared vs Isolated Profiles

Continue a Chat Across Accounts

Profile Types

Environment Variables

Legacy Profiles

Diagnostics

Shell Completion

Uninstall

Links

Credits

License

About

Topics

Resources

Security policy

Stars

Watchers

Forks

Releases

Packages

Contributors

Languages