What changed

Try Graft on a fork without signing up

Paste a public fork at /try and watch a real sync: Graft finds the upstream, the release your changes sit on and your changes, moves them onto the newest release on a short-lived machine, runs your tests, and shows each change's outcome and the pull request it would open. A try never pushes and runs no agent. It stops after 10 minutes, and a result is reused for 24 hours. Each visitor gets 3 a day, and results are deleted after 30 days.

Also new: real examples from the benchmark, including one that stayed, and a results page with every benchmark sync, moved or stayed, and the live outcomes of hosted syncs since launch.

Fixed on launch day: a change could be left out of a move

On launch day we found a bug in the sync engine. In specific cases, a change could be left out while the sync still moved the copy. We found it in our own benchmark: on a node-semver release, an agent's rewrite left out two small edits that git had carried cleanly, and the sync moved anyway. We fixed it before any user was affected: no production sync had run into it.

The fix adds a final check before any move: every one of your changes must be present on the moved copy, kept, dropped because the release has it, or rewritten, and a rewrite must keep every part of the change that git carried cleanly. A drop now needs evidence. If a change can't be accounted for, the sync fails closed: your copy stays where it was, and the report names the change.

Graft for agents: a Claude Code plugin, a full MCP server and an HTTP API

An agent can now use Graft directly: register a repository whose changes should survive upstream releases, start a sync, see why one stayed, and fix the conflicts it stopped on. The safety rule doesn't change: Graft moves a copy only when every change lands and the tests pass.

• Claude Code plugin. /plugin marketplace add craigm26/graft-claude-code, then /plugin install graft@graft-claude-code. It connects Graft's MCP server and adds a skill that writes why each change was made into the commit, in the form Graft reads. Agents and Claude Code
• MCP server at https://graftfork.com/mcp with ten tools, including track_change, sync_now and explain_stop, for any MCP client.
• HTTP API under /api/v1, with an OpenAPI description. HTTP API
• Personal API tokens in Settings: scoped to read, sync and resolve, shown once, stored only as a hash, and every use listed in your dashboard.

The personal plan is open

Graft keeps your changed copy of an open-source project on upstream's releases. It carries your changes onto each new release, runs your tests, and opens a pull request only when everything lands and the tests pass. Otherwise your copy stays where it was, and the dashboard says why.

• Free plan, by invite. Up to 10 syncs a month and 5 copies. Your copy moves automatically when nothing conflicts, and your first conflict is resolved free, automatically. Or Graft's agent resolves conflicts on your own Anthropic key. The first 50 people to ask are invited right away.
• Premium, $12 a month. Conflicts are resolved automatically too: Graft's agent sets up your tests and resolves them, and Graft's own runner re-runs your tests before anything moves. $6 of agent work is included each month, with no overage charges, and up to 40 syncs.
• Questions with evidence. When an agent needs your decision, Graft tries each option against your tests and shows the results; one click answers, in the dashboard or the email. On Premium, when exactly one option passes, Graft uses it.
• Billing you control. Cancel or change your card in Stripe's customer portal from the dashboard. Premium runs to the end of the month you paid for.
• Workflow releases. A release that changes .github/workflows is held until you install the optional second app on that repository.
• A new dashboard. Copies with their status at a glance, a timeline of every sync with its report, model and pull request, and agents, billing and settings in tabs.
• Docs, a changelog and a status page with live health from the service.

The safety rule is fail-closed

An agent's rewrite is accepted only when tests exist to check it and none of them already failed on the new release or on your copy before the move. A copy whose own changes already fail some of upstream's tests can still move when the carry adds no new failure, where the test output names failures.

Measured on 12 real forks: 10 of 24 syncs moved by themselves, with 0 wrong moves, as of 2026-10-28. Method and data: graft-evidence.