crux-cockpitlisted
Install: claude install-skill mehdiforoozandeh/crux
# crux-cockpit — launch the crux GUI, beginning to finish
The **cockpit** is crux's read-only browser GUI: `crux serve` boots a stdlib HTTP server
on `127.0.0.1`, serves the `webui/` frontend, and exposes the vault as `/snapshot.json`
(status-colored tree — pan / zoom / collapse / search / re-orient / focus one question —
plus the review queue, node detail with rendered markdown, and a hypothesis's linked report
and figures; live-refreshing, zero writes). Either panel can go full-screen (`[` / `]`,
`Esc` restores). The engine does the serving; **you (the
agent) do the operating**: find the vault, launch clean, verify, hand over one URL, and
manage the server's lifecycle. The user should never have to touch a terminal **on the
machine you run on** — the one thing you can't do for them is start a local `ssh -L`
tunnel (plain-SSH contexts only; see **Local vs remote**).
The engine rides in the **crux** skill: `ENGINE = <crux skill>/scaffold/crux.py` — the
crux skill is this skill's sibling directory in your skills dir (in a repo clone,
`skills/crux`). If that engine file is missing, the crux skill isn't installed: install
it first (`npx skills add mehdiforoozandeh/crux --all`, or the repo's `./install.sh`)
before continuing.
## Ground rules (load-bearing)
- **Never report an unverified URL.** Before telling the user the cockpit is up, both `/`
and `/snapshot.json` must have answered 200 from *your* curl. A URL you haven't verified
does not leave your mouth.
- **URL only