Agents · Intermediate
Agentic Reflection Loops
Also known as: Feedback and revision loops
A feedback-and-revision loop gives an agent information about an attempt, then lets it revise or try again. Reflection is not proof that the revision is correct.
What Agentic Reflection Loops is
Here, reflection loop is a descriptive label, not one standardized algorithm. Reflexion is a specific research framework: it turns feedback into text retained in episodic memory for later trials, without updating model weights.
How it works
Separate the attempt, the feedback and the next revision. Anthropic's evaluator–optimizer pattern uses generation and evaluation calls in a loop. Reflexion can use different feedback sources, including external signals and internally generated feedback; these are not equally authoritative.
Why it matters
A loop makes a failure available to the next attempt. Whether that improves the result needs measurement against an external acceptance rule, rather than agreement between model responses.
Common uses
- →Inspect a failed test before proposing a code revision
- →Revise an answer against a supplied source passage
- →Compare a bounded retry process with a one-pass baseline
Strengths
- ✓Keeps explicit feedback available to a subsequent attempt
Watch for
- ✓A 2023 study found intrinsic self-correction without external feedback could fail or reduce reasoning performance in its tested settings
- ✓Repeated confident critiques do not establish factual correctness
- ✓Extra attempts consume resources; set a stopping rule
Proposed missing-field revision exercise
Fictional note: Rina will send the draft. No deadline was agreed. An illustrative faulty extraction says owner Rina, deadline Friday.
- Keep the note and the acceptance rule outside the revision: owner Rina; deadline unknown.
- Provide the concrete feedback that Friday has no support in the note, rather than asking only whether the answer looks right.
- Allow one revision, then compare both versions with the note. Preserve the first attempt in the record.
- Stop if the revision invents another date. Escalate the unresolved field to a person; do not keep retrying until a model says it is correct.
Expected reference: owner Rina; deadline unknown. The example, faulty extraction and acceptance rule are editorial illustrations, not observed model behavior. No trial was run.
Continue exploring
More in this collection
Browse all AI ConceptsSources & References
Shinn et al. — Reflexion (2023 revision): textual feedback and episodic memoryAnthropic — Building effective agents (2024): workflows, agents and evaluator–optimizerHuang et al. — Large Language Models Cannot Self-Correct Reasoning Yet (2024 revision): limits in studied settings