# Self-healing Codebase

## Don't just find the bug. Fix it.

Ito already runs your app, builds the test plan, and captures exactly how each bug reproduces. Self-healing closes the loop: for the small, well-understood issues it surfaces, Ito proposes the fix as a pull request. Bugs get resolved, not just reported.

Alpha Now in private alpha

Talk to us about the alpha →

available to paying customers

## How it works.

Self-healing builds on the testing Ito already does. When Ito finds a bug it understands well enough to fix, it closes the loop for you.

### Step 1: Ito finds a real bug

On every release, Ito runs your app end-to-end and catches behavioral bugs that code review and linters miss, complete with video, reproduction steps, and the exact lines of code responsible.

### Step 2: Ito attempts a fix

Because Ito already has the isolated environment, the test plan, and the runtime evidence, it's uniquely positioned to fix the small, well-scoped issues it surfaces.

### Step 3: You get a fix as a PR to review

Ito opens a pull request with the proposed fix, re-runs the same test to confirm the bug is gone, and hands it to you to review and merge. You stay in control; Ito does the legwork.

## 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.""
>
> CTO

> ""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""
>
> Head of Engineering, Series B

> ""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.""
>
> Founder / CTO

## Questions teams ask about self-healing.

Common questions from engineering leaders evaluating autonomous fixes.

**Q: Does Ito merge code on its own?**

A: 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.

**Q: What kinds of bugs can Ito fix?**

A: 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.

**Q: How does Ito prevent an endless loop?**

A: 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.

**Q: How do I get access?**

A: 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.

## From finding bugs to fixing them.

Self-healing is in private alpha. Tell us how your team ships and we'll see if it's a fit.

Talk to us about the alpha