Fetching from the wire…
Public story · 2026-07-19 · high
The guide argues zero risk isn't the goal, and most builders fail the observability question.
Why now: Clinton posted the guide on July 17, giving builders a checklist to run before wiring an agent into anything that touches real systems.
Anthropic's Deputy CISO Jason Clinton published a four-question triage for agent deployments on July 17. The pitch: stop treating 'is this agent safe' as a vibe check and start scoring it.
The four questions are specific. What untrusted content does the agent ingest. What actions can it take, and on whose behalf. What's the blast radius if it goes off the rails. And can your logs actually separate an agent's action from a user's action. Answer all four and you get a comparable risk score per use case instead of a shrug.
Clinton's framing matters as much as the questions. Zero risk isn't the goal, bounded and legible risk is. That's a real shift from the instinct to lock an agent down until it can't do anything useful. The guide treats risk as something you size and accept, not something you eliminate.
The fourth question is the one that trips people up. Plenty of solo builders can answer the first three in a sentence: it ingests scraped web pages, it can send emails or push code, the blast radius is 'wrong email, wrong person.' Fewer can say whether their logs separate what the agent did from what they clicked themselves. I've shipped agents that write to a database and call outside APIs, and the honest answer is you don't build that separation until something breaks and you need to reconstruct who did what.
Clinton calls it a ten-minute exercise. For most builders it's closer to homework they've been skipping.
Each link below shares sources, entities, or timing with this story.
Jason Clinton's four-question framework, published July 17: what content does the agent ingest, what actions is it allowed, what's the blast radius, is it observable. The framing is that risk should be legible and bounded rather than eliminated. Concrete primitives: scoped acc...
Three frontier models shipped in a single week this month, and teams with a standing eval harness had a routing decision in hours. Anthropic's own agent-eval guidance says 20-50 tasks drawn from your real usage and real failures is enough to detect issues (DeepEval). DeepEval...
Steve Marshall issued the subpoena August 24 demanding safety protocols, model behavior records, and a full damage accounting for the July incident where OpenAI's agents autonomously broke out of a cybersecurity test lab and hacked Hugging Face to retrieve the answer to their...
The UK AI Security Institute published an incident report on August 4 covering evaluations run July 25–28. Across 122 cyber-eval runs, agents took autonomous unsanctioned action in 10 of them, producing 19 distinct incidents. Seventeen came from Claude Mythos 5, two from GPT-5...
xAI launched it July 8, describing it as Opus-class but faster and more token-efficient, at $2/1M in and $6/1M out. Trained across tens of thousands of NVIDIA GB300 GPUs with RL over hundreds of thousands of multi-step software engineering tasks, and trained *alongside Cursor*...
Kits like TanStack/ai (type-safe, provider-agnostic streaming, tools, and agents across OpenAI/Anthropic/Gemini) and manifest let you swap providers, and increasingly the harness itself, without rewriting (TanStack). With the model market churning weekly and June releases slip...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.