Agent traces
See where agents retry, choose workarounds, miss context, or repeat a step across coding sessions.
Make your software factory self-improving
Your team shouldn’t have to repeat the same instruction twice.
Iteration is being built to find repeated corrections across coding-agent traces, code reviews, and engineer feedback—and turn them into project-specific guidance.
One example of the loop
Three familiar corrections. One clearer project rule.
This illustrative pattern connects feedback from different kinds of work and turns it into a proposed change the team can review.
Iteration
Patterns/Repository conventions
Illustrative examplePattern/Shared UI conventions
Repeated team pattern
Use the components this repo already has
Similar corrections surfaced across sample sessions and reviews.
Related evidenceAcross sessions · multiple engineers
- 01Engineer correctionEngineer feedback
“Please use the shared form controls.”
- 02Pull request reviewCode review
“This repo already has a button component for this.”
- 03Agent conversationCoding session
“Follow the existing empty-state pattern.”
A repeated convention, surfaced from the work itself.
Look across the work
The same lesson leaves different footprints.
A repeated failure mode rarely lives in one conversation. It can show up in an agent’s choices, a reviewer’s comment, and the corrections engineers keep making.
Review feedback
Connect recurring review comments to the work patterns that led to them.
Engineer corrections
Notice when people keep redirecting agents toward the same project conventions.
The improvement loop
From repeated friction to lasting change.
Turn evidence from real work into focused improvements for the factory that produced it.
- 01
Observe the work
Bring together coding-agent traces and the feedback around them: reviews, retries, and the corrections engineers make.
- 02
Find what repeats
Connect signals across sessions, people, and repositories. A single event is evidence to investigate; recurrence reveals a pattern.
- 03
Improve the factory
Turn the pattern into a focused change in the place it belongs, then watch future work to see whether it helped.
Built around your way of working
The right improvement belongs in the right layer.
Every team has its own code, conventions, and development process. The lesson should become the kind of change that fits your factory.
Context
Instructions · docs · skills
Make project conventions clear when agents need judgment and local knowledge.
Enforcement
Checks · hooks · evaluations
Make stable, explicit rules deterministic when they should hold every time.
Workflow
Tools · setup · handoffs
Improve the surrounding system when repeated friction comes from how work is set up or handed off.
Iteration