<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Ben Nevile</title><link>https://bennevile.vercel.app/</link><description>Projects, notes and editorials from Ben Nevile.</description>
<item><title>Little Pan: most review bots never set GitHub&#39;s review decision, so auto-merge does not wait for them</title><link>https://bennevile.vercel.app/notes/little-pan-review-bots-dont-move-review-decision-auto-merge-wont-wait/</link><guid>https://bennevile.vercel.app/notes/little-pan-review-bots-dont-move-review-decision-auto-merge-wont-wait/</guid><pubDate>Mon, 26 Oct 2026 00:00:00 GMT</pubDate><description>Oct 26, a how-to on waiting for CI and review on agent-opened PRs finds that Codex, Claude Code Review, Copilot and Gemini mostly comment or post neutral checks. Auto-merge waits only for required checks, and with none required it merges at once.</description></item>
<item><title>Samuel Medeiros: four ways a green agent loop lies, and a delivery gate that measures instead of asking</title><link>https://bennevile.vercel.app/notes/medeiros-four-ways-a-green-agent-loop-lies-deterministic-delivery-gate/</link><guid>https://bennevile.vercel.app/notes/medeiros-four-ways-a-green-agent-loop-lies-deterministic-delivery-gate/</guid><pubDate>Mon, 26 Oct 2026 00:00:00 GMT</pubDate><description>Oct 26, Samuel Medeiros on a run where the builder said done and the gate scored 55 with a token in the diff. His rule is builder, critic, and reviewer in separate contexts, with a fail-closed security gate, and he lists four ways a passing check can hide a failure.</description></item>
<item><title>Conor Bronsdon: when agents write most of the code, the test suite is the gate and people sign off at the boundary</title><link>https://bennevile.vercel.app/notes/bronsdon-review-the-boundary-test-suite-is-the-gate-humans-at-entry-and-exit/</link><guid>https://bennevile.vercel.app/notes/bronsdon-review-the-boundary-test-suite-is-the-gate-humans-at-entry-and-exit/</guid><pubDate>Sun, 25 Oct 2026 00:00:00 GMT</pubDate><description>Drawing on Graphite&#39;s Greg Foster and AMD&#39;s Anush Elangovan, a Chain of Thought explainer argues that review at agent volume moves from reading every line to rerunnable tests, small stacked diffs, and human sign-off on what enters and leaves the agents&#39; working enclosure.</description></item>
<item><title>John Crowley (Port): a factory that only runs tasks ships the same quality in month six as in week one</title><link>https://bennevile.vercel.app/notes/crowley-port-self-improving-factory-grade-runs-write-back-skills/</link><guid>https://bennevile.vercel.app/notes/crowley-port-self-improving-factory-grade-runs-write-back-skills/</guid><pubDate>Sun, 25 Oct 2026 00:00:00 GMT</pubDate><description>Oct 25, John Crowley at Port on closing the loop in an AI software factory: capture each run, grade a sample on a fixed rubric, find the pattern across a batch, and write a reviewed fix back into the skill the next run reads.</description></item>
<item><title>Ahmad Dogar: agent reports must carry evidence, and the section he reads first is what it did not check</title><link>https://bennevile.vercel.app/notes/dogar-make-agents-prove-their-work-what-it-did-not-check/</link><guid>https://bennevile.vercel.app/notes/dogar-make-agents-prove-their-work-what-it-did-not-check/</guid><pubDate>Sun, 25 Oct 2026 00:00:00 GMT</pubDate><description>Oct 25, Ahmad Dogar on making coding agents prove their work: checks ordered cheapest first, a fixed report format with pasted output, a Stop hook that keeps the agent working while typecheck or lint is red, a bundle budget printed on every run, and screenshots opened by someone who did not write the code.</description></item>
<item><title>Hiroki Kondo: 43 of 80 AI reviews were re-reviews, and a review step written down for agents ran once in about 290 sessions</title><link>https://bennevile.vercel.app/notes/kondo-karasu-re-reviews-quota-written-steps-skipped-become-hooks/</link><guid>https://bennevile.vercel.app/notes/kondo-karasu-re-reviews-quota-written-steps-skipped-become-hooks/</guid><pubDate>Sun, 25 Oct 2026 00:00:00 GMT</pubDate><description>Oct 25, the third weekly log for karasu, built entirely through Claude Code. 50 PRs merged in a week. Re-reviews on every fix burned the CodeRabbit quota, so he moved a local review ahead of the web one. When agents skipped that written step almost every time, he turned it into hooks that refuse to mark a PR ready.</description></item>
<item><title>Ted Factory: a PR agent that merges every ten minutes, and why its owner chose thicker review over putting a human back</title><link>https://bennevile.vercel.app/notes/ted-factory-ten-minute-pr-operator-merges-before-ci-thicker-review-not-humans/</link><guid>https://bennevile.vercel.app/notes/ted-factory-ten-minute-pr-operator-merges-before-ci-thicker-review-not-humans/</guid><pubDate>Sun, 25 Oct 2026 00:00:00 GMT</pubDate><description>Since July, a self-built agent has reviewed, merged, resolved conflicts, and deployed across one company&#39;s repositories on a 10-minute loop. Compared against Claude Code Review and GitHub&#39;s new PR security features, its owner kept the loop and borrowed the designs instead.</description></item>
<item><title>Wakim&#39;s night shift: agent jobs built, reviewed and merged by 1:40 a.m., after a four-day outage nobody noticed</title><link>https://bennevile.vercel.app/notes/wakim-night-shift-log-not-scheduler-silent-four-day-outage/</link><guid>https://bennevile.vercel.app/notes/wakim-night-shift-log-not-scheduler-silent-four-day-outage/</guid><pubDate>Sun, 25 Oct 2026 00:00:00 GMT</pubDate><description>Oct 25, Charbel Wakim on running headless Claude Code jobs overnight with a reviewer agent and a merge step. The scheduler kept failing quietly: usage limits, a sleeping laptop, an exit message that said a finished job had died. What made the night shift trustworthy was a row each job updates after every step.</description></item>
<item><title>Zontak&#39;s one-Mac factory: a ticket became a reviewed PR overnight, and the limit he names is his own attention</title><link>https://bennevile.vercel.app/notes/zontak-one-mac-overnight-factory-first-pr-attention-is-the-cap/</link><guid>https://bennevile.vercel.app/notes/zontak-one-mac-overnight-factory-first-pr-attention-is-the-cap/</guid><pubDate>Sun, 25 Oct 2026 00:00:00 GMT</pubDate><description>Oct 25, Denis Zontak writes up one sleepless night building a small software factory on a Mac and a $200 subscription: plan, plan-check, sandboxed build, 1,100 tests, diff review, then his sign-off. The limits he lists are usage caps, review attention, and what the checks can test.</description></item>
<item><title>Hayden Bleasel: code review was always two jobs, and agents now do the bug-finding one better</title><link>https://bennevile.vercel.app/notes/bleasel-two-kinds-of-code-review-objective-to-agents-direction-to-people/</link><guid>https://bennevile.vercel.app/notes/bleasel-two-kinds-of-code-review-objective-to-agents-direction-to-people/</guid><pubDate>Sat, 24 Oct 2026 00:00:00 GMT</pubDate><description>An OpenAI engineer splits review into objective checks (does it work) and subjective ones (is it the right code), argues agents should own the first, and says consequences, not the split, decide how much to trust them alone.</description></item>
<item><title>Redman: a nightly agent pipeline&#39;s final check passed for months because it was testing the wrong branch</title><link>https://bennevile.vercel.app/notes/redman-nightly-verifier-checked-wrong-branch-hash-bound-verdicts/</link><guid>https://bennevile.vercel.app/notes/redman-nightly-verifier-checked-wrong-branch-hash-bound-verdicts/</guid><pubDate>Fri, 23 Oct 2026 00:00:00 GMT</pubDate><description>A 20-agent overnight pipeline reported green every morning while its last verification job re-tested a tree that had already passed. Binding each verdict to file hashes and re-checking them at merge then refused all 23 open agent PRs.</description></item>
<item><title>Simple Memo: a pull request shipped at 08:06, and the pipeline&#39;s daily report said nothing did</title><link>https://bennevile.vercel.app/notes/simple-memo-shipped-pr-daily-report-said-nothing-stranded-ledger-commits/</link><guid>https://bennevile.vercel.app/notes/simple-memo-shipped-pr-daily-report-said-nothing-stranded-ledger-commits/</guid><pubDate>Fri, 23 Oct 2026 00:00:00 GMT</pubDate><description>A scheduled content pipeline merged only the exact commit it had verified. The run record landed on the same branch after the merge, so it never reached main, and the human-facing report counted a zero day. 17 of 41 after-the-fact records had stranded the same way.</description></item>
<item><title>Alpic set out to build a dark factory and ended up with a light one: twice as fast, human review kept, scheduled routines capped at five PRs</title><link>https://bennevile.vercel.app/notes/alpic-light-factory-routines-capped-review-kept-specs-reviewed/</link><guid>https://bennevile.vercel.app/notes/alpic-light-factory-routines-capped-review-kept-specs-reviewed/</guid><pubDate>Thu, 22 Oct 2026 00:00:00 GMT</pubDate><description>After four months of rebuilding its development cycle around coding agents, Alpic reports shipping about twice as fast with quality and uptime flat. Peer review moved from the PR to the spec, every agent PR has a named owner, and weekly codebase sweeps can&#39;t run again until their last batch of PRs is closed.</description></item>
<item><title>Arize: a software factory that uses its own review-gate verdicts to test reviewer prompts before they ship</title><link>https://bennevile.vercel.app/notes/arize-factory-review-gate-verdicts-tune-reviewer-prompts/</link><guid>https://bennevile.vercel.app/notes/arize-factory-review-gate-verdicts-tune-reviewer-prompts/</guid><pubDate>Thu, 22 Oct 2026 00:00:00 GMT</pubDate><description>Oct 22, Jim Bennett at Arize built a seven-station factory and turned every human gate verdict into a label for its three reviewer agents. A &quot;look harder&quot; prompt fix changed nothing; an optimizer-written prompt took correctness misses from 2–3 PRs per run to zero across 19 PRs, and a retuned router cut unnecessary human reviews from 9 of 17 to 6 with no unsafe auto-merges.</description></item>
<item><title>A software factory is mostly waiting, so Cortex built engrams on a durable workflow engine</title><link>https://bennevile.vercel.app/notes/cortex-engrams-factory-durable-workflow-review-waits-days-side-effects-once/</link><guid>https://bennevile.vercel.app/notes/cortex-engrams-factory-durable-workflow-review-waits-days-side-effects-once/</guid><pubDate>Thu, 22 Oct 2026 00:00:00 GMT</pubDate><description>Oct 22 Unni on how Cortex&#39;s open-source engrams runs: every automation, including its two-agent PR reviewer, is one checkpointed workflow that can park for days on a reviewer, survive deploys mid-run, and perform each side effect once, down to a git clone inside a snapshotted VM.</description></item>
<item><title>GetYourGuide&#39;s Automerge: 5,000 dependency PRs a month with no human clicks, and the agent mistakes that were failures of contract</title><link>https://bennevile.vercel.app/notes/getyourguide-automerge-5000-dependency-prs-a-month-failures-of-contract/</link><guid>https://bennevile.vercel.app/notes/getyourguide-automerge-5000-dependency-prs-a-month-failures-of-contract/</guid><pubDate>Thu, 22 Oct 2026 00:00:00 GMT</pubDate><description>GetYourGuide&#39;s platform team describes a pipeline that approves, merges, and repairs Dependabot pull requests across 250+ repositories. It handles about 97.2% of them automatically, fixes roughly 1,200 CI and security failures a month with AI, and its funniest failures (deleting the failing test, mocking missing secrets) came from asking the agent to make CI pass rather than to find out why it failed.</description></item>
<item><title>Two loops and one gate: an unattended slow loop holds, and autonomy is earned per project by tests proven to fail</title><link>https://bennevile.vercel.app/notes/kappel-two-loops-one-gate-autonomy-earned-by-oracles-that-fail/</link><guid>https://bennevile.vercel.app/notes/kappel-two-loops-one-gate-autonomy-earned-by-oracles-that-fail/</guid><pubDate>Thu, 22 Oct 2026 00:00:00 GMT</pubDate><description>Oct 22 Shai Kappel on six weeks of agents across solo projects: a hub loop has run unattended since mid-September, every job ending in a PR a human approves, while the fast per-project loop is parked. Autonomy is a per-project level set by oracle coverage and escalation rate, and no project is above level zero yet.</description></item>
<item><title>Jared Smith: a revert rate measures noticing, not correctness, so a small team needs checks an agent can&#39;t talk into a pass before an AI reviewer</title><link>https://bennevile.vercel.app/notes/smith-revert-rate-measures-noticing-deterministic-checks-before-ai-reviewer/</link><guid>https://bennevile.vercel.app/notes/smith-revert-rate-measures-noticing-deterministic-checks-before-ai-reviewer/</guid><pubDate>Thu, 22 Oct 2026 00:00:00 GMT</pubDate><description>Responding to the Claude Code team&#39;s review post, Smith argues revert-rate guardrails depend on huge volume, internal users and fast rollback, and that small teams should first add contract tests, post-deploy outcome checks and branch protection. His own merge gate once merged a failing PR because of a shell pipe.</description></item>
<item><title>Snowflake&#39;s overnight pull-request agent reported success for weeks while every tool call failed</title><link>https://bennevile.vercel.app/notes/snowflake-overnight-pr-agent-green-runs-did-nothing-watchdog-outside-agent/</link><guid>https://bennevile.vercel.app/notes/snowflake-overnight-pr-agent-green-runs-did-nothing-watchdog-outside-agent/</guid><pubDate>Thu, 22 Oct 2026 00:00:00 GMT</pubDate><description>A Snowflake engineer scheduled agents to keep pull requests mergeable and answer review comments unattended. The lessons: a separate watchdog, permission checks in plain code, assertions on output rather than run status, and a noisy alert that hid a real break for twelve days.</description></item>
<item><title>CircleCI&#39;s Rob Zuber: the PR becomes a record of evidence, and mutation tests check the agent&#39;s own tests</title><link>https://bennevile.vercel.app/notes/zuber-circleci-pr-becomes-evidence-record-mutation-tests-agent-suites/</link><guid>https://bennevile.vercel.app/notes/zuber-circleci-pr-becomes-evidence-record-mutation-tests-agent-suites/</guid><pubDate>Thu, 22 Oct 2026 00:00:00 GMT</pubDate><description>CircleCI&#39;s CTO argues the pull request carries too many jobs at once. When agents write both the code and the tests, a green suite proves little, so CircleCI is trying mutation testing, earlier reviewer feedback, and risk-routed human attention.</description></item>
<item><title>Stefan Judis: your software factory stops at deploy, so let a failed production check start the next agent run</title><link>https://bennevile.vercel.app/notes/judis-software-factory-stops-at-deploy-failed-check-starts-the-next-loop/</link><guid>https://bennevile.vercel.app/notes/judis-software-factory-stops-at-deploy-failed-check-starts-the-next-loop/</guid><pubDate>Wed, 21 Oct 2026 00:00:00 GMT</pubDate><description>Oct 21, Checkly&#39;s Stefan Judis on the half of the factory loop most teams skip. Tests and review lower the cost of checking work; little lowers the cost of catching a failure after it ships. His setup: a failed synthetic check fires a webhook, an agent follows a runbook skill, and opens a draft PR that proves the fix against the preview.</description></item>
<item><title>Jamie on the Kiln factory: 169 PRs in four days, 15 merged overnight, and the wait moved to the merge queue and the owner&#39;s yes</title><link>https://bennevile.vercel.app/notes/kiln-dynamic-factory-169-prs-four-days-queue-and-human-yes-bottleneck/</link><guid>https://bennevile.vercel.app/notes/kiln-dynamic-factory-169-prs-four-days-queue-and-human-yes-bottleneck/</guid><pubDate>Wed, 21 Oct 2026 00:00:00 GMT</pubDate><description>Oct 21, jamie.codes on a factory that reshaped itself while building Kiln: the reviewer bot retired once CI could do its job, green PRs waiting to merge were 78% of open time, and open-to-merge rose from 14 to 77 minutes as risky PRs queued for a human.</description></item>
<item><title>Melta: a draft PR the reviewer never scored sent its agent back to &quot;fix&quot; nothing, four times in a day</title><link>https://bennevile.vercel.app/notes/melta-draft-pr-unscored-four-false-review-rounds/</link><guid>https://bennevile.vercel.app/notes/melta-draft-pr-unscored-four-false-review-rounds/</guid><pubDate>Wed, 21 Oct 2026 00:00:00 GMT</pubDate><description>An agent pipeline merged at a 5/5 automated review score and looped the agent on anything less. Drafts were never scored, so &quot;no score&quot; fell into the retry branch. The fix is a third state: not there yet means wait.</description></item>
<item><title>PulseEngine: the agents arrived before the factory, and 26 checks were found that could not fail</title><link>https://bennevile.vercel.app/notes/pulseengine-machine-before-factory-gates-that-cannot-fail/</link><guid>https://bennevile.vercel.app/notes/pulseengine-machine-before-factory-gates-that-cannot-fail/</guid><pubDate>Wed, 21 Oct 2026 00:00:00 GMT</pubDate><description>Oct 21, Ralf Anton Beier measures 20 agent-written PulseEngine repositories: changes got smaller and features gave way to fixes, while issue trackers held 26 confirmed checks that passed without checking, surfaces that disagreed about the same fact, and an agent-filed backlog outgrowing human decisions. His fix is manufacturing&#39;s: gates proven to fail, one source per fact, and a cap only on the queue waiting for people.</description></item>
<item><title>DevOps.com: ten times the code, the same reviewers, and dashboards that only count generation</title><link>https://bennevile.vercel.app/notes/saqib-jan-devops-review-bottleneck-ten-times-code-same-reviewers/</link><guid>https://bennevile.vercel.app/notes/saqib-jan-devops-review-bottleneck-ten-times-code-same-reviewers/</guid><pubDate>Wed, 21 Oct 2026 00:00:00 GMT</pubDate><description>Oct 21, Saqib Jan on DevOps.com. Agent adoption moved the constraint to the review queue. Qodo&#39;s Itamar Friedman puts the arithmetic at two 100-line PRs a week becoming two to five 1,000-line PRs a day; the recommended fixes are capping generated PR size, review agents rewarded differently from coding agents, and putting review wait time and depth next to velocity.</description></item>
<item><title>Trail of Bits audited 130+ of its own merged agent patches, found 21 regressions, and built a regression checker that has to prove each one live</title><link>https://bennevile.vercel.app/notes/trail-of-bits-regression-hunt-21-regressions-130-patches-three-arm-proof/</link><guid>https://bennevile.vercel.app/notes/trail-of-bits-regression-hunt-21-regressions-130-patches-three-arm-proof/</guid><pubDate>Wed, 21 Oct 2026 00:00:00 GMT</pubDate><description>Trail of Bits reviewed every Patch the Planet fix its engineers got merged upstream and confirmed 21 regressions in over 130 PRs, from 58 candidates (about 36% precision). Its new regression-hunt plugin replays every suspected regression on a running build in a fresh-context agent and produced 25% fewer false positives than a plain Codex review prompt, at the cost of leaving some real regressions unconfirmed.</description></item>
<item><title>VeeReview: an LLM judge of verification evidence partly measures how a PR is presented</title><link>https://bennevile.vercel.app/notes/veereview-build-verify-pairs-llm-judge-measures-presentation/</link><guid>https://bennevile.vercel.app/notes/veereview-build-verify-pairs-llm-judge-measures-presentation/</guid><pubDate>Wed, 21 Oct 2026 00:00:00 GMT</pubDate><description>Oct 21 Dautović and Wu: V-Model build-verify pairs across 1,454 matched agent and human PRs; agents looked less build-only, but the instrument failed its own calibration bar and kappa was 0.154.</description></item>
<item><title>Mayur Agnani: stop the agent-reviewer loop after two clean passes, not one, and let only new important findings on changed lines block</title><link>https://bennevile.vercel.app/notes/agnani-two-clean-passes-gate-agent-reviewer-loop/</link><guid>https://bennevile.vercel.app/notes/agnani-two-clean-passes-gate-agent-reviewer-loop/</guid><pubDate>Tue, 20 Oct 2026 00:00:00 GMT</pubDate><description>Treating the agent and AI reviewer loop like retry-until-green on a flaky suite, Agnani simulates a 50%-recall reviewer: stopping at one clean pass let 24.4% of bugs escape versus 13.1% for the noisy loop, while a two-clean-pass gate kept 13.1% and halved fix rounds.</description></item>
<item><title>GitLab&#39;s AI-native playbook: agents earn autonomy rung by rung, and a checkpoint nobody exercises is worse than none</title><link>https://bennevile.vercel.app/notes/gitlab-ai-native-playbook-autonomy-ladder-layered-verification/</link><guid>https://bennevile.vercel.app/notes/gitlab-ai-native-playbook-autonomy-ladder-layered-verification/</guid><pubDate>Tue, 20 Oct 2026 00:00:00 GMT</pubDate><description>Oct 20, Chandler Gibbons (GitLab). Launching an AI-Native Engineering Playbook built with IT Revolution, GitLab cites its April survey of 1,528 practitioners: 85% say AI moved the bottleneck from writing code to reviewing and validating it, and 78% say review was not designed for AI-scale code. Its answers are a four-stage autonomy ladder with no skipped rungs and a layered verification system where humans leave the loop only when risk and evidence justify it.</description></item>
<item><title>Gojko Adzic&#39;s lights-on software factory: review moves from reading diffs to certifying evidence</title><link>https://bennevile.vercel.app/notes/gojko-lights-on-software-factory-humans-certify-evidence/</link><guid>https://bennevile.vercel.app/notes/gojko-lights-on-software-factory-humans-certify-evidence/</guid><pubDate>Tue, 20 Oct 2026 00:00:00 GMT</pubDate><description>Oct 20, Gojko Adzic. He open-sourced the Claude Code setup behind Votito as a lights-on factory boilerplate: a container, a Bash command regulator, lint rules that turn repeated review comments into hooks, and a plan-to-workflow orchestrator with gates and a final agent that tries to refute each step. His GOTO Copenhagen slides call human review the new bottleneck and claim 80% fewer tokens and 6 to 10 times faster runs once orchestration moves out of the model.</description></item>
<item><title>Kassebaum: agents review and merge 136 PRs in ten days, with the risk tier computed from the diff and a person on money and auth</title><link>https://bennevile.vercel.app/notes/kassebaum-agents-review-and-merge-136-prs-risk-tier-from-the-diff/</link><guid>https://bennevile.vercel.app/notes/kassebaum-agents-review-and-merge-136-prs-risk-tier-from-the-diff/</guid><pubDate>Tue, 20 Oct 2026 00:00:00 GMT</pubDate><description>Oct 20, William Kassebaum describes a merge gate where a different agent identity reviews each PR, the tier comes from a path-based risk map, verdicts are pinned to the commit, CI stays a separate required check, and the top tier needs two reviewers and a human merge.</description></item>
<item><title>Two AI review prompts found the same bugs; only one showed proof you could act on</title><link>https://bennevile.vercel.app/notes/pereiro-ai-review-skills-18-seeded-bugs-detection-tie-proof-gap/</link><guid>https://bennevile.vercel.app/notes/pereiro-ai-review-skills-18-seeded-bugs-detection-tie-proof-gap/</guid><pubDate>Tue, 20 Oct 2026 00:00:00 GMT</pubDate><description>A medical-software engineer seeded 14 production bugs and four clean traps across 18 pull requests and ran two review skills on the same models. Both caught 15 of 15 bugs. The skill that had to prove serious findings with a test it ran backed 76-78% of real findings, against 14-43% for a checklist prompt, with far fewer nits.</description></item>
<item><title>About 600 PRs, two weeks, one workday of human time: a long-running loop with a second agent that argues back</title><link>https://bennevile.vercel.app/notes/steinberger-openclaw-solid-migration-600-prs-second-agent-challenges/</link><guid>https://bennevile.vercel.app/notes/steinberger-openclaw-solid-migration-600-prs-second-agent-challenges/</guid><pubDate>Tue, 20 Oct 2026 00:00:00 GMT</pubDate><description>Oct 20 Peter Steinberger: a planner-plus-coder loop moved OpenClaw&#39;s web frontend from Lit to Solid 2.0 while he checked in every other day. The piece that kept it on track was a separate agent challenging the work, and the misses were the visual ones.</description></item>
<item><title>T3 Code&#39;s agent merge campaign: hundreds of PRs a day on green CI and AI audits, then a revert of everything the fleet couldn&#39;t run</title><link>https://bennevile.vercel.app/notes/t3-code-agent-merge-campaign-reverts-what-the-fleet-cannot-run/</link><guid>https://bennevile.vercel.app/notes/t3-code-agent-merge-campaign-reverts-what-the-fleet-cannot-run/</guid><pubDate>Tue, 20 Oct 2026 00:00:00 GMT</pubDate><description>Oct 17–20, pingdotgg/t3code. Maintainer Julius Marminge&#39;s agent merged almost 400 web-performance PRs in 30 hours, then took over contributor PRs from the backlog and landed hundreds more. On Oct 20 he reverted 14 desktop fixes in one PR: all had passed CI and code audits, none had run on a real desktop build, and one broke every existing install. He says the open PR and issue counts have barely moved because intake is so large.</description></item>
<item><title>Cutting an agent&#39;s review loop short can double the bugs that escape</title><link>https://bennevile.vercel.app/notes/theaicommit-agent-reviewer-loop-two-clean-passes-cheap-fix-lets-bugs-escape/</link><guid>https://bennevile.vercel.app/notes/theaicommit-agent-reviewer-loop-two-clean-passes-cheap-fix-lets-bugs-escape/</guid><pubDate>Tue, 20 Oct 2026 00:00:00 GMT</pubDate><description>A worked guide to the coding-agent and AI-reviewer loop argues that the long tail of overnight review rounds was doing hidden work. In its simulation, stopping at one clean pass let 24.4% of bugs through, against 13.1% for the noisy loop; requiring two clean passes kept escapes flat with half the fix rounds.</description></item>
<item><title>Violet Labs: five AI reviewers on every PR, audited against 729 merges, and why the Low-risk label still can&#39;t skip the human</title><link>https://bennevile.vercel.app/notes/violet-labs-five-ai-reviewers-729-prs-low-risk-label-not-merge-gate/</link><guid>https://bennevile.vercel.app/notes/violet-labs-five-ai-reviewers-729-prs-low-risk-label-not-merge-gate/</guid><pubDate>Tue, 20 Oct 2026 00:00:00 GMT</pubDate><description>Violet clustered five weeks of bot review into 1,072 distinct issues and replayed its rules prompt on nine models. The cheapest valid finding beat the priciest model, two reviewers got cut, and Low-risk PRs still needed follow-up fixes.</description></item>
<item><title>Twelve days of agents arguing on a visible message board: challenges fixed real decisions, but the human ended up as the hands</title><link>https://bennevile.vercel.app/notes/drag-triglav-agent-message-board-12-days-human-became-the-hands/</link><guid>https://bennevile.vercel.app/notes/drag-triglav-agent-message-board-12-days-human-became-the-hands/</guid><pubDate>Mon, 19 Oct 2026 00:00:00 GMT</pubDate><description>Oct 19, Adam Drag. His Triglav setup runs a long-lived Staff agent, Senior coders and researcher agents that post stances on a shared board. Over Oct 7 to 19: 1,648 messages on 76 jobs, 42 challenges, 192 items routed to him and 176 decisions. 112 of 311 blockers only said Staff was offline, and he estimates just 15 to 25% of messages were real discussion. Two agents agreed on a premise neither checked.</description></item>
<item><title>Everfinity: Claude Code PRs are rejected once in 77, because the person who asked is now the only reviewer</title><link>https://bennevile.vercel.app/notes/everfinity-agent-prs-rejected-1-in-77-author-became-reviewer/</link><guid>https://bennevile.vercel.app/notes/everfinity-agent-prs-rejected-1-in-77-author-became-reviewer/</guid><pubDate>Mon, 19 Oct 2026 00:00:00 GMT</pubDate><description>Oct 19, Everfinity counted two weeks of public GitHub: 14.5% of opened PRs came from agent branches, Claude Code PRs were closed unmerged 1.3% of the time against 6.3% for everything else, and drew about eleven times fewer change requests per merge. AI bots wrote 37% of reviews, but 92.6% of those were comments, not approvals.</description></item>
<item><title>IronBee&#39;s raw-model review benchmark: top models match the best review tools for cents a PR, and more thinking trades precision for recall</title><link>https://bennevile.vercel.app/notes/ironbee-raw-llm-code-review-benchmark-thinking-buys-recall-costs-precision/</link><guid>https://bennevile.vercel.app/notes/ironbee-raw-llm-code-review-benchmark-thinking-buys-recall-costs-precision/</guid><pubDate>Mon, 19 Oct 2026 00:00:00 GMT</pubDate><description>Oct 19, IronBee AI. It ran 21 raw models, up to three effort levels each, three times over Martian&#39;s 50-PR Code Review Bench: 7,980 reviews, all open. Ranked with 21 commercial tools, the top group holds twelve model configurations and three tools. Claude Sonnet 5.5 at low effort scored highest for $0.14 and 9 seconds a PR. At their highest effort level most models found more issues but were less precise. IronBee says it will soon launch its own review tool.</description></item>
<item><title>A six-week build ran overnight in 10 hours, and review and fixing took 40% of the agent time</title><link>https://bennevile.vercel.app/notes/mornati-six-weeks-one-night-agent-team-review-took-40-percent/</link><guid>https://bennevile.vercel.app/notes/mornati-six-weeks-one-night-agent-team-review-took-40-percent/</guid><pubDate>Mon, 19 Oct 2026 00:00:00 GMT</pubDate><description>Oct 19, Marco Mornati: a lead agent, an Opus spec writer, Sonnet developers and an Opus reviewer built Graft&#39;s first phase from 22:17 to 08:35. 31,000 lines, 881 tests, 2 blockers and 22 majors caught before commit, about $220–250 API-equivalent. The bottleneck moved to a 51-item human to-do list.</description></item>
<item><title>PACE-Bench: agents land most of a PRD but only 14% of whole features, and harness releases help less than they seem</title><link>https://bennevile.vercel.app/notes/pace-bench-prd-delivery-14-percent-complete-harness-releases/</link><guid>https://bennevile.vercel.app/notes/pace-bench-prd-delivery-14-percent-complete-harness-releases/</guid><pubDate>Mon, 19 Oct 2026 00:00:00 GMT</pubDate><description>Oct 19 arXiv paper from Zhejiang University and Alibaba. On 43 enterprise feature requests with 750 audited acceptance points, the best agent fully delivered six; unfinished work and missing wiring caused 72% of lost credit. Three in-house harness releases moved the mean from 59.4 to 63.0 on the same model, inside the error bars.</description></item>
<item><title>A weekly gardener turns the fixes your team accepted into lint rules, so Monday&#39;s correction reaches Thursday&#39;s agent</title><link>https://bennevile.vercel.app/notes/reehal-gardener-weekly-loop-turns-accepted-fixes-into-lint-rules/</link><guid>https://bennevile.vercel.app/notes/reehal-gardener-weekly-loop-turns-accepted-fixes-into-lint-rules/</guid><pubDate>Mon, 19 Oct 2026 00:00:00 GMT</pubDate><description>Oct 19, Jag Reehal. Shepherd fixes a PR inside the coding agent, Stamp approves or refuses it in CI, and once a week a gardener reads the GitHub record and proposes one small change to skills or lint rules, as a PR with evidence a person merges. It counts only unreverted fixes, needs three accepted cases before proposing a rule, and its first run over fourteen PRs produced one edit.</description></item>
<item><title>Parallel agent loops gave a one-person repo a merge queue problem, so he built one in GitHub Actions</title><link>https://bennevile.vercel.app/notes/alatas-personal-repo-merge-queue-for-parallel-claude-code-loops/</link><guid>https://bennevile.vercel.app/notes/alatas-personal-repo-merge-queue-for-parallel-claude-code-loops/</guid><pubDate>Sun, 18 Oct 2026 00:00:00 GMT</pubDate><description>Oct 18, Enes Oğuzhan Alataş. Several persistent Claude Code loops working on his tool Spool left approved PRs stuck in rebase-and-rerun round trips. His Actions-based queue rebases each labelled PR onto the current main inside the runner, reruns the existing CI, and turns green only if the head, base, label and auto-merge are unchanged. Any push after approval removes the PR from the queue.</description></item>
<item><title>A bot that watches Sentry and fixes errors overnight: 29 fixes merged in a week, and a person still merges each one</title><link>https://bennevile.vercel.app/notes/altman-sentinel-overnight-sentry-fixes-human-still-merges/</link><guid>https://bennevile.vercel.app/notes/altman-sentinel-overnight-sentry-fixes-human-still-merges/</guid><pubDate>Sun, 18 Oct 2026 00:00:00 GMT</pubDate><description>Oct 18, Patrick Altman. Sentinel turns Sentry alerts into PRs as they arrive and picks two or three backlog issues each evening, so there are fresh fixes to review each morning. In one week 29 errors were fixed, reviewed, merged and released, with a median of 8.7 hours from alert to merge. Other agents review every PR first, then a human merges.</description></item>
<item><title>One week, 88 merged agent PRs: a low open-PR cap turned 24 updates into three triage passes, and about half of 261 AI review findings were real</title><link>https://bennevile.vercel.app/notes/kondo-karasu-open-pr-cap-waves-coderabbit-half-real/</link><guid>https://bennevile.vercel.app/notes/kondo-karasu-open-pr-cap-waves-coderabbit-half-real/</guid><pubDate>Sun, 18 Oct 2026 00:00:00 GMT</pubDate><description>Oct 18, Hiroki Kondo&#39;s weekly log for karasu, a project built entirely through Claude Code. 88 PRs merged from Oct 10 to 17. A cap of 8 open Dependabot PRs split 24 updates into three waves that each needed its own triage, so he raised it to 25. He classified 261 CodeRabbit threads and found about half were real defects; the repeat false positives came from badly scoped rule text.</description></item>
<item><title>Graft puts a verified intent card in front of the diff, because the agent&#39;s own description is the least trustworthy thing on the page</title><link>https://bennevile.vercel.app/notes/mornati-graft-intent-cards-read-before-the-diff/</link><guid>https://bennevile.vercel.app/notes/mornati-graft-intent-cards-read-before-the-diff/</guid><pubDate>Sun, 18 Oct 2026 00:00:00 GMT</pubDate><description>Oct 18, Marco Mornati releases Graft v0.0.1: a GitHub App that records which agent wrote a PR, has one model write an intent card and a second model check it against the diff alone, and applies a base-branch policy file. Shadow mode only; the 90% card-accuracy gate has no pilot data yet.</description></item>
<item><title>Overnight agents should be judged by how ready the team is in the morning, not by how much they produced</title><link>https://bennevile.vercel.app/notes/ryzhykau-overnight-agents-judged-by-morning-readiness-not-output/</link><guid>https://bennevile.vercel.app/notes/ryzhykau-overnight-agents-judged-by-morning-readiness-not-output/</guid><pubDate>Sun, 18 Oct 2026 00:00:00 GMT</pubDate><description>Oct 18, engineering leader Fiodar Ryzhykau sketches a team whose agents keep investigating, testing and preparing work overnight and over weekends. His test is blunt: if people come back to 40 new pull requests, the bottleneck only moved. He asks for a review-capacity budget, independent verification, and no expectation that humans stay on call for the agents.</description></item>
<item><title>Ben Vinegar told his agents to act like a human engineering team, so they clocked out until Monday</title><link>https://bennevile.vercel.app/notes/vinegar-agent-eng-team-clocked-out-until-monday/</link><guid>https://bennevile.vercel.app/notes/vinegar-agent-eng-team-clocked-out-until-monday/</guid><pubDate>Sun, 18 Oct 2026 00:00:00 GMT</pubDate><description>Oct 18, Ben Vinegar&#39;s agent factory experiment: personas on their own Linux VMs, a private IRC server, standups and &quot;review my PR&quot;. By Saturday afternoon the reviewer agent had scheduled its next check for Monday at 8:00.</description></item>
<item><title>Csorba: for background agents the queue entry is the spec, and work is capped per reviewer</title><link>https://bennevile.vercel.app/notes/csorba-background-agents-queue-is-the-spec-cap-per-reviewer/</link><guid>https://bennevile.vercel.app/notes/csorba-background-agents-queue-is-the-spec-cap-per-reviewer/</guid><pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate><description>Oct 17 from Balázs Csorba, a practical guide to cloud coding agents that open PRs while you are away (Codex cloud, Copilot cloud agent, Claude Code cloud, Jules). The queue entry is the specification, every run is time-boxed and resumable, CI is the first reviewer, and work in progress is capped per human reviewer rather than per agent. The cost that counts is cost per merged PR, including review minutes.</description></item>
<item><title>Ka1manov: a loop that keeps its best score reported twice the gain it actually made</title><link>https://bennevile.vercel.app/notes/ka1manov-loop-engineering-noisy-eval-dashboard-reports-2x-gain/</link><guid>https://bennevile.vercel.app/notes/ka1manov-loop-engineering-noisy-eval-dashboard-reports-2x-gain/</guid><pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate><description>Oct 17, a loop-engineering guide with a noisy-evaluator simulation: &quot;beat the best so far&quot; showed +2.37 against a true +1.16, while a gated keep rule told the truth at about six times the eval cost.</description></item>
</channel></rss>
