Skip to main content
A fix is a set of code changes the agent makes in response to a failed verification. After a fix, the agent re-verifies, if it passes, the session continues; if it fails again, another fix cycle begins. Fixes are accessed through the Session Timeline, they appear as labeled intervals (Fix 1, Fix 2, …) nested inside activity bars. Click a fix interval to open the Fix Detail panel.

​
Fix lifecycle

  1. A verification fails, the agent reports issues
  2. The agent edits one or more files to address the issues
  3. A new verification cycle runs
  4. If it passes, the session continues to completion; if it fails, the cycle repeats up to maxRetries
All fix cycles are recorded in the timeline so you can trace exactly what the agent changed and whether each change helped.

​
Interpreting fixes

The number of fix cycles in a session is a signal of difficulty:
Fix countInterpretation
0The agent verified successfully on the first attempt
1–2Normal for moderately complex changes
3+The agent struggled, worth reviewing Quality Analysis findings
Fixes clustered on the same files across many sessions suggest those files are error-prone and may benefit from clearer code or better test coverage.

​
Relationship to verification quality

Fix count, fix effectiveness (did the fix actually resolve the issue?), and backfiring fixes (fixes that introduced new problems) are all surfaced as metrics in Quality Analysis.