Skip to main content
CC Commander supports three install paths depending on how you use Claude. Path A gives you the full CLI experience. Path B installs skills and commands for use inside existing Claude Code sessions. Path C adds CC Commander as a Cowork plugin for Claude Desktop. All paths share the same one-liner installer — the difference is how you invoke CC Commander afterward.

​
System requirements

  • Node.js 18 or later — verify with node --version
  • git — required by the installer to clone the kit
  • tmux (recommended, not required) — needed for Split Mode, which runs each task in its own terminal window
The installer checks for Node.js and git before proceeding. It installs Claude Code CLI automatically via npm if it is not already present.

​
Choose your install path

Use this path if you run claude in your terminal. This is the most common path and gives you the full CC Commander experience.Step 1: Run the one-liner
curl -fsSL https://raw.githubusercontent.com/KevinZai/cc-commander/main/install-remote.sh | bash
Alternatively, install via npm:
npm install -g cc-commander
Step 2: Launch
ccc
Arrow keys to navigate. Enter to select. That is the entire interface.What you get: Full TUI with tmux Split Mode, 10 themes, the Cockpit Dashboard, daemon mode, and headless agent dispatch via ccc --dispatch.

​
What the installer does

The one-liner installer (install-remote.sh) performs the following steps:
  1. Checks for Node.js and git
  2. Installs Claude Code CLI if not already present (npm install -g @anthropic-ai/claude-code)
  3. Clones the CC Commander repository to ~/.cc-commander/ (or pulls the latest if already present)
  4. Runs install.sh --force, which copies skills, commands, hooks, libraries, and config files into ~/.claude/
  5. Creates a ccc symlink at /usr/local/bin/ccc or ~/.local/bin/ccc
If you already have CC Commander installed, running the one-liner again updates it to the latest version — the same as running ccc --update.

​
File locations

Do not delete ~/.cc-commander/. The ccc binary is a symlink that points into this directory. Removing it will break the CLI.
PathWhat it contains
~/.cc-commander/CC Commander source — skills, commands, hooks, the CLI engine, and vendor submodules
~/.claude/Installed config — CLAUDE.md, settings.json, skills directory, commands directory, hooks
~/.claude/commander/Runtime state — knowledge base, session history, queue files, daemon state
The installer never modifies existing CLAUDE.md or settings.json files — it preserves your existing config and only creates new files.

​
Verify the installation

After installing, run the built-in self-test: 
ccc --test
This runs a 22-point check covering the binary, config files, skills directory, commands directory, hooks, and vendor dependencies. All items should pass.

​
Update

To pull the latest version of CC Commander: 
ccc --update
This is equivalent to re-running the one-liner installer. It pulls the latest source to ~/.cc-commander/, updates vendor submodules, and reinstalls all components.

​
Uninstall

CC Commander ships an uninstall.sh script at ~/.cc-commander/uninstall.sh. It removes kit components from ~/.claude/ and deletes the ccc symlink, but preserves your existing CLAUDE.md and settings.json so you do not lose personal configuration. 
~/.cc-commander/uninstall.sh
To remove everything including the source directory: 
~/.cc-commander/uninstall.sh
rm -rf ~/.cc-commander

​
Split Mode and tmux

Split Mode is the default launch mode when tmux is available. It opens tabbed tmux sessions — the CC Commander menu runs in tab 0, and each dispatched task opens in a new window where you can watch Claude work with full output visible. Install tmux if you do not already have it: 
brew install tmux
If tmux is not installed, CC Commander falls back to simple mode automatically. You can also force simple mode explicitly: 
ccc --simple
In Split Mode, use Ctrl+A n and Ctrl+A p to move between tabs, and Ctrl+A 0 to return to the CC Commander menu from any task window.