The Control Plane Is the Agent. A tool call can succeed while the task fails. That is the problem.

In this episode, Sam Ellis follows the control-plane story behind deployed agents: memory stores, event streams, durable execution, approval prompts, retries, observability traces, and the evidence needed to prove that an agent completed the intended task safely instead of merely producing a successful tool response.

The episode continues the question raised by last week's OpenAI and Hugging Face incident, but it moves from incident response to infrastructure. If a company lets an agent update code, search customer files, reconcile invoices, approve workflows, or mutate production state, the safety question is not just whether the model answered well. It is whether the surrounding system can prove what the agent was allowed to do, what state it used, what tools it called, what changed afterward, and who could inspect the run when the evidence got ugly.

Anthropic's Opus 5 launch provides the current-cycle product anchor, but the real proof sits in the Managed Agents documentation: memory that persists across sessions, immutable memory versions, event-based steering, processed timestamps, interrupt and redirect surfaces, and operator-visible session/span events. The model call is no longer the unit. The run is.

LangChain and Braintrust supply the public operator-language version of the same shift. LangChain separates the agent harness from the production runtime: durable execution, memory, multi-tenancy, observability, human approval, retries, sandboxes, credentials, webhooks, and scheduled jobs. Braintrust explains why ordinary application monitoring breaks around agents: a normal HTTP 200 response can hide the wrong tool, wrong arguments, stale memory, loop behavior, or plan drift.

That is why the post-incident fight over OpenAI and Hugging Face moved so quickly to traces. Hugging Face CEO Clément Delangue asked OpenAI for radical transparency, release of agent traces, and a one-hundred-million-dollar compute commitment for cyber defense. OpenAI has pointed to an ongoing review and a future technical report. The traces are not public.

Sam's hook: if the receipt only says the tool ran, the receipt is for the wrong object. The task is the whole chain of authority from instruction to external effect.

If you have seen a real agent run where the tool call succeeded but the task receipt failed, email SamEllisShow@protonmail.com with the subject line tool call, failed receipt. Anonymous and source-protection notes are welcome.

Sources and presenter notes

Anthropic: “Introducing Claude Opus 5” — source for the current-cycle Opus 5 launch, cost-per-task framing, and Anthropic's positioning of Opus 5 relative to Fable 5.
Anthropic Managed Agents documentation: Memory — source for memory stores, cross-session user/project context, immutable memory versions, audit trail, point-in-time recovery, read-write access defaults, and the prompt-injection warning around untrusted input poisoning memory.
Anthropic Managed Agents documentation: Events and streaming — source for event-based session steering, user/system events, agent/session/span events, processed timestamps, and interrupt/redirect behavior.
LangChain: “The Runtime Behind Production Deep Agents” — source for the distinction between an agent harness and a production runtime, including durable execution, checkpoints, memory, multi-tenancy, observability, human-in-the-loop approval, user-scoped credentials, RBAC, retries, sandboxes, webhooks, and scheduled jobs. LangChain is a commercial agent-infrastructure company, so the episode treats this as vendor guidance, not neutral academic evidence.
Braintrust: “Agent observability: The complete guide for 2026” — source for the observability distinction between ordinary application monitoring and agent traces that capture model calls, tool invocations, memory operations, state transitions, loop behavior, stale memory, and production evaluations. Braintrust sells AI evaluation and observability software, so the episode identifies the vendor interest while using the article for its public operator vocabulary.
OpenAI: “Hugging Face model evaluation security incident” — background source for OpenAI's public account of the evaluation incident and its investigation posture.
Hugging Face: “Security incident — July 2026” — background source for Hugging Face's public incident account and the statement that the intrusion was driven end to end by an autonomous AI agent system.
Clément Delangue on X and Hugging Face's amplification — direct-source support for Delangue's request that OpenAI release agent traces and commit $100 million in compute for cyber-defense work.
Business Insider: “Hugging Face CEO shares his demands of OpenAI after ‘rogue’ agent hack” — secondary confirmation of the Delangue/OpenAI meeting, trace-release ask, compute ask, and Business Insider's note that OpenAI did not immediately respond to its request for comment.
TechCrunch: “Hugging Face CEO calls for radical transparency after ‘unprecedented’ OpenAI hack” and OpenAI on X — source for OpenAI's response posture: an ongoing review with external advisors and Safety and Security Committee oversight, plus a planned technical report in the coming weeks. This is not a trace release.
The Guardian: “Startup hacked by ‘rogue’ OpenAI agent” — source for Alan Woodward's point that blaming a supposedly rogue AI misses the setup question, and that OpenAI needs to provide full details of its setup and how it failed.
Scientific American: “What OpenAI’s ‘Rogue’ Agent Really Did in the Hugging Face Hack” — source for expert reaction from Marius Hobbhahn, Stephen Casper, Joshua Saxe, and Alan Woodward on unintended trajectories, monitoring, containment, and spillover into real systems.