Skip to main content
CC Commander installs in a single command and launches with ccc. No configuration file, no API keys to manage, and no commands to memorize — the interactive menu guides you through every option. This page walks you through the full flow from install to first build.

​
Before you begin

Make sure you have the following:
  • Node.js 18 or later — check with node --version
  • A terminal — CC Commander runs in any standard terminal emulator
CC Commander installs Claude Code CLI automatically if it is not already present.

​
Install and launch

1

Run the one-liner installer

Paste this command into your terminal and press Enter:
curl -fsSL https://raw.githubusercontent.com/KevinZai/cc-commander/main/install-remote.sh | bash
The installer clones the kit to ~/.cc-commander/, links the ccc binary, and copies skills, commands, hooks, and config files to ~/.claude/. The whole process takes about 30 seconds.
The installer checks for Node.js and Claude Code CLI before proceeding. If Claude Code CLI is missing, it installs it via npm automatically.
2

Verify the install

Run the built-in self-test to confirm everything installed correctly:
ccc --test
This runs a 22-point check across skills, commands, hooks, config files, and the ccc binary. All items should pass. If anything fails, see the troubleshooting guide.
3

Launch CC Commander

Start the interactive menu:
ccc
You will see the main menu with 14 options. Use arrow keys to move between items and Enter to select. Press ? at any time to open the keyboard shortcut help popup.
4

Navigate the main menu

The main menu looks like this in your terminal:
┌─────────────────────────────────────────────────────┐
│  CC Commander  v2.3.1                               │
├─────────────────────────────────────────────────────┤
│                                                     │
│  ❯ Build something new                              │
│    Continue last session                            │
│    Browse skills (450+)                             │
│    Browse domains (11)                              │
│    Project import / stack detection                 │
│    XRay — project health audit                      │
│    Makeover — auto-fix top issues                   │
│    Night mode (YOLO — autonomous build)             │
│    Stats dashboard                                  │
│    Settings                                         │
│    Update CC Commander                              │
│    Quit                                             │
│                                                     │
└─────────────────────────────────────────────────────┘

↑ ↓ to navigate   Enter to select   ? for help   q to quit
Arrow keys move the cursor. Enter selects the highlighted item. Pressing q or Escape cancels and returns to the previous screen.
5

Start your first build

Select “Build something new” from the main menu.CC Commander will ask you three multiple-choice questions about what you want to build — project type, scope, and priority. Based on your answers, it:
  1. Scores the task complexity (0–100)
  2. Detects your project stack from package.json, Dockerfile, and other config files
  3. Recommends the most relevant skills for your task and stack
  4. Auto-selects the right Claude model and token budget
  5. Dispatches Claude Code with all of the above pre-configured
You will see an Intelligence Analysis summary before dispatch:
Intelligence Analysis:
├─ Complexity Score: 60/100 (complex)
├─ Stack detected:   nextjs, react, tailwind
└─ Related lessons:  2 found from past sessions

Auto-configured dispatch:
   Model: Sonnet  |  Turns: 35  |  Budget: $6
   Skills: nextjs-app-router, shadcn-ui, ccc-saas

Dispatching... ████████████████████░░░░ 78%
When the session ends, CC Commander extracts patterns and errors from the work. Every future dispatch is informed by what just happened.

​
The three install paths

CC Commander supports three distinct usage patterns. Choose the one that matches how you use Claude.
You run claude in your terminal. This is the most common path and gives you the full CC Commander experience including Split Mode, the Cockpit Dashboard, and the daemon.
curl -fsSL https://raw.githubusercontent.com/KevinZai/cc-commander/main/install-remote.sh | bash
Then launch:
ccc
What you get: Full CLI with tmux Split Mode, theme switching, the Cockpit Dashboard, daemon mode, and headless agent dispatch.

​
What happens after your first session

When a session ends, CC Commander runs knowledge extraction automatically. It stores patterns, stack context, and success signals in ~/.claude/commander/. The next time you dispatch a task, this store is searched before Claude receives a single token — so the dispatch is pre-informed by everything that worked before.
Run ccc --stats to see your session history, streak, level, and total cost at any time.

​
Next steps

Installation details

Full details on all three install paths, file locations, updates, and uninstall.

Intelligence Layer

How complexity scoring, stack detection, and knowledge compounding work under the hood.

Skills and domains

Browse the 450+ skills and 11 domain routers, and learn how to install only what you need.

CLI reference

Full flag reference for every ccc command — interactive, headless, daemon, and more.