Signals

2026-10-24 / cursor

Origin lets an agent or installed app satisfy code-owner review

Edited by Michael Ruescher

Origin's current early-beta web ruleset offers Off, Classic and Agentic code-owner review. In Agentic, Origin's ownership decision can replace the approval count; an installed app named in ORIGIN_CODEOWNERS can satisfy review for its paths. The captured week-of-2026-10-12 note spans the old cutoff and has no established first-publication time. This is newly established current capability, not a proved post-cutoff launch or a guarantee supplied by installing the separate stable Origin CLI.

What this changes for operators

  • Origin repository owners: choose Classic and human-owned path entries where a person must approve, and remove app_ alternatives for those paths. Classic requires owner approval but does not itself require a human owner. App installation and path ownership determine who can satisfy that gate.
  • Trial Agentic on a scratch repository, recording head, paths, agent decision, human reversals and owner approvals avoided. Published substitution thresholds and a discoverable decision log, corroborated by those tests, would settle which human decisions it can replace.
  • Test an app’s own and another author’s pull requests before treating app review as independent approval. The captured contract does not establish self-review counting. Less owner waiting is possible; teams inherit acceptance-policy and reversal work, with no measured saving.

Signal metadata

Source findings

Featured in

Run: 2026-10-24-weekly-digest-2026-10-13_2026-10-24-frontier-v0

Schema: bitter.frontier_signals.v0 / ID: 2026-10-24-cursor-origin-code-owner-review-can-be-delegated

Research evidence and publication history are open in the repository.