> ## 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.
# CC Commander quickstart: install and run your first build
> Install CC Commander and launch your first session in under two minutes. One command installs everything; no configuration or API keys required.
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
Paste this command into your terminal and press Enter:
```bash theme={null}
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.
Run the built-in self-test to confirm everything installed correctly:
```bash theme={null}
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](/reference/troubleshooting).
Start the interactive menu:
```bash theme={null}
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.
The main menu looks like this in your terminal:
```text theme={null}
┌─────────────────────────────────────────────────────┐
│ 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.
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:
```text theme={null}
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.
```bash theme={null}
curl -fsSL https://raw.githubusercontent.com/KevinZai/cc-commander/main/install-remote.sh | bash
```
Then launch:
```bash theme={null}
ccc
```
**What you get:** Full CLI with tmux Split Mode, theme switching, the Cockpit Dashboard, daemon mode, and headless agent dispatch.
You want skills and commands inside Claude Code without a separate CLI binary.
Run the same installer:
```bash theme={null}
curl -fsSL https://raw.githubusercontent.com/KevinZai/cc-commander/main/install-remote.sh | bash
```
Then, inside any Claude Code session, type:
```text theme={null}
/ccc
```
The full interactive menu appears — same options, same sub-menus, same actions as the CLI.
**What you get:** All 450+ skills and 80+ slash commands, accessible from inside Claude Code without running `ccc` separately.
You use Claude Desktop and want CC Commander as a Cowork plugin.
Inside Claude Desktop, run:
```text theme={null}
/plugin marketplace add KevinZai/cc-commander
```
Then say "start commander" or "what should I work on" to begin.
**What you get:** 7 Cowork skills covering project management, infrastructure, knowledge base access, and night mode.
## 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
Full details on all three install paths, file locations, updates, and uninstall.
How complexity scoring, stack detection, and knowledge compounding work under the hood.
Browse the 450+ skills and 11 domain routers, and learn how to install only what you need.
Full flag reference for every `ccc` command — interactive, headless, daemon, and more.