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.Documentation Index
Fetch the complete documentation index at: https://docs.commanderplugin.com/llms.txt
Use this file to discover all available pages before exploring further.
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
Choose your install path
- Path A — Claude Code CLI
- Path B — Slash commands only
- Path C — Claude Desktop
Use this path if you run Alternatively, install via npm:Step 2: LaunchArrow 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
claude in your terminal. This is the most common path and gives you the full CC Commander experience.Step 1: Run the one-linerccc --dispatch.What the installer does
The one-liner installer (install-remote.sh) performs the following steps:
- Checks for Node.js and git
- Installs Claude Code CLI if not already present (
npm install -g @anthropic-ai/claude-code) - Clones the CC Commander repository to
~/.cc-commander/(or pulls the latest if already present) - Runs
install.sh --force, which copies skills, commands, hooks, libraries, and config files into~/.claude/ - Creates a
cccsymlink at/usr/local/bin/cccor~/.local/bin/ccc
ccc --update.
File locations
| Path | What 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 |
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:Update
To pull the latest version of CC Commander:~/.cc-commander/, updates vendor submodules, and reinstalls all components.
Uninstall
CC Commander ships anuninstall.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.