jhfnetboy/devloop

A budget-bounded engineering loop for DSH: expensive models plan and review, cheap ones implement, a program keeps the spend inside limits.

Turns an agent session into a supervised factory tick instead of a single unbounded chat: plan, delegate, review, then a mechanical local git merge only after a review verdict of PASS. The premise, stated in the README, is that a program — not a model — owns state and budget: decisions are cheap, so they are made by expensive models, while implementation goes to whatever cheaper model you route. Safety is layered and legible. There is a hard kill switch and per-day cost caps applied after decideNextAction, so a budget trip can rewrite any intended action into stop; state is file-backed (GOAL.md, revisioned STATE.json, append-only EVENTS.jsonl, a LOCK, PROGRESS.md and a per-worktree CONTRACT.json); and when the loop needs a person it prints the question plus the exact answer retry|accept|stop command that resolves it. A DevLoop tab beside Chat and Trajectory renders every project with its lane, spend and tasks, with Pause/Resume/Start. The README is candid about instrumentation gaps rather than hiding them: in headless mode the daily cost cap only sees planner and reviewer spend, and a crash-recovery path is documented as a resume, not a continued response.

Workflow & Automation ★ 0
View on GitHub ↗

Install

dsh plugin --profile web add @jhfnetboy/dsh-devloop@0.6.11

The pinned npm line, taken as the README writes it — the author pins the tag on purpose rather than tracking a range. The Quick start instead documents the from-source route (pnpm install && pnpm build, then dsh plugin --profile web add /absolute/path/to/DevLoop), because that is how the loop is developed. One operational detail the README is emphatic about: devloop is not on PATH, since neither npm, pnpm nor dsh plugin add links a package's own bin into its own node_modules/.bin, so the CLI is invoked by path — for an installed profile that is node ~/.dsh/profiles/web/node_modules/@jhfnetboy/dsh-devloop/lib/bin/devloop.js status <project>.

Compatibility

Node ^22.19.0 || >=24.0.0 — the README says Node 23 is outside the harness range, so it is not a Node-22-or-later floor. The loop is idle until the target workspace holds a regular file at .devloop/GOAL.md; a bare .devloop/ directory does not arm it. agentBackend defaults to noop, which calls no model and writes nothing but .devloop/, so an install against a real project changes no source until a backend is chosen. Routed defaults need dsh, claude and codex authenticated on PATH; the forge mode that opens one pull request per task needs gh, plus forge.pushUrl and forge.reviewers, which have no defaults.

Details

Alternatives

winyh/dsh-geo · btspoony/dsh-advisor · winyh/dsh-idea

More plugins in Workflow & Automation

Browse more in Workflow & Automation

Guides for Workflow & Automation plugins