patch-itUse patch-it

Your code never comes to us.

patch-it runs inside your own CI and writes fixes with your own model key. We built it that way so that the safest answer to "what do you do with our code" is the true one: we don't have it.

Where your code runs.

In your GitHub Actions runner, in a workflow you control. patch-it checks out your repo there, the way your tests do, and does all of its reading there.

  1. patch-it's change feedPublic facts about what providers changed. No customer data.
  2. Your GitHub Actions runnerYour repo is read here. Matching and fixing happen here.
  3. Your model providerThe lines that need fixing are sent here, under your key and your account's terms.
  4. Your repoA pull request or an issue. Never a direct commit to your branches.

What leaves your CI.

Two things go out. One comes to us, one goes to the model provider you chose.

  • To patch-it: a request for changes since the last run, which tells us what you track, and links to the pull requests patch-it opens.
  • To your model provider: the affected lines and the change that affects them, so the model can write the fix. This uses your key. It does not pass through us.
what patch-it receives from your CI

Sent: what you track

Sent: links to the pull requests patch-it opens

Never sent: your source code

Never sent: your diffs

Never sent: your model key

What we store.

Metadata only.

  • Stored: what a repo tracks, and links to the pull requests patch-it opened.
  • Not stored, because we never receive it: source code, diffs, file contents, your model key, your model's prompts and answers.
  • If you join a list: your email address, for that list only. The site itself sets no cookies and loads no trackers.

Your model key.

You bring your own Anthropic key and keep it in GitHub secrets. The Action reads it at run time. It is never printed to logs and never sent to us. The default model is claude-sonnet-5-5, and you can see every call on your own provider bill.

What it can do on GitHub.

  • The Action, today: runs with the token your workflow gives it. It opens pull requests and issues in the repo it runs in. It does not push to your branches; every change waits for your review.
  • The GitHub App, not out yet: every permission it asks for will be listed here, with the reason for each, before it opens. Hear when it does.
  • To stop it: delete the workflow file. Open pull requests stay open until you merge or close them.

The details of each Action input are in the docs.