moshcode work
A command-line workflow feature of moshcode that supports running multiple headless AI agents in parallel to execute tasks, using the exit code of a verify command as the completion criterion, and managing failed tasks through git worktree isolation, atomic task claiming and an inbox mechanism.
Timeline (last 90 days)
moshcode version 0.117.0 adds the `moshcode work` feature.
In moshcode work, each task carries a `verify` command, and exit code 0 is the sole definition of task completion.
The workers in moshcode work are headless processes, each running in its own git worktree.
The engine's assessment of its own work is recorded but never accepted as the basis for completion.
A failed attempt returns to the queue with the verification output and goes into the next prompt; after three failures, the task goes into the inbox along with its worktree.
A task that has already passed requires only one verification and consumes no tokens.
Task claiming in moshcode work is an atomic file rename, so multiple runs on the same queue can split the tasks.
Each run of moshcode work is recorded as an OpenFleet swarm.
In the first run, 50 Claude workers processed 19 tasks in parallel, all passed on the first attempt, the inbox remained empty, and local failures dropped from 139 to 0.
The design philosophy of moshcode work is borrowed from the field of mathematical proofs: humans do not review each agent's reasoning process, but instead rely on an objective pass/fail signal (a Lean proof checker or a verify command).
2 more timeline events
All Facts (12)
The inbox mechanism ensures that human attention is focused on genuinely difficult problems: only tasks that fail after exhausting all attempts (three by default) enter the inbox, with their worktrees preserved for inspection.
50%UnverifiedIn moshcode work, each task carries a `verify` command, and exit code 0 is the sole definition of task completion.
50%UnverifiedThe workers in moshcode work are headless processes, each running in its own git worktree.
50%UnverifiedThe engine's assessment of its own work is recorded but never accepted as the basis for completion.
50%UnverifiedA failed attempt returns to the queue with the verification output and goes into the next prompt; after three failures, the task goes into the inbox along with its worktree.
50%UnverifiedA task that has already passed requires only one verification and consumes no tokens.
50%UnverifiedTask claiming in moshcode work is an atomic file rename, so multiple runs on the same queue can split the tasks.
50%UnverifiedEach run of moshcode work is recorded as an OpenFleet swarm.
50%UnverifiedThe design philosophy of moshcode work is borrowed from the field of mathematical proofs: humans do not review each agent's reasoning process, but instead rely on an objective pass/fail signal (a Lean proof checker or a verify command).
50%UnverifiedBy using a git worktree to isolate each worker, moshcode work avoids file conflicts between agents and provides a foundation for horizontal scaling.
50%UnverifiedIn the first run, 50 Claude workers processed 19 tasks in parallel, all passed on the first attempt, the inbox remained empty, and local failures dropped from 139 to 0.
50%Unverifiedmoshcode version 0.117.0 adds the `moshcode work` feature.
50%