Skip to content

Automate long-running work

Start with plan and implement for ordinary project changes. Choose automation when the work must continue autonomously across multiple steps, repeat, follow reproduction gates, or use a saved procedure.

If you do not know which mode fits, use:

/automate

The picker only pre-fills one of the canonical commands below. It does not start work or create a fifth automation mode.

Need Use Example
Continue until a defined outcome is complete Goal /goal start Finish the release checklist
Repeat open-ended work Loop /loop start Watch for new failures and triage them
Reproduce a model or system with evidence at each milestone Repro /repro start Reproduce model X in framework Y
Execute a saved, staged procedure Workflow /workflow run builtin:research Compare the two designs

A goal keeps working toward one durable outcome and stops when it completes, fails, or needs your input.

/goal start <objective>
/goal status
/goal stop
/goal restart [objective]

A loop is intentionally open-ended. It continues only after the current step schedules another one.

/loop start <objective>
/loop status
/loop stop
/loop restart [objective]

Use /loop fresh <objective> when each step should start with a fresh hidden execution context while keeping the same Workspace state.

Repro guides evidence-gated work through setup, scaffold, reproduce, scale, and deliver. It pauses instead of guessing when a baseline, authority decision, or approval is missing.

/repro start <objective>
/repro status
/repro stop
/repro restart [objective]

Use one canonical command to discover, run, and control workflows:

/workflow
/workflow list
/workflow run <builtin:foo|workspace:foo|user:foo> [focus]
/workflow runs [runRef]
/workflow inspect <runRef>
/workflow pause <runRef>
/workflow resume <runRef>
/workflow stop <runRef>
/workflow restart <runRef>
/workflow save <runRef>
/workflow ack <runRef>

The empty /workflow command opens the picker. Existing commands such as /workflows, /workflow-runs, and /workflow-pause remain executable as compatibility aliases but are hidden from the normal command catalog.

Use /help for the short everyday path, /help commands for grouped commands, and /help all only when diagnosing aliases or extension registration.

When automated work needs a decision, answer it in the current Session or open /inbox. Cockpit provides Session activity plus Tasks, Artifacts, and Inbox views.