cc

Enter Cockpit CLI operation mode. The Cockpit CLI is a thin local client over the running Cockpit server: each invocation forwards to the server and reuses its CodeIndex / caches / git views. CLI entry point selection (**default = prod**): - Default: **`cockpit`** (prod, port 3457) — use this when no explicit dev signal is given. - Switch to `cockpit-dev` (dev, port 3456) ONLY when the user explicitly signals dev mode, via one of: 1. They write `cockpit-dev ...` directly in the task text. 2. The first word after `/cc` is `dev` (e.g. `/cc dev terminal bmfb check the errors`). Examples below use `cockpit`; only swap in `cockpit-dev` when one of the two dev signals above is present. ## Subcommands | Subcommand | Purpose | |---|---| | (none) / `<path>` | Start server, open project | | `browser open <url>` | Create a browser bubble (auto-registered) and print its id | | `browser <id> <action>` | Drive browser bubbles | | `terminal <id> [<action>]` | Read-only observation of a terminal ring buffer | | `codegraph <subcmd>` | Project code graph (search/callers/callees/impact/file/coedit/context/related/risk/affected) | | `update` | Upgrade to latest npm version | ## Typical usage pattern Terminal / browser bubbles in the UI carry a 4-char short id (e.g. `bmfb` / `mpcw`). After `/cc` users typically follow with `cockpit <subcmd> <id> <what to do>`, e.g.: ``` /cc cockpit terminal bmfb look at the recent error logs ← default prod (cockpit) /cc cockpit browser mpcw...