Agency & Decisions

Review

Solves: judging what an agent produced, fast and on the record.

Emerging — seen across multiple products; the shape is still settling.

watching →emerging →established →contested →fading 53 sightings since Aug 2026
Ask an assistant about this pattern Ask ChatGPT ↗Ask Claude ↗

Review puts a person over the agent's output before it is accepted. Side-by-side views of before and after make judgment fast; the acceptance is recorded, not implied. Review only works when the reviewer can see enough to judge, which is what Human Handoff has to provide.

When to Use It

  • Agent output needs human evaluation before it counts
  • Diffs and side-by-sides make judgment fast
  • Acceptance should be recorded, not implied

When Not To

  • Output is low-stakes and reversible — sample instead of reviewing everything
  • Review would be rubber-stamping at this volume — fix upstream autonomy instead
  • The reviewer lacks context to judge — improve the handoff first

Three views

The exchange between the human, the agent and the system the agent acts on; who holds each part of it; and the component that implements it.

01 · the interaction
human agent system diff · draft · record makes the change: a diff, a draft, a record presents the change for review reads the change in place; runs it approves, requests changes or rejects merges, sends or discards
02 · who holds what
human interface agent Surface: Where the exchange appears — inline, panel, or notification 01 Surface Trigger: What starts it — the agent proposes, or the human initiates 02 Trigger Decision: The person decides: accept, redirect, or stop 03 Decision Record: What persists afterward — receipt, log, or memory entry 04 Record
human interface agent Surface: Where the exchange appears — inline, panel, or notification 01 Surface Trigger: What starts it — the agent proposes, or the human initiates 02 Trigger Decision: The person decides: accept, redirect, or stop 03 Decision Record: What persists afterward — receipt, log, or memory entry 04 Record
  1. 01 Surface Where the exchange appears — inline, panel, or notification
  2. 02 Trigger What starts it — the agent proposes, or the human initiates
  3. 03 Decision The person decides: accept, redirect, or stop
  4. 04 Record What persists afterward — receipt, log, or memory entry

generic anatomy — parts specialize as sightings are mapped

03 · the component

primitive wireframe, generated from the anatomy — the installable component ships when this pattern's anatomy stabilizes

Field Notes

OCT 14 · Paper · via arXiv ApprovalHuman HandoffObservabilityReview

Hidden ads in search results steered what a shopping AI bought

The human approved the task, then reviewed the result. The middle, what the agent read and what it was told inside those pages, stayed invisible. That gap is what this paper lands on.

OCT 14 · Paper · via arXiv Confidence SignalingHuman HandoffReview

Expertise shapes how far workers trust and delegate to AI

Experts caught errors; novices did not. The difference was review behavior, not trust. A screen that makes scrutiny feel optional skips the most important moment in the interaction.

OCT 14 · Paper · via arXiv Confidence SignalingHuman HandoffReview

Researchers find AI interaction leaves measurable marks on the human

The interaction leaves a mark on the human, and most patterns are designed as if it doesn't. That's the gap. Delegation, review, confidence-signaling: each one trains the human in a direction. Worth knowing which direction before you ship.

OCT 13 · Paper · via Martin Fowler Budget ScopingRelease DecisionEval Run SetupReview

Fowler and Jain measure what scaffolding costs to run an AI coder

The harness is the signal the reviewer depends on. If it's too expensive to run or too noisy to trust, the human's review step loses its foundation before it begins.

OCT 6 · Paper · via arXiv ApprovalObservabilityReview

Attackers fool AI code reviewers by rewriting the attack mid-review

The agent's explanation helps the human judge the work. The same explanation helps an attacker beat the agent. Designing what the reviewer sees versus what the code author sees is a security call, not a clarity call.

OCT 5 · Paper · via arXiv Confidence SignalingObservabilityReview

LLM agents yield to group pressure but keep their original view

The agent said yes, but held a different answer inside. Consensus in a multi-agent setup is not the same as agreement. Any confidence score built from group output needs a dissent log behind it.

SEP 30 · Paper · via arXiv Agent IdentityConfidence SignalingReview

Study finds AI agent groups erode human skepticism over time

A confident tone moved trust more than accuracy did. Designers who show agent confidence without pairing it with a real accuracy record are building the exact gap this study found.

SEP 28 · Paper · via arXiv Confidence SignalingHuman HandoffReview

NYT's Epstein Files agent cut 26,000 documents to 2,500 for reporters

The Times scoped the agent to surface, not conclude. The reporter kept the decision. That boundary was chosen, not accidental. Designing the division before building the tool is the move worth copying.

SEP 28 · Paper · via arXiv Confidence SignalingHuman HandoffReview

366-person study finds AI lifts confidence faster than skill

The agent handed the human a finished result and the human felt expert. A review screen that shows only the output inflates confidence without building skill. That gap is the design problem.

SEP 17 · Clipped · via GitHub Blog Human HandoffObservabilityReview

GitHub used Copilot to rewrite a core part of Copilot itself

Engineers stopped writing code and started directing it. Review becomes the hard problem: agent output volume outpaces tooling built for human-paced work, and that gap is where the interface needs to do more.

SEP 16 · Paper · via arXiv DelegationHuman HandoffReview

20 workers show how reviewing finished agent work opens a reuse loop

The review screen is also the screen where a worker starts the next job. Workers moved from judging a finished run to copying it for a new one. Treating those as two separate screens adds a step the worker does not need.

SEP 16 · Paper · via arXiv DelegationHuman HandoffReview

535 humans and capable AI agents still left gains on the table

The synergy existed in the model; the human did not reach for it. That is a design failure in how work gets passed to the agent, not a capability gap. If a human cannot see the right moment to pass work over, the agent's power goes unused.

SEP 16 · Clipped · via TechCrunch ObservabilityReview

Meinke says the public is trusting the labs to check and then to tell

Voluntary disclosure has the same weakness as a self-reported log: the author decides what counts. The fix is the same too, a reader with their own copy.

SEP 15 · Clipped · via The Pragmatic Engineer DelegationHuman HandoffReview

OpenAI engineers hand Codex their code reviews and move on

The engineer's job moved from writing to judging. Review is now the primary human moment, and most agent products design it as an afterthought. That is the gap to close.

SEP 9 · Paper · via arXiv Agent-to-AgentObservabilityReview

AI audit agents copied the conclusions they were sent to check

An audit agent that relays conclusions is a confidence trap. Any approval pattern that routes through an AI reviewer must show who produced each conclusion. Without that trail, the reviewer hands the person manufactured certainty.

SEP 4 · Paper · via arXiv Agent-to-AgentConfidence SignalingReview

Agents sharing one model voted as one and faked consensus in a study

Any UI showing agent consensus as a trust signal needs to answer: are these agents actually independent? If not, we're designing false confidence into the approval layer.

AUG 31 · Clipped · via Vercel Blog ContextDelegationReview

Vercel puts its brand judgment in a file agents read first

The compliance criteria move upstream into the spec, not downstream into review — this is the clearest sighting I've seen of the context pattern doing real work on design judgment specifically.

AUG 29 · Paper · via arXiv ApprovalRecoveryReview

Margaret Mitchell argues oversight wears down as agents do more alone

This is the clearest framing I've seen for why approval and review patterns decay in production. The design challenge isn't shipping the gate — it's keeping the gate meaningful as agents scale.

Documented sightings (29) — anatomy-mapped observations from vendor materials

Expert participants actively decomposed tasks and scrutinized agent outputs, sacrificing completion rate to maintain evaluative oversight.

arXiv · Oct 14, 2026

Medical training cases show that AI-assisted review of diagnostic decisions can transmit systematic decision biases into later unaided human judgment.

arXiv · Oct 14, 2026

The shift from pull requests to 'antique change requests' visible in the chart suggests Anthropic built new review primitives suited to agent-generated code at scale.

Simon Willison · Oct 14, 2026

The harness enforces checkpoints during code generation that catch failures a smaller model would otherwise propagate through to final output.

Martin Fowler · Oct 13, 2026

SkillRelayGuard provides pre-execution advisory review of artifact integrity while leaving the final execution decision to the agent itself.

arXiv · Oct 13, 2026

Researchers inspected agent-retrieved evidence directly within the shared document artifacts, using co-located traces to evaluate agent output quality.

arXiv · Oct 8, 2026

AI agents performing automated pull-request code review are shown to approve revised code that still contains hidden vulnerabilities after the attacker uses the reviewer's own feedback to appear compliant.

arXiv · Oct 6, 2026

The paper identifies a pattern of post-hoc review as a trust mechanism, where practitioners monitor execution and assess work afterwards rather than approving every step in advance.

arXiv · Oct 6, 2026

The study directly challenges the validity of multi-agent debate as a review mechanism, showing stated consensus can mask persistent internal disagreement rather than genuine convergence.

arXiv · Oct 5, 2026

The experimental setup models a review-like interaction where one agent sees a peer's dissenting answer and explanation and may revise its own judgment accordingly.

arXiv · Oct 5, 2026

The proposed audit framework positions user judgment as a structured check against agent-stated capabilities, enabling systematic review of behavioral claims.

arXiv · Oct 2, 2026

Project-wide structural review and agent dialogue help authors inspect the evolving narrative work at both local and cross-layer levels.

arXiv · Oct 1, 2026

The judgment tasks are structured as single-correct-answer problems where agents must evaluate and potentially revise their answers in light of peer responses, surfacing how identity biases corrupt peer review dynamics.

arXiv · Sep 29, 2026

The Engine returned citation-rich answers explicitly designed so reporters could verify and trust the results before publishing.

arXiv · Sep 28, 2026

The study motivates interfaces that help users evaluate the quality of their joint work with AI rather than simply accept AI-produced answers.

arXiv · Sep 28, 2026

Agents surface concerns and challenge perspectives on the document, functioning as a continuous peer-review layer during composition.

arXiv · Sep 26, 2026

Developers evaluate and approve agent work through the graph interface rather than relying solely on natural-language chat, reducing cognitive load during oversight decisions.

arXiv · Sep 22, 2026

Supervisory control loops include review stages where developers assess agent-produced work before proceeding.

arXiv · Sep 22, 2026

Human coders were used to validate automated coding of agent behavior against declared behavioral rules, establishing a post-hoc review methodology for agentic compliance.

arXiv · Sep 18, 2026

Human engineers reviewed agent-generated Rust migrations at scale across 800,000 lines of production code.

GitHub Blog · Sep 17, 2026

The hierarchical condition gives the Manager agent power to reject worker output and require revision, operationalizing a formal review loop between agents.

arXiv · Sep 16, 2026

Trace2Flow translates completed agent execution traces into interactive graph-based workflows that users can inspect to detect prompt or agent errors post-execution.

arXiv · Sep 16, 2026

The study measures how well humans evaluate and selectively accept or reject model answers, finding deference increases with perceived model competence but confidence calibration degrades post-advice.

arXiv · Sep 16, 2026

The agentic software factory model implies human engineers shift toward reviewing and approving agent-generated code rather than writing it directly.

The Pragmatic Engineer · Sep 15, 2026

A designated accountability layer agent reads upstream agent reports to assign fault, but is shown to perform worse than chance when agents' own conclusions are included in those reports.

arXiv · Sep 9, 2026

Every substantive skill edit is authored or merged through a named human account, establishing human review as the de facto governance gate for agent capability updates.

arXiv · Sep 9, 2026

The paper demonstrates that report-only review of multi-agent outputs cannot distinguish independent corroboration from replication, undermining standard human review workflows that treat agent consensus as evidence of correctness.

arXiv · Sep 4, 2026

Human oversight is deferred to post-hoc inspection of agent-generated findings rather than inline approval of each step.

GitHub · Aug 29, 2026

Frames design critique and critical thinking as the human review layer that agents cannot replace, positioning humans as quality-gatekeepers over generated output.

Maggie Appleton · Aug 28, 2026

What we are learning from the community

Readers who build with Review add what they found: questions, use cases, critiques, other ways to solve it. An editor reads each one before it shows here. Nothing here changes the pattern's status on its own.

This pattern has no contributions yet. The form below sends the first one.

Add to this pattern

A post, a comment, a thread or a repo. Leave it empty to write it here.

Or the name you post under. It shows beside your contribution.

We store a one-way hash of it, not the address.

Up to 2,000 characters. Leave it empty if the link says it all.

The Story So Far

  1. Sep 29, 2026 drift: new → rising (30d sightings 10 → 9)