Skip to content

v0.117.0 — moshcode work: a queue, a verifier, an inbox

Choose a tag to compare

@ralyodio ralyodio released this 17 Oct 09:34
6cf9a9f

moshcode work: a queue, a verifier, an inbox (PRD 0021)

A swarm is a handful of panes a person watches, and that stops at the number of panes a person can read. moshcode work is the shape that scales past it, the way the teams running thousands of agents on math proofs do it: the proof checker judges every attempt, and the human sees only what passed and what is stuck.

Every task carries a verify shell command, and exit 0 is the only definition of done. What the engine says about its own work is recorded and never consulted.

moshcode work from-tests fix-tests                 # one task per failing test file
moshcode work run fix-tests -n 50 --engine claude  # fifty headless workers, a git worktree per attempt
moshcode work status fix-tests                     # pending, working, done, inbox, pass rate, done/h
moshcode work inbox fix-tests                      # only what failed every attempt
moshcode work apply fix-tests                      # land the passing patches, each checked first
moshcode work add docs "document every flag" --verify "npm test"
  • Claims are atomic renames. Tasks are files under ~/.moshcode/work/<queue> (or $MOSHCODE_WORK_DIR), so several work runs on one queue split it between them, on one box or several sharing the directory.
  • Each attempt gets its own worktree at the run's base commit, with node_modules linked in. A pass keeps the diff as a patch; nothing touches your checkout until apply.
  • Retries learn. A failed attempt goes back to the queue with the verify output in its next prompt. After --max-attempts (default 3) the task goes to the inbox with its worktree kept for you to look at.
  • Nothing is paid for twice. A task that already passes is done for the price of one verify, and the task id is a hash of prompt, verify and directory, so the same ask queued twice is one task.
  • Every run is an OpenFleet swarm: a member and a verdict per attempt in the ledger, moshcode fleet tree shows it, and the fleet's fan_out ceiling bounds -n.

Verbs: ls, add, from-tests, run, status, inbox, show, retry, drop, apply, recover. moshcode help work has the details. (#576)