What a loop does
A loop is a written process attached to a thread or category. It names the inputs, phases, checkpoints, and completion conditions. An agent follows it and records how far the work has reached.
For example, a review loop might be: read the request, inspect the change, verify behavior, record findings, and resolve each finding.
Define and run one
Ask the agent to create a loop for a process you repeat. Give it the actual checkpoints and stopping conditions, then review the definition before using it.
Define a review loop for this thread: read the brief, inspect the diff,
run relevant checks, and save findings. Finish only when each finding
has a resolution or a clearly named owner.Once the loop is attached to the thread, ask the agent to run it by name. The bundled thread-loops skill reads the definition and manages its status.
Read the status
The thread can show the last run, the phase reached, whether work is complete or blocked, and what is blocking it. Recorded status is a handoff, not proof that a check passed. Ask for the supporting result when it matters.
Reset a loop when starting a fresh pass. Do not mark an incomplete run complete just to remove it from view.
Loop or automation?
| Use a loop | Use an automation |
|---|---|
| “Follow these steps every time we review a change.” | “Start this review every Friday at 10.” |
| Defines the process and completion gates. | Defines when work runs and how it is executed. |
An automation can ask an agent to run a loop. A loop on its own is not a timer or background service.