The coding agents you already run are harnesses around a model. wicked-crew is the harness around them — it drives your own CLIs as governed workers through durable, multi-agent workflows where “done” is re-derived from evidence, never self-graded. Intent in, verified work out. Runs on the agents and plans you already pay for.
You state intent. crew drives a governed workflow to a verified result — deriving “done” from evidence at every gate instead of trusting a claim. No ceremony, no shelfware spec.
Not a new model, not a subscription. crew dispatches your installed coding CLIs — Claude Code, Antigravity, Codex, Copilot, opencode, Pi, a local model, or any binary — as no-shell workers in isolated git worktrees, under your own auth and plan. The roster is data: a manifest plus aworkers.toml you own.
claude -p→ runs in →.worktrees/run-4f2a · no shell · read-scopedSame governed lifecycle wraps every worker. Swap the roster in workers.toml — crew treats them all as stateless subprocesses it owns.
A real transition — build → ship — behind a dual gate that deny-dominates: an approved deterministic check re-verified against the worktree, plus an LLM judge that canfail a gate but can never approve one. It plays itself. Click a switch to take over.
*.json. It’s a workflow.feature, bug, migration — each ships as validated JSON. Add or override one by dropping a file in; the plan is acyclic-validated with loud, per-file errors. No recompile, no plugin. It auto-cycles the defs below — click one to pin it.
A single-writer store and durable cursors give exactly-once effect over at-least-once delivery. Interrupted runs are automatically re-driven on restart. Hover to pause, click a phase to jump, or kill the engine and watch it come back where it left off.
Fan the same question to heterogeneous CLIs — each answers in its own isolated sandbox, blind to the others. crew parses the votes and synthesizes agreement and divergence. That seat diversity is the machinery behind evaluator ≠ creator.
A browser console built into crew. Launch a run from a free-text problem, watch alive event feed and per-unit transcript, drive an embedded governed terminal, and resolve steering gates — approve, steer with an amendment, or reject.
Local-first today — the engine runs in-process, workers are local subprocesses, the bus is local. The execution seam is built for a remote runner; that’s the direction, not a shipped claim.
The simplest way in is npx wicked-installer — the interactive, cross-CLI installer for the whole wicked-* family. Already know you want just this one? Installwicked-crew directly — either way you get crew and the studio console ships inside it, served on your machine.
npx wicked-installer # interactive · picks products · ships the `wicked` CLICross-CLI, cross-product. Choose wicked-crew (and anything else in the family) from one prompt. npm v0.2.0
npm install -g wicked-crew
wicked-crew serve # the studio console, served on your machine