Rerun, requeue, resume or steer

Resume, restart, requeue, take over, stop, and dismiss do different jobs. Use the row that matches the situation.

kusaw serve has to be running to pick up these requests.

Requeue with a noteCopy Anchor Link

Use this when the run is needs_attention, failed, or stopped, and the task needs a hint. The note is required (requeue needs a note.).

Requeue starts the next run of that task from the last checkpoint, on a new branch factory/<task>-<seq>, with your note and the last findings as try-1 feedback. A requeue of a partially delivered run is refused; use resume or restart.

On the Dashboard, Requeue explains: it starts the next run on a new branch from the last checkpoint, and the current run is dismissed automatically.

Resume or restartCopy Anchor Link

Use this when a step failed for a passing reason (a flaky test) and the task itself is fine.

• kusaw resume <run> --failed-only reruns the failed repositories in the worktrees that were kept. The run id, branch, and change-set id stay the same. Dashboard: Resume failed repos.
• kusaw restart <run> reruns every repository from its base commits. Without a terminal it exits 2 and asks for --yes. Dashboard: Restart run. Earlier commits are kept at refs/factory/backup/<run>/<n>.

kusaw resume with no run id still unpauses the queue. That is not a rerun.

Take overCopy Anchor Link

Use this when you want to finish the work by hand. Take over stops a queued, running, or waiting run and keeps its worktrees. There is no take-over CLI command; use the MCP take-over tool. The Dashboard shows a taken-over run and does not offer Take over.

The run ends stopped with reason taken_over. Continue on the kept branch and worktree, then kusaw dismiss <run> (Dashboard Dismiss) to remove the worktree. The branch stays.

Stop or dismissCopy Anchor Link

• kusaw stop <run> — you don't want this run any more while it is still queued, running, or waiting. Worktrees are removed. Dashboard Stop all is the factory-wide form (kusaw stop --all): every running or finalizing run stops and the queue pauses.
• kusaw dismiss <run> — the run is already needs_attention or taken over. Dismiss removes the worktree and keeps the branch. You can still requeue afterwards.

If it goes wrongCopy Anchor Link

• requeue needs a note. — pass --note, or type the note in Requeue before you confirm.
• Run "<run>" can't be requeued from … — requeue only from needs_attention, failed, or stopped. For a flaky failure on a finished run, resume or restart instead.
• A requeue of a partially delivered run is refused — use kusaw resume <run> --failed-only or kusaw restart <run>.
• Resume with a run id needs --failed-only. kusaw resume with no run id only unpauses the queue.
• Restart needs confirmation — pass --yes, or confirm Restart run on the Dashboard.
• Run "<run>" is not in needs_attention or taken over — dismiss is for those runs only. Stop a live run with kusaw stop <run>.
• The run stays queued — the queue is Paused. kusaw resume with no run id, or Resume.