A factory loop keeps iterating under you-agent-factory until the goal is done.
What It Is
A factory loop is work that keeps iterating under you-agent-factory until the goal is done, or until you take an explicit stop or terminal path. The factory keeps the session and continues agent passes across that loop, so each pass builds on the same run instead of ending when one answer finishes. It is not a one-shot chat reply.
Why It Matters
Long-running goals stay persistent across agent passes, so progress does not reset after every submit. You can tell when a loop format fits — a goal that needs repeated work under a live factory — versus a single submit that is finished when one answer returns.
Simple Example
You start or continue a named run under you-agent-factory, submit work the factory can cycle on, and keep submitting until the goal is done or you stop. Each pass stays on the same live run, so later work picks up where the last pass left off instead of starting a new chat.
Common Confusions
A factory loop is not a one-shot chat reply that ends when a single answer returns. It is also not a write-review loop, where draft or execute work must pass an explicit review gate before the goal can complete. A programming for or while loop only repeats code in a process; it does not keep a factory session living across agent passes. Cursor-driven dynamic workflows are editor-session automation that may call the factory, not the plain factory-loop format itself.