Skip to main content
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

​
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.
​
flag
Display your session stats dashboard: total sessions, current streak, level, badges, cost to date, and activity heatmap.
​
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.
​
flag
Pull the latest release and reinstall. Preserves your state, sessions, and learned knowledge.
​
flag
Reset corrupt state files. Run this when the TUI crashes on startup or ccc --test reports failures that --update does not fix.
​
flag
Open menu-only mode without tmux. Use this if tmux is not installed or you prefer a single-pane experience.

​
Dispatch (Headless and Agent API)

These flags let AI agents and scripts drive CC Commander without a human at the keyboard.
​
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.
​
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.
​
flag
Emit the full skill catalog as a JSON array. Useful for agents that need to enumerate available skills before dispatching.
​
flag
Run a health check and output JSON. Reports daemon state, queue depth, knowledge base size, and configuration validity.

​
Dispatch Override Flags

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

​
Skills Management

​
flag
Open the interactive skill manager. Browse installed skills, install new tiers, remove individual skills, or change the active tier.
​
subcommand
Print all installed skills and their tier assignments to stdout.
​
subcommand
Install a specific skill by name.
​
subcommand
Remove a specific skill.
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.

​
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.
​
flag
Start the background daemon. It runs a tick loop (default: every 5 minutes) that checks the queue, inspects git status, and dispatches work.
​
flag
Add a task to the daemon’s priority queue.
​
flag
Show all pending tasks in the queue with their priority and timestamps.
​
flag
Stop a running daemon process.

​
Daemon Customization Flags

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

​
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.
​
flag
Force tabbed tmux mode. Use this if you launched ccc outside tmux and want to re-enter split mode.

​
Split Mode Keyboard Shortcuts

​
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.
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.