@loomfsm/daemon
v0.3.8
Published
Long-lived supervisor over loom's headless driver-loop — drives a project's task server-side, parks on a human gate and wakes on the answer, retries transient failures, recovers in-flight work on restart, and owns the worktree lifecycle.
Downloads
2,187
Maintainers
Readme
@loomfsm/daemon
The long-lived supervisor over loom's headless driver loop — "set it and check back". It drives a project's tasks server-side and surfaces you only at decision points.
What it does
- Parks on a genuine human gate and wakes when you answer (from the dashboard, the Telegram bot, or the CLI).
- Retries transient failures with backoff; a permanent provider error parks the task instead of retry-looping.
- Recovers an interrupted task on restart — idempotent re-delivery, no double work.
- Commits finished work to a
loom/<task>branch: reviewable, never auto-merged, with optional push / squash-merge on accept.
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
