> ## 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 CLI Reference — All Flags and Commands

> Complete reference for every ccc flag, dispatch option, skill management command, daemon control, environment variable, and split mode keyboard shortcut.

CC Commander exposes everything through a single binary — `ccc`. Whether you are launching the interactive TUI, dispatching headless tasks for an AI agent, managing skill tiers, or running a background daemon, every action starts here.

## Main Commands

<ParamField path="ccc" type="command">
  Launch the interactive TUI in default tmux split mode. Arrow keys navigate the menu; Enter selects. Each dispatched task opens in its own tmux window.
</ParamField>

<ParamField path="ccc --stats" type="flag">
  Display your session stats dashboard: total sessions, current streak, level, badges, cost to date, and activity heatmap.
</ParamField>

<ParamField path="ccc --test" type="flag">
  Run the 22-point self-test suite to verify your installation. Checks Node.js version (must be ≥ 18), binary paths, skill directories, hook wiring, and more. Use this first when troubleshooting.
</ParamField>

<ParamField path="ccc --update" type="flag">
  Pull the latest release and reinstall. Preserves your state, sessions, and learned knowledge.
</ParamField>

<ParamField path="ccc --repair" type="flag">
  Reset corrupt state files. Run this when the TUI crashes on startup or `ccc --test` reports failures that `--update` does not fix.
</ParamField>

<ParamField path="ccc --simple" type="flag">
  Open menu-only mode without tmux. Use this if tmux is not installed or you prefer a single-pane experience.
</ParamField>

***

## Dispatch (Headless and Agent API)

These flags let AI agents and scripts drive CC Commander without a human at the keyboard.

<ParamField path="ccc --dispatch" type="flag">
  Dispatch a task headlessly. CCC scores complexity, detects your stack, selects the right model and budget, injects relevant lessons, and runs Claude Code non-interactively.

  ```bash theme={null}
  ccc --dispatch "Add rate limiting to the API"
  ```
</ParamField>

<ParamField path="ccc --dispatch ... --json" type="flag">
  Return machine-readable JSON output containing `session_id`, `cost`, and `result`. Use this when an orchestrator or CI pipeline needs to parse the response.

  ```bash theme={null}
  ccc --dispatch "Build auth with JWT" --json --model opus --budget 5
  ```
</ParamField>

<ParamField path="ccc --list-skills --json" type="flag">
  Emit the full skill catalog as a JSON array. Useful for agents that need to enumerate available skills before dispatching.

  ```bash theme={null}
  ccc --list-skills --json | jq '.[] | select(.name | contains("auth"))'
  ```
</ParamField>

<ParamField path="ccc --status" type="flag">
  Run a health check and output JSON. Reports daemon state, queue depth, knowledge base size, and configuration validity.
</ParamField>

### Dispatch Override Flags

You can override the Intelligence Layer's automatic choices on any `--dispatch` call:

| Flag                 | Description                          | Example                  |
| -------------------- | ------------------------------------ | ------------------------ |
| `--model <name>`     | Force a specific model               | `--model opus`           |
| `--max-turns <n>`    | Limit agentic loop iterations        | `--max-turns 50`         |
| `--budget <dollars>` | Hard cost cap for the session        | `--budget 5`             |
| `--cwd <path>`       | Run the task in a specific directory | `--cwd /path/to/project` |

***

## Skills Management

<ParamField path="ccc --skills" type="flag">
  Open the interactive skill manager. Browse installed skills, install new tiers, remove individual skills, or change the active tier.
</ParamField>

<ParamField path="ccc --skills list" type="subcommand">
  Print all installed skills and their tier assignments to stdout.
</ParamField>

<ParamField path="ccc --skills install <name>" type="subcommand">
  Install a specific skill by name.

  ```bash theme={null}
  ccc --skills install senior-backend
  ```
</ParamField>

<ParamField path="ccc --skills remove <name>" type="subcommand">
  Remove a specific skill.

  ```bash theme={null}
  ccc --skills remove benchmark
  ```
</ParamField>

<Note>
  You can also manage skills from inside any Claude Code session with `/ccc:skills`. This gives you context-aware recommendations ranked for your current project stack.
</Note>

***

## Daemon Mode

The daemon is a KAIROS-inspired background agent. It monitors your project, processes a file-backed task queue, and consolidates knowledge — all without a terminal open.

<ParamField path="ccc --daemon" type="flag">
  Start the background daemon. It runs a tick loop (default: every 5 minutes) that checks the queue, inspects git status, and dispatches work.
</ParamField>

<ParamField path="ccc --queue" type="flag">
  Add a task to the daemon's priority queue.

  ```bash theme={null}
  ccc --queue "fix login bug"
  ```
</ParamField>

<ParamField path="ccc --queue-list" type="flag">
  Show all pending tasks in the queue with their priority and timestamps.
</ParamField>

<ParamField path="ccc --daemon-stop" type="flag">
  Stop a running daemon process.
</ParamField>

### Daemon Customization Flags

Combine these with `--daemon` to tune the tick loop and dream cycle:

| Flag                      | Default     | Description                                    |
| ------------------------- | ----------- | ---------------------------------------------- |
| `--interval <seconds>`    | 300 (5 min) | Tick loop interval                             |
| `--tick-budget <seconds>` | 15          | Time budget per tick action                    |
| `--dream <minutes>`       | 60          | Dream interval — knowledge consolidation cycle |

```bash theme={null}
# 2-minute ticks, 30-second budget, 30-minute dream cycle
ccc --daemon --interval 120 --tick-budget 30 --dream 30
```

***

## Split Mode

Split mode is the default. When you run `ccc`, it launches inside tmux. The CCC menu runs in tab 0 and each dispatched task opens its own tmux window where Claude Code output is fully visible.

<ParamField path="ccc --split" type="flag">
  Force tabbed tmux mode. Use this if you launched `ccc` outside tmux and want to re-enter split mode.
</ParamField>

### Split Mode Keyboard Shortcuts

| Key         | Action                 |
| ----------- | ---------------------- |
| `Ctrl+A n`  | Next tab               |
| `Ctrl+A p`  | Previous tab           |
| `Ctrl+A 0`  | Return to CCC menu tab |
| `Ctrl+A q`  | Quit session           |
| Mouse click | Switch tabs directly   |

### Cancelling Tasks

* **During any build:** Press `Escape` or `q` to kill the Claude process and return to the menu.
* **During YOLO loop:** Run `touch ~/.claude/commander/yolo-stop` to halt between cycles.
* **In split mode:** Switch to the Claude tab and press `Ctrl+C`.

***

## Environment Variables

These variables control visual output and coaching behavior. Set them in your shell profile or prefix them to any `ccc` command.

| Variable                      | Effect                                                                          |
| ----------------------------- | ------------------------------------------------------------------------------- |
| `CC_NO_COLOR=1`               | Disable all ANSI color output. Recommended for CI/CD pipelines.                 |
| `CC_NO_ANIMATION=1`           | Disable spinner and gradient animations.                                        |
| `CC_COACH_DISABLE=1`          | Disable the session coach's periodic nudges entirely.                           |
| `CC_COACH_INTERVAL=<seconds>` | Set how frequently the session coach fires nudges. Default: every 10 responses. |

```bash theme={null}
# Run headless dispatch with no color or animation
CC_NO_COLOR=1 CC_NO_ANIMATION=1 ccc --dispatch "run tests" --json
```

<Tip>
  `CC_NO_COLOR=1` also suppresses all gradient text, themed borders, and status bar colors. This is the recommended setting for log aggregation and CI environments.
</Tip>