What Patchlit does, what it refuses to do, and what it costs. If something here is unclear, that is our fault.
No. It pushes a fix to the PR branch and your CI runs on it. A person reads the diff and merges. “Merged as is” is tracked as its own number, so you can see how often a fix needed no edits.
Your own CI went green on the exact commit Patchlit pushed. It does not prove the change is right, only that your tests passed. That is why a person still reviews every fix.
The failing job logs, the version change, and the few files the logs name along with what those import. Not your whole repository.
It has been tested on JavaScript and TypeScript projects. Reproduction tests for bug reports are JavaScript and TypeScript only today.
Patchlit pushes nothing until you allow it, repository by repository. A push from Patchlit starts a CI run that can use your secrets, so the default is no.
No. Tests, lockfiles and CI config are always protected, and you can add your own protected paths. Fixes are checked before the push and audited again on what landed.
Patchlit can only edit files, so it tells you and stops. A clear hand-back is better than a guess.
It stops after your attempt limit, says why on the PR, and leaves the PR as it was for a person.
Yes. Each repository has its own switch, plus limits, protected paths, labels and comment style. You can also ask it to wait for your approval before every fix.
Three fixed pull requests a month are free, with no card. You are counted when Patchlit actually pushes a fix, not for attempts it declines. Full details are on the pricing page.
It is early access. We publish a green rate only once there are enough real runs behind it to mean something.