Mushin Docs / Automating with the Autoloop

Automating with the Autoloop

Beyond generating an application in one pass, Workbench can turn your committed design into a stream of implementation work that an automated worker carries out — building the application up issue by issue, with every change gated by review before it lands. This is the autoloop, and you drive it from Workbench. It is designed to keep you firmly in control: nothing merges without passing checks and your approval.

From design to work items

Once you have committed a Mushin design, the Work Items panel turns it into concrete pieces of work. You preview the work items derived from your design, then generate them as tracked issues. Each work item is a well-scoped task — implement this part of the specification — ready to be picked up.

The worker

The Worker panel starts and stops an automated worker for your project. When running, the worker takes work items one at a time and implements them: it writes the change, opens it for review, and runs it through automated checks. The worker runs against a code repository you point it at.

Crucially, the worker is human-gated by default: it prepares changes and runs the checks, but a change does not become part of your project until it has passed and a person has approved it. You decide how much autonomy to give it.

The codegen work queue

The Codegen Work area is where you oversee the loop. It presents the work as a live queue organized around what needs your attention:

  • What needs you — changes waiting for your review or approval
  • What is active — work in progress
  • Everything, for the full picture

From here you review a change, see how it fared against the automated checks, and approve or send it back. The Codegen Runs area shows the history and detail of runs, including the per-stage progress of each — implementation, checks, review, and merge.

Staying in control

The autoloop is powerful, so it is built to be safe by default: it prepares and proposes, checks run automatically, and a person approves before anything lands. You can watch every step, and you decide the pace. Used this way, it lets you turn a reviewed design into a working, growing application while keeping the same review discipline you would apply to any change.

← PreviousAI Model Configuration