Two Days with Claude Fable 5: First Impressions of a Mythos-Class Model
I spent two days testing Anthropic's Claude Fable 5 on real work. First impressions of its intent understanding, debugging and security analysis.
On Tuesday, Anthropic released Claude Fable 5 to enterprise customers and paid subscribers. I have spent the two days since putting it to work on real tasks across my own platform, and it is rare that a new model genuinely changes the shape of my working week. This one has.
A quick recap if the launch passed you by. Fable 5 is the public version of Anthropic's new Mythos class of models. Mythos was unveiled back in April and deliberately held back from general release, because in testing it did something no previous model could do at scale. It found previously unknown security vulnerabilities in widely used software, some of which had survived more than twenty years of human auditing, and it built working exploits for them on its own. On one benchmark, the previous generation managed 2 successful exploits where Mythos managed 181. Anthropic responded by routing early access through Project Glasswing, a programme that put the model in the hands of defenders and open source maintainers first.
Fable 5 is that capability made safe for the rest of us. Ask it something high risk in cybersecurity or biology and it blocks the response and falls back to Claude Opus 4.8 for a safe answer. A less restricted version, Claude Mythos 5, exists for Glasswing partners and selected researchers. On the numbers, Fable 5 scores more than 10 per cent higher than Opus 4.8 on some benchmarks, has a one million token context window, and costs roughly double on the API.
What two days of real use actually showed me
Benchmarks are one thing. Here is what I noticed doing real work.
The first thing is that it intuits intent far better than anything I have used before. Briefs that previously needed two or three rounds of clarification get understood first time, including the parts I forgot to mention.
The second is that it fixes most things on the first attempt. Debugging with earlier models was a back-and-forth loop of trying a fix and checking the result. With Fable 5 the first fix usually holds.
One example from yesterday. A partner portal on my platform kept going down, and the obvious move was to restart it and carry on. Fable 5 read the situation differently. It traced the outage to a deliberate decision made during a security review the day before, where a configuration gate meant every routine restart silently left the service switched off. It fixed the actual cause, brought the portal back, and kept the security decision intact, all in one pass. An earlier model would almost certainly have restarted the container and called it done.
The security work deserves its own mention. I ran Fable 5 across parts of my platform that earlier models had already reviewed and waved through. It surfaced real weaknesses they had missed, including a default secret that could have allowed forged logins, a credential sitting in source code where it should never have been, and a public route exposing more of the internal interface than intended. In many ways it is low risk because everything sits on my local network, but you can never be too safe. Every one of them was fixed the same day. Given what the Mythos class was built to find, I should not have been surprised, but watching it catch what previous reviews missed was the moment the launch coverage became real for me.
One practical note on timing. If you are on a paid Claude plan, Fable 5 is included at no extra charge until 22 June, and worth testing properly before it moves onto usage credits after that. Give it a genuinely hard task from your own business rather than a toy prompt. That is where the difference shows.
Takeaways
Fable 5 is the public, safeguarded release of Anthropic's Mythos class, and the capability jump over the previous generation is noticeable in everyday work, especially in understanding intent and getting fixes right first time.
Its security analysis caught real issues that earlier models had reviewed and missed. If your software estate has not had a fresh look recently, this generation of model makes one worthwhile.
The defensive basics are still essential. Patches will arrive faster because of models like this, and capable attackers will eventually hold similar tools. Updates, multi-factor authentication and working backups remain the foundation.
Test it before 22 June while it sits outside usage credits, and test it on real work.
The interesting question for most business owners is no longer whether these models are capable enough. The practical questions are what you would delegate first, and how you would check the work. That is a leadership question, and it is worth thinking through this week rather than next year.