Protocol
Write the completion condition before the agent starts iterating
An agent loop cannot finish reliably if 'done' exists only in the model's mood.
Before you use it
- Use when
- An agent is told to 'keep improving' or 'work until done' without an external definition of done.
Keep this limit in mind
- Open-ended creative work may need a human accept/reject condition rather than an objective test.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Why it matters
Define the observable completion state outside the loop: tests pass, required files exist, all checklist items are satisfied, source coverage reaches a threshold, or another verifiable condition. Keep subjective quality separate from mandatory completion so the agent does not keep polishing indefinitely.
Steps
- Completion is observable outside the model's narrative.
- Mandatory outputs are explicit.
- Quality improvements are separated from hard done criteria.
- A human or grader can verify the state without trusting 'I finished.'
An example
For a repo task, completion means the requested files changed, tests pass and the final diff contains no unrelated edits—not 'the implementation looks good now.'
Check your result
A separate evaluator could decide done/not-done from artifacts and state.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingWrite the completion condition before the agent starts iterating
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaTreat done as an evidence object
More from this collection
Make the agent loop finish, recover and stay inspectable
Detect stagnation separately from completionEvidence and sources
Agent-loop frameworks rely on explicit completion conditions; evaluation guidance likewise recommends unambiguous tasks and success criteria.
Open-ended creative work may need a human accept/reject condition rather than an objective test.
Agent Looping · See source record
All sources (1)
Edition and review
Version 0.1.0
No review details are supplied for this edition.