Skip to main content
Stage ⑤ of the loop · owned by the Optimize skill.
Optimize closes the loop. It takes a remedy that Diagnose proposed, applies it, and re-runs build → evaluate → diagnose to confirm whether the change helped, then repeats until it converges. It conducts the loop itself: it dispatches each stage in turn, feeds one stage’s output to the next, and stops when there’s no better change to make or the moment you decline a remedy.

​
Run it

Tell Helix what to improve and when to stop:
Other ways people ask:
  • Apply the top remedy from diagnosis to the Deep Research agent and re-run the eval loop until the agent holds.
  • Tighten the Refund Processing agent’s escalation rule so large disputes stop getting auto-approved.

​
One approval, where it counts

Optimize is a bounded loop, not an open-ended one. You confirm once at the start, and there’s a single approval at convergence — the point where a change is about to be written. Nothing lands on your code without that approval.

​
What you get

  • An agent that measurably improved against your criteria, or a clear result that it didn’t.
  • A change history you approved, each step re-checked.

Back to the start

See how the five stages connect.