Fix with AI

A fix written against your file and opened as a draft pull request on a branch of its own.

1
Open a finding and ask for a fix
The estimate is shown before anything runs and reserved from your credits.
2
The change is written
Against the file in your repository - its imports, its helpers, its conventions - not from a generic snippet.
3
A draft pull request opens
On a new branch, with a body explaining what was wrong and why the change fixes it.
4
You review, run and merge
Nothing is pushed to your default branch and nothing merges itself.
5
The next scan verifies
The rule that raised the finding re-runs and resolves it only if the problem is actually gone.

Read the diff

It is a draft on purpose. A machine-written change to security-relevant code deserves a person’s eyes and your test suite before it reaches main.

When a fix is not offered

The finding is not actionable in code - a rotated key, a DNS change, a vendor setting.
The fix would touch files outside the connected repository.
The finding was dismissed. Dismissed work never spends a credit.
The change would be large enough that a patch would be a rewrite rather than a fix.

Questions

Can it fix several findings at once?

It groups findings that share a root cause into one pull request. Unrelated findings get their own, so each change can be reviewed on its own terms.

What if the patch is wrong?

Close the draft. Nothing was merged, the branch is yours to delete, and the finding stays open. Tell us which rule produced a bad patch - that is the feedback that improves it.

Does it need write access to my repository?

It needs permission to create a branch and open a pull request. It never writes to your default branch.

Something here wrong, missing or out of date? Tell us and we will fix the page.