EvaluationLoop’s output-quality score.
A loop can succeed (score ≥ 8.0) while burning max iterations, triggering doom-loop recovery, or costing 5× the expected tokens. EvaluationLoop scores output quality; LoopEvaluator scores loop health on top of it — no extra LLM calls.
Quick Start
How It Works
LoopEvaluator derives health from a completed EvaluationLoopResult — it never re-runs the loop, so it makes zero LLM calls and is safe in CI.
| Input | Source | Used For |
|---|---|---|
score_history | EvaluationLoopResult | Convergence, per-iteration deltas |
threshold | Constructor or loop result | Convergence check |
mode | EvaluationLoopResult | Optimize vs review convergence |
guard_events | doom_loop.py / loop_detection_plugin | Doom-loop detection |
Mode-Aware Convergence
Convergence is computed differently inoptimize vs review mode — the health verdict never disagrees with the loop’s own verdict.
optimizemode: convergence = first iteration whose score ≥ threshold.wasted_iterations = num_iterations − iterations_to_success.reviewmode:EvaluationLoopruns every iteration and derives success from the final score, so a transient earlier high score is not treated as convergence.LoopEvaluatordefers toloop_result.success(orscore_history[-1] >= threshold).wasted_iterationsis always0.
Configuration Options
Constructor parameters forLoopEvaluator.
| Option | Type | Default | Description |
|---|---|---|---|
threshold | Optional[float] | None | Score threshold for convergence. Falls back to the threshold on the EvaluationLoopResult. |
max_wasted_iterations | int | 0 | Maximum wasted iterations tolerated before the loop is unhealthy. |
name | Optional[str] | None | Optional name for this evaluation run. |
save_results_path | Optional[str] | None | Optional path to persist the result JSON. |
verbose | bool | False | Print a rich summary table after run(). |
run(loop_result, guard_events=None) takes a completed EvaluationLoopResult (or any object exposing score_history, threshold, total_duration_seconds, mode, success) and an optional list of guard events.
Eval SDK Reference
Full auto-generated Python reference for the
eval moduleLoopHealthResult Fields
run() returns a LoopHealthResult. These are the fields returned by to_dict().
| Field | Type | Description |
|---|---|---|
iterations_to_success | int | 1-based iteration at which threshold was first met; otherwise total iterations. |
wasted_iterations | int | Iterations that ran after threshold was first met (always 0 in review mode). |
doom_loop_fired | bool | Whether any guard event indicated a doom-loop. |
guard_interventions | int | Total number of guard events observed. |
total_duration_s | float | Total wall-clock duration in seconds. |
score_delta_per_iteration | List[float] | Per-iteration delta (len == num_iterations − 1, rounded to 4dp). |
converged | bool | Whether the loop reached its threshold. |
success / passed | bool | converged AND not doom_loop_fired AND wasted_iterations <= max_wasted_iterations. passed aliases success. |
threshold | float | The threshold used (constructor, else loop result, else 8.0). |
reasoning | str | Human-readable explanation of the verdict. |
metadata | Dict[str, Any] | Includes num_iterations. |
to_dict(), to_json(), and print_summary() are all provided.
Recognised Guard-Event Shapes
Guard events are duck-typed — the evaluator detects a doom-loop without coupling to any specific class.| Shape | Trigger |
|---|---|
DoomLoopResult-style | is_loop bool is truthy |
DoomLoopEvent-style | presence of a loop_type (a DoomLoopType enum) |
| Explicit flag | doom_loop / doom_loop_fired boolean is truthy |
| Generic marker | type / event field matches a known string (below) |
type / event string values (case-insensitive): doom_loop, doom-loop, doomloop, repetition, loop_detected, repeated_action, repeated_failure, no_progress, circular_plan, resource_exhaustion, repeated_output.
Common Patterns
CI Gate on Loop Health
Fail the build when a loop wastes iterations or a doom-loop fires.Combine Quality and Health
Score output quality (EvaluationLoop) and loop health (LoopEvaluator) on the same run — they are complementary.
Wire Real Doom-Loop Guards
Plug in structuredDoomLoopEvents (or loop_detection_plugin events) as guard_events.
Best Practices
Use max_wasted_iterations=0 for optimize-mode CI gates
Use max_wasted_iterations=0 for optimize-mode CI gates
0 is the strictest setting — any post-threshold iteration marks the loop unhealthy. Use it for optimize-mode CI gates; use ≥1 for exploratory review-mode runs.Review mode always reports wasted_iterations=0
Review mode always reports wasted_iterations=0
That is intentional, not a bug — review mode runs all iterations by design, so post-threshold iterations are not “waste”.
Guard events are duck-typed
Guard events are duck-typed
A dict or an object works.
type, event, loop_type, is_loop, and explicit doom_loop flags are all recognised — see the accepted string values above.Zero LLM calls, safe offline
Zero LLM calls, safe offline
The evaluator only consumes an existing
EvaluationLoopResult. No external deps, no network — safe in offline CI.Related
Evaluation Suite
Run all four evaluators as one CI gate
Evaluation Loop
The loop this evaluator scores
Loop Detection
The guard whose events feed this evaluator
Loop Guard
Per-turn tool-call guard, complementary safety net
Judge
The underlying judge used by EvaluationLoop
CHL Engineering
The Context / Harness / Loop rubric this evaluator scores against.

