ditto-cli-0.2.0 is not a library.

Ditto CLI

Keep work, personal, and client Claude Code and Codex logins apart.

Ditto CLI gives each profile its own authentication, settings, and session history. Pick a profile in the terminal, sign in through the official CLI, then launch Claude Code or Codex. Your existing setup stays available as the default profile.

Ditto CLI takes its name from the shape-shifting Pokémon: one small tool, whichever coding identity you need.

┌────────────────── Ditto CLI  choose a profile, then a tool ──────────────────┐
├─ Profiles ───────────────┬─ Selected profile ─────────────────────────────────┤
│  default  existing       │ work  Isolated profile                            │
│› work                    │                                                    │
│  personal                │ Authentication                                     │
│                          │ Claude Code  ● Signed in                            │
│                          │ Codex        ○ Sign in required                     │
├──────────────────────────┴────────────────────────────────────────────────────┤
│ c open Claude   x open Codex   l sign in   o sign out                         │
│ ↑/↓ select   n new profile   e rename   r refresh   q quit                   │
└───────────────────────────────────────────────────────────────────────────────┘

Why use it?

Claude Code and Codex both keep user-level configuration and login state in a home directory. That works until you need separate accounts for different jobs. Manually moving auth files around is easy to get wrong, and it is hard to tell which account a new session will use.

Ditto CLI launches each tool with a profile-specific home directory:

Tool	Setting used by Ditto CLI
Claude Code	`CLAUDE_CONFIG_DIR=~/.ditto/profiles/<name>/claude`
Codex	`CODEX_HOME=~/.ditto/profiles/<name>/codex`

No config files are swapped. Profiles remain independent, and switching only affects the process launched by Ditto CLI.

Requirements

Install at least one of the supported CLIs:

Building Ditto CLI requires Rust 1.85 or newer.

Install

From crates.io:

cargo install ditto-cli

From the latest GitHub source:

cargo install --git https://github.com/reyanshgupta/ditto-cli

From a local checkout:

git clone https://github.com/reyanshgupta/ditto-cli.git
cd ditto-cli
cargo install --path .

Make sure Cargo's binary directory is in your PATH:

export PATH="$HOME/.cargo/bin:$PATH"

Ditto CLI installs as ditto-cli. macOS already uses ditto for its built-in file-copy utility at /usr/bin/ditto.

Quick start

Open Ditto CLI:

ditto-cli

Then:

Press n and name the profile, such as work.
Select it and press l.
Choose Claude Code with c or Codex with x.
Complete the official login flow. Ditto CLI returns to the profile screen afterward.
Press c or x to launch the tool.

Repeat the sign-in step for the other CLI if the profile uses both.

TUI controls

Key	Action
`↑` / `↓` or `k` / `j`	Select a profile
`c`	Launch Claude Code
`x`	Launch Codex
`l`	Sign in with Claude Code or Codex
`o`	Sign out, with confirmation
`n`	Create a profile
`e`	Rename the selected profile
`r`	Refresh authentication status
`q` or `Esc`	Quit or close a dialog

The selected profile is remembered for the next run.

Renaming keeps the profile's logins, settings, and session history. The built-in default profile cannot be renamed.

Command-line usage

The TUI is optional. Every launch command works directly from the shell:

# Profiles
ditto-cli create work
ditto-cli rename work client-a
ditto-cli list
ditto-cli status client-a
ditto-cli paths client-a

# Launch a tool
ditto-cli claude client-a
ditto-cli codex client-a

# Pass arguments to the underlying CLI after --
ditto-cli claude client-a -- --model opus
ditto-cli codex client-a -- --search

If the profile name is omitted, Ditto CLI uses the last selected profile. Before the first selection it uses default.

You can also call the native authentication commands through a profile:

ditto-cli claude client-a -- auth login
ditto-cli codex client-a -- login

Where credentials are stored

Ditto CLI does not ask for passwords, parse OAuth tokens, or keep credentials in its state file. The login action runs the installed Claude Code or Codex CLI with the selected profile directory, so each vendor's own authentication flow remains responsible for credential storage.

Codex keeps its auth state under the selected CODEX_HOME. Claude Code uses the selected CLAUDE_CONFIG_DIR; on macOS, sensitive Claude credentials remain in the system Keychain.

Ditto CLI's files are laid out like this:

~/.ditto/
├── state.toml
└── profiles/
    ├── work/
    │   ├── claude/
    │   └── codex/
    └── personal/
        ├── claude/
        └── codex/

Directories are created with user-only permissions on Unix systems.

The default profile points to ~/.claude and ~/.codex. It exposes your existing setup without copying or migrating anything.

Environment variables

Variable	Purpose
`DITTO_HOME`	Move Ditto CLI's state and profile directory from `~/.ditto`
`DITTO_CLAUDE_BIN`	Override the `claude` executable
`DITTO_CODEX_BIN`	Override the `codex` executable

Example:

DITTO_HOME="$HOME/.config/ditto" ditto-cli

ANTHROPIC_API_KEY, ANTHROPIC_AUTH_TOKEN, and OPENAI_API_KEY are inherited by launched tools. They may override a saved subscription login, so Ditto CLI shows a warning when one is set.

Remove Ditto CLI

Uninstall the binary:

cargo uninstall ditto-cli

Profiles are deliberately left alone. If you no longer need their settings, sessions, or credentials, remove ~/.ditto yourself.

Development

cargo test
cargo fmt --check
cargo clippy --all-targets -- -D warnings

License

Ditto CLI is available under the MIT License.

Ditto CLI is an independent project. It is not affiliated with Anthropic, OpenAI, Nintendo, or The Pokémon Company.

ditto-cli 0.2.0