Skip to main content
If you use Claude Desktop rather than the terminal claude CLI, you can run CC Commander entirely within the Claude Desktop UI as a Cowork plugin. There is no separate binary to install, no tmux required, and no shell environment to configure. You install the plugin once and invoke it by talking to Claude naturally.

​
What you get

The Claude Desktop integration ships 7 Cowork skills that cover the most common CC Commander workflows:
The Cowork plugin does not include the tmux split mode, daemon mode, or the full cockpit dashboard. Those features require the CLI path (Path A). If you need them, see the main quickstart.

​
How to install

1

Open Claude Desktop

Launch Claude Desktop and start a new conversation.
2

Add the plugin from the marketplace

Type the following command in the Claude Desktop input:
Claude Desktop will fetch the plugin manifest, confirm the install, and register all 7 Cowork skills.
3

Invoke CC Commander

In the same or any future conversation, say one of the trigger phrases:
or
The cc-commander skill activates and walks you through the guided project manager flow.

​
How it differs from the CLI path

  • Install via /plugin marketplace add
  • No binary, no shell environment needed
  • Works entirely within the Claude Desktop UI
  • 7 Cowork skills covering core workflows
  • Trigger by natural language phrases
  • No tmux, no daemon mode, no cockpit dashboard

​
Using the skills

Once installed, you do not need to type slash commands explicitly. Claude Desktop matches your natural language to the appropriate skill. These phrases all work:
The plugin is spec-driven: before starting any build task, it asks clarifying questions to scope the work. It also auto-detects installed vendor packages (gstack, Compound Engineering, Superpowers) and sequences them for each phase.

​
Knowledge compounding in Claude Desktop

The cc-knowledge skill reads from ~/.claude/commander/knowledge/ — the same knowledge base written by the CLI path. If you use both the CLI and the Cowork plugin, they share the same lesson store. Past sessions from terminal work inform Claude Desktop sessions and vice versa.
The Cowork plugin never modifies your .claude/ directory. It reads from the knowledge base but does not write session data back to it. Full knowledge compounding (lesson extraction after every session) requires the CLI path.