Question 1

Does Ito merge code on its own?

Accepted Answer

No, Ito proposes a fix as a pull request and re-runs its test to confirm the bug is resolved. A human always reviews and merges. Self-healing is about doing the legwork on well-scoped bugs, not removing you from the loop.

Question 2

What kinds of bugs can Ito fix?

Accepted Answer

The small, well-understood issues it surfaces during testing. The bugs where the reproduction is clear and the fix is contained. Larger or ambiguous changes are still reported for your team to handle.

Question 3

How does Ito prevent an endless loop?

Accepted Answer

Ito already runs your app, builds the test plan, and captures runtime evidence for every issue. That context of the environment, the failing flow, and the responsible code is exactly what's needed to attempt a reliable fix and verify it worked.

Unlike other codegen tools, Ito knows how to scope the change appropriately to the PR itself and doesn't allow scopecreep to refactor your whole codebase.

Question 4

How do I get access?

Accepted Answer

Self-healing is in private alpha with paying customers. If you want early access, talk to us about how your team ships and we’ll see if you’re a fit.

Don't just find the bug. Fix it.

What engineering leaders say.

"Ito doesn't just report bugs, it fixes them and proves the bug is gone. For the small stuff, that's hours back every week."

"We ship too fast to manually review everything. A self-healing loop that finds the small bugs and proposes the fix is exactly what we need. Especially as we move to auto-merge"

"Because Ito already has the environment and the repro, its fixes actually land. It's the first tool that closes the loop instead of adding another dashboard. We trust Ito to auto-merge."

Questions teams ask about self-healing.

Does Ito merge code on its own?

What kinds of bugs can Ito fix?

How does Ito prevent an endless loop?

How do I get access?

From finding bugs to fixing them.