Fat package, thin wiring.

It installs with your project's own package manager, reads the real manifest out of node_modules rather than trusting a catalog, resolves what the capability composes against as a graph, and writes the bindings into every environment stanza your wrangler file declares.

This is the part most CLIs bolt on later and never finish. Every command supports --json, with structured errors that name the failure and the fix — so a coding agent can install a capability, read what happened, and decide what to do next without parsing prose.

One command cuts a git worktree and its branch, reserves a port block so several features run at once, installs, migrates and seeds a local backend. A second provisions that branch its own ephemeral Cloudflare resources — its D1, its KV, its R2, its own master key.

Every name is derived from the branch, so an already-provisioned resource is recovered by looking it up rather than by anything stored. That is what makes it idempotent, resumable, and safe to run from CI. And the ids land in a build artifact, never in your tracked config, so git add -A cannot commit them and a branch abandoned without teardown strands nothing.

An isolated worktree, a real environment, and structured output on every command is the loop a coding agent already wants: take an issue, get a branch and infrastructure of its own, build, deploy a preview, and tear the whole thing down when the pull request closes.

Teardown deletes by recomputed name regardless of what anyone recorded, so a half-finished run cleans up too. Put the same two commands in CI and every pull request gets a real environment rather than a shared staging everyone queues for.

pithy remove is destructive, so it is interactive only. Passing --json fast-fails with a clear error before anything changes, and its confirmations are typed at a real terminal.

Tearing down an ephemeral environment is a different command, because that is a different intent.

In a terminal it asks one question for the whole cascade. With --with-prerequisites it proceeds. Anything non-interactive exits and names the exact commands to run, in order — and nothing is wired.

Composing something nobody asked for is not a thing to do behind your back, and reporting success on a project that cannot boot is worse.