Self-maintaining APIs
When an API provider ships a breaking change, Patchwork rewrites the affected call sites in your repo and opens a pull request — verified to compile. Not a version bump. The actual code.
ingest → extract → locate → migrate → verify → pr
How it works
A breaking change goes in. A reviewable pull request comes out. No agent wandering your codebase — a deterministic pipeline with a model at two tight steps.
Point us at a migration guide, changelog, or diff. We extract the exact breaking changes — renames, moved symbols, new signatures, response-shape shifts — as structured data.
We clone your repo, grep candidates, then confirm each call site with a real AST parse. Strings and comments never match — only code that actually breaks.
We rewrite each site to the new API, bump the dependency, then run your typecheck in a clean checkout. Green means it compiles — then we open the PR.
Why now
Agentic coding tools proved that developers will grant real access to their codebase when the payoff is real. That unlocked the hard part. Breaking-change migration is the obvious, painful, universally-shared job that no one wants to do by hand — and Patchwork is the missing layer: the service that watches for the break and ships the fix as a PR you just review and merge.
Proof
Not a toy — Patchwork migrated RomanHotsiy/commitgpt, a 1.6k★ CLI, from the OpenAI SDK v3 to v4, then confirmed it builds with npm run build in a clean checkout.
Install
Add the GitHub App to a repo and Patchwork watches your dependencies against npm on a schedule — opening a verified PR the moment one breaks. Nothing to trigger. PRs land on a patchwork/* branch, never your default.