@loomfsm/cli

The loom binary: host setup, project authorization, the local control plane, and every way to drive a task from a terminal.

Commands

# run
loom up | serve | run "<task>" | daemon start|stop|status | bot telegram

# configure once
loom config get|set · loom secrets set|list · loom models set|list · loom projects add|list|remove

# host setup & lifecycle
loom setup · loom allowlist add|list · loom init · loom status · loom reset · loom history

loom setup registers the MCP server and installs the /task, /done, /proceed commands — idempotent, never clobbers a command you've edited. The project allowlist is default-deny: each directory is authorized explicitly with loom allowlist add.

Part of loom

loom drives multi-step LLM agent work — code review, implementation, any review-gated task — as a replay-deterministic state machine: safety invariants enforced at commit time, human gates where they matter, and a complete, replayable audit trail in a local SQLite file.

Most users should install @loomfsm/pipeline (npm i -g @loomfsm/pipeline), which pulls the whole runtime in one step. Install this package directly only if you are assembling your own runtime.

Website · Quickstart · Why loom · GitHub

License

Apache-2.0