Your Dependabot PRs are red and nobody’s job is to make them green.

Unbreak fixes them in your own GitHub Actions and charges $49 only when CI passes. Otherwise free.

Install on GitHub

Engineers call these PRs “busy-work”, “spam”, and “a noise machine”, and they rot because keeping them green is nobody’s job. Unbreak only appears when one is red, and only charges when it is green.

How it works

1

A Dependabot or Renovate PR fails CI. Unbreak posts a check run with one button: Unbreak this.

2

You press it. The agent runs inside your own GitHub Actions runner, on your own Anthropic account, runs your tests before and after, and pushes the fix under its own App identity.

3

CI goes green with zero regressions, or you pay nothing. Every fix ships with a before-and-after report.

A real run on our own repository: baseline 18 tests, candidate 18 tests, 0 regressions, $0.20 of API usage.

The three questions every engineer asks

  • Whose name is on the commit?Unbreak commits under its own GitHub App identity, never as you, and never merges. Branch protection still applies.
  • How do I know it didn’t break something?Your test suite runs before and after, the report shows the diff and every test that changed state, and you pay only when CI is green.
  • Where does my code go?Nowhere. Everything runs in your own runner on your own credentials, and the agent’s source is public.

Pricing

$49 per verified fix

No fix, no charge. The API cost of a failed attempt is credited back to you.

$99 per repo, per month

Unlimited fixes, auto-approved at high confidence, with a spend cap you set on your own tokens.

from $4k upgrade sprint

A runtime end-of-life migration plus every failing dependency PR, fixed price, pay on green.

The Node 20 clock

—days until GitHub Actions removes Node 20 from its runners
  • Node.js 20 end-of-life. Source: nodejs/Release.
  • GitHub Actions removes Node 20 from its runners. Actions pinned to node20 stop running. Source: GitHub changelog.
  • Google Cloud Run and Cloud Functions decommission Node.js 20: no new deploys, no updates. Source: Google Cloud runtime support.
  • AWS Lambda blocks updates to Node.js 20 functions (new functions blocked February 1, 2027). Source: AWS Lambda runtimes.

Dates are read from the vendors’ own pages and kept in one file we re-check; if a vendor moves a date, this page moves with it.