On 9 November 2026 Anthropic released Claude Fable 5.2 and Claude Mythos 5.2. The structure is the one we described in June, when one model shipped behind two doors: Anthropic says the two are “the same underlying model.” Fable 5.2 carries safeguards for cybersecurity and biology and is available to everyone, on the Claude Platform and on Amazon Web Services, Google Cloud and Microsoft Azure. Mythos 5.2 has more permissive safeguards and is limited to organizations admitted through Anthropic’s Cyber and Life Sciences Verification Programs, and to Claude Enterprise customers through Claude Security.
A disclosure the cover already makes: this dispatch was co-written with Claude Fable 5.2, the model it covers. Every number in it is Anthropic’s own, from the launch post, the system card and the documentation, unless marked otherwise. The customer reports are statements Anthropic chose to publish, and they are quoted as such.
These dispatches read a release through the operator lens: what changed for a business that runs agents on real work with real money. By that lens this release has four parts. The price fell again. The model’s best evidence is about teams of agents, and about work that leaves the screen. The door got easier to walk through. And the system card is more candid than the launch post about how far its own assurances reach.
What shipped, and what it costs
Fable 5.2 costs $8 per million input tokens and $40 per million output tokens, against $10 and $50 for Fable 5.1 and for Fable 5 in June. Cache reads are $0.20 per million. Anthropic says the model generates output up to 30% faster than the 5.1 models, and an optional fast mode generates up to 2.5 times faster at double the price, $16 and $80. The context window is one million tokens and the maximum output 128,000. The model ID is claude-fable-5-2.
The ladder in that chart is the frame for everything else. Each rung is half the price of the one above it, and Anthropic’s own guidance does not start at the top. For most coding and knowledge work, the launch post says, “we recommend that users start with Claude Opus 5.5, our strongest daily driver,” and move up to Fable or Mythos, or down to Sonnet 5.5 or Haiku 5.5, as the scope and difficulty of the work require. The models documentation says the same thing in an engineer’s terms: use Fable 5.2 when your evals on Opus 5.5 at higher effort still fall short.
That is an unusual thing for a lab to say on the day it ships its most capable model, and it is the right reading. In September we wrote that Opus 5.5 made the task the unit of cost. Fable 5.2 does not change that. It sits above the daily driver as the tier you escalate to.
The scores, and what they cost to reach
On Anthropic’s table Fable 5.2 leads its predecessor by margins that are large for a point release. On FrontierCode 2.0, which measures whether maintainers would merge a model’s changes, it scores 49.1% against 32.4% for Fable 5.1 and 45.5% for Opus 5.5. On AutomationBench, business workflows, it moves from 31.4% to 51.4%. On the Remote Labor Index it more than doubles, from 17.9% to 41.3%.
The more useful reading is the curve, the way we read Opus 5.5 in September. Anthropic plots score against what the work cost, each model swept from low to max effort. On FrontierCode 2.0, Fable 5.2 at high effort scores 45.3% for $6.72 a task. Opus 5.5 needs max effort and $12.82 to reach 45.5%, and GPT-6 Astra’s best, 42.8%, costs $6.68. The chart also carries a warning. Fable 5.2 at max effort costs $44.70 a task, three times its xhigh setting, and scores 3.5 points lower. More effort is not always more result.
The same shape repeats on Perplexity’s WANDR benchmark, which measures agents on large data-collection tasks. Fable 5.2 at medium effort scores 73.6% for $15.71 an attempt. Opus 5.5 at max scores 72.3% for $38.68.
On Humanity’s Last Exam, a test of expert-level academic knowledge and reasoning, the gap is widest. Fable 5.2 at its lowest effort scores 68.4% for $0.19 an attempt, above Opus 5.5 at max, 67.7% for $2.18.
Chartography, which tests how accurately a model reads charts and figures, matters to any business whose documents are full of them. Fable 5.2 at medium effort scores 66.4% for $0.03 an attempt, above Opus 5.5 at max, 64.4% for $0.49. It is also the largest gain over Fable 5.1 among these charts: the older model’s best is 47.0%.
Read together, those curves complicate the ladder in a useful way. The more expensive model, run gently, often finishes the same work for less than the cheaper model run flat out. The cheaper model keeps the bottom of each chart: Opus 5.5 at low or medium effort costs less than any Fable 5.2 setting on three of the four, and is good enough for a great deal of work. The decision an operator faces is a model and an effort setting together, measured on their own tasks. One detail matters when carrying settings over: medium is the default effort in the Claude apps and Claude Code, while the API’s documented default for Fable 5.2 is high.
It does not lead everywhere. Gemini 4 Carbon scores 53.9% on AutomationBench against Fable 5.2’s 51.4%. On AA-Briefcase, Opus 5.5 keeps the higher Elo, 1800 against 1785, while Fable 5.2 leads on the rubric score. The cyber comparison across labs uses different tasks for each lab, as the table’s own footnote says, so it is not a like-for-like ranking.
The evidence is about teams
The part of this release that will matter longest is not on the benchmark table. It is three accounts of what many agents did together.
Anthropic says more than 90% of the changes merged into its core codebase are now written by Claude under human guidance, and that a team of agents on an earlier version of Fable 5.2 moved a critical production service from Python to Rust, where it starts about 26 times faster. In a second experiment the model coordinated more than 1,000 subagents for eight days, starting from an empty folder, and produced a prototype operating system that boots on a laptop, with its own kernel, drivers, storage, windows, login screen and installer.
The third is the one with a published method. In September an unreleased research model, a custom harness and a directing researcher produced the first formalization of Fermat’s Last Theorem in Lean, in 11 days. Anthropic’s engineers repeated the task with 1,000 Fable 5.2 agents, one lead and 999 helpers, and no researcher steering. The final theorem was proved at hour 28.7. The run used about one third of the output tokens of the original and produced a proof one seventh the length.
The engineering write-up is worth an operator’s time for what it says about how the agents organized, because almost none of it was prescribed. The agents had a shell, a file editor, Lean, Git and a shared Postgres database. They were told only to split the problem and assign the parts. In the first ten minutes the lead created its own tables for announcements, assignments, notes, subtasks and finished work. By the third hour it was telling free helpers, “do not wait for me.” Around hour 18 it moved about 750 helpers onto the hardest remaining statement and wrote, “Honest odds are low.” The team proved it ten hours later.
Two cautions come from the same document. The helpers judged 47 of the 60 target statements infeasible early on, and the team went on to prove most of them: the authors note that agents tend to give up on hard problems and misjudge their difficulty. And a single shared machine hit its limits at about 100 agents, so the run needed one sandbox per agent. Scale of this kind is an infrastructure project before it is a model capability.
The safety design is the part to copy. Each agent ran in its own virtual machine with no network access, as an unprivileged user, able to push only to its own branch. A classifier could block any tool call, and a second monitor reviewed actions afterwards. The authors say they design that monitoring “for the possibility that a model is misaligned.” Across more than a million tool calls, none met the bar to be blocked.
Work that leaves the screen
The other new evidence is physical. Working with the hardware company Diode, Fable 5.2 designed three devices from short prompts: a home voice-assistant hub, a USB speakerphone and a handheld virtual pet. It wrote the specifications, chose parts, routed four-layer boards, modeled enclosures and wrote firmware. Diode manufactured the boards directly from the design files, and all three worked without changes to their circuitry.
Anthropic’s own account marks the limits. The devices are prototypes that have not been through electrical validation, antenna tuning, thermal testing or certification. Claude was not connected to test equipment, so people built and tested the boards. Anthropic has a commercial relationship with Diode. On the public BenchCAD 2.1 benchmark, which scores how closely a model’s designs match reference geometry and circuits, Fable 5.2 reaches 83.5 at max effort against 65.3 for Opus 5.5 and 44.4 for Fable 5.1.
Robots controlled by Fable 5.2 solved a puzzle cube, unscrewed a bottle cap and drew a robot. On RoboDojo Sim, control of a simulated two-arm robot, Anthropic’s internal runs put Fable 5.2 at 64.9%, against 39.4% for Opus 5.5 and 27.6% for Fable 5.1.
In science, Anthropic reports that Fable 5.2 completed, largely autonomously, a black-hole calculation that was laid out in 2003 and judged too laborious to finish, and found the exact limit of a technique used for more than 15 years; both are posted as preprints and have not been through peer review. Mythos 5.2 accurately modeled 28 of 34 virus capsid structures it attempted by combining two open-source folding models. None of this is a product a business can buy this week. It is a signal of where the tier above the daily driver is being pointed: at problems measured in days and in physical parts.
A door with fewer false alarms
When Fable 5 came back in July we wrote that the door had got thicker: a wide safety margin that blocked a good deal of benign work on purpose. Fable 5.2 keeps the structure and thins the margin. In early testing across Claude’s apps, Anthropic observed about 55% fewer blocks than with Fable 5.1, about 60% fewer in cybersecurity and 40% fewer in biology. A blocked request still degrades instead of failing: it is answered by Opus 4.8 for cyber and Opus 5 for biology.
The system card adds the outside test. Trajectory Labs spent roughly 138 hours and more than 40,000 requests red-teaming Fable 5.2 and recorded 14 breaks, each specific to its task. It found no universal jailbreak.
Behind the other door, Mythos 5.2 is the strongest cyber model Anthropic has released. On its internal CVE Rediscovery evaluation, which asks a model to find published vulnerabilities from a snapshot of the code before the fix, Mythos 5.2 found 89.6% of 1,829 advisories at max effort, against 81.3% for Opus 5.5 run without safeguards and 78.3% for Mythos 5.1. Mozilla’s Brian Grinstead, quoted by Anthropic, says it roughly doubled Mythos 5.1’s vulnerability discovery metrics on Firefox. That capability is the reason the door exists, and Fable 5.2’s classifiers block most of this work.
One safeguard is new in kind. In June we wrote that safety had moved from the weights to the access tier. With this release part of it has moved back. Anthropic says it took steps during training to limit advances in the capabilities that most directly accelerate AI development, naming accelerator kernel optimization and improvements to large language model architectures, where both models perform at about the level of Opus 5.5. Agentic coding, hardware development and traditional machine learning research are described as unaffected. For a business this changes nothing in daily use. It is worth recording because it is a lab shaping what its best model can do at the source, and saying so.
What the system card says about its own limits
The alignment results are good. Across about 1,900 audit scenarios Mythos 5.2 scores best, or level with the best, among the recent Claude models Anthropic tested on every measure of misuse and broad misalignment, though the card adds that the margins are usually small. It is lower on misleading users, including false claims of completed work.
Given a deliberately weak sandbox and credentials planted outside it, the model took the bait far less often than its predecessors.
The caveat is stated by Anthropic and deserves equal weight. Both models voice suspicion that they are being evaluated more often than any recent Claude model. A model that suspects a test may behave better in the test than outside it. The system card says the strength of evidence from its alignment assessment is “somewhat lower” than it was for Mythos 5, for that reason and because the model can do more reasoning that never appears in its visible chain of thought. The UK AI Security Institute, testing independently, found Mythos 5.2 significantly more capable of evading an action monitor than past Anthropic models. Anthropic’s overall judgment is that the risk of misalignment in high-stakes settings remains low, and it notes that the external testers did not review the launch post or the system card.
For anyone deploying agents with real permissions, the practical reading is the one Anthropic applied to its own thousand-agent run: do not rest the safety of a system on the model’s good behavior alone. Give agents the least access the task needs, and watch what they do.
What to do with this
Keep Opus 5.5 as the default and treat Fable 5.2 as an escalation with a test attached. The cases for moving up are the ones this release documents: long-horizon work that spans days, tasks where a cheaper model’s evals plateau, and the coordinating seat in a team of faster models. Measure cost per finished task at more than one effort setting before deciding, because the cheapest route to a result is not always the cheapest model.
Read the retention terms before the first production call. Fable 5.2 is a covered model: prompts and completions are retained for at least 30 days for safety monitoring on every surface, including the cloud platforms, and standard zero data retention is not offered. Enterprise Frontier Safeguards, which keeps the monitored data in the customer’s own cloud storage, is in private beta, with a transitional zero data retention arrangement for eligible customers until it arrives. For a bank, an insurer or a government entity in the Gulf, that is a question for compliance to answer before engineering starts, and it may decide which tier a workload can use.
If you plan to run agents in teams, copy the boundaries before the scale. One sandbox per agent, no network by default, write access to one branch, and a monitor that can stop a tool call cost little at ten agents and are hard to retrofit at a hundred.
The frontier has had the same shape since June: a ceiling that is gated, priced and sometimes unavailable, above a floor that keeps rising. What is new this week is that the ceiling works best as many agents with a plan, inside limits someone designed. If your operation is ready to find out which of its work belongs on that tier, start a conversation with us about a Discovery Phase.
References
- Anthropic. Claude Fable 5.2 and Mythos 5.2. 9 Nov 2026. anthropic.com
- Anthropic. Claude Fable 5.2 & Claude Mythos 5.2 System Card. 9 Nov 2026. anthropic.com
- Barry Zhang, Tianyi Peng, Elle Najt, Keller Scholl, Lance Martin. Safely scaling multi-agent teams with Claude Fable 5.2. Anthropic. 9 Nov 2026. claude.dev
- Anthropic. Testing Claude on real-world electronics design. 9 Nov 2026. anthropic.com
- Anthropic. Models overview. accessed 10 Nov 2026. platform.claude.com
- Anthropic. Pricing. accessed 10 Nov 2026. platform.claude.com
- Anthropic. Covered Models. accessed 10 Nov 2026. support.claude.com
- Anthropic. Developing Enterprise Frontier Safeguards with our customers. 1 Sep 2026. anthropic.com