AI-First
Claude Mythos Preview was announced on April 7, 2026 by Anthropic as part of Project Glasswing. The benchmarks published that day spread across the web within hours: 93.9% on SWE-bench Verified, a near doubling of the multimodal score, zero-days found in Linux and Firefox. Two months later, I have enough hindsight from my daily production use to separate the marketing story from the field reality.
- 📊 Spectacular benchmarks: SWE-bench Verified at 93.9%, +13 points over Opus 4.6.
- ⚠️ Contested hype: only 198 manual reviews, the community is right to have doubts.
- 💡 Targeted production gains: visible on complex code, virtually zero on routine tasks.
- 🎯 Field verdict: Mythos for major refactors, Opus 4.6 for everything else.
What I care about here is what I've actually observed since mid-March on my own projects, and why the community is right to be divided. My verdict is that of a practitioner who bills for code, not a tech journalist relaying press releases.
Claude Mythos SWE-bench benchmarks: what the numbers show
When Anthropic published the Mythos System Card on April 7, 2026, one number captured all the attention: 93.9% on SWE-bench Verified. As a reminder, this benchmark evaluates a model's ability to solve real software engineering tickets, verified by human developers. Opus 4.6, Anthropic's flagship model until then, topped out at 80.8%.
The most significant gap, however, isn't there. On SWE-bench Pro, the hardened variant with no data leakage, Mythos reaches 77.8% versus 53.4% for Opus 4.6. According to the detailed analysis from fabien.cf-evolution.com, this 24-point improvement on a benchmark designed to resist current models is the real technical breakthrough.
Why is SWE-bench Pro the true indicator?
SWE-bench Verified, however popular it may be, suffers from a well-known bias: some problems have solutions that circulate in training data. SWE-bench Pro uses active repositories and eliminates all ground truth leakage. A score of 77.8% means that Mythos correctly solves nearly four out of five problems in an environment it has never seen.
According to Les Numériques, the reasoning performance confirms the trend. GPQA Diamond yields 94.6% (versus 91.3% for Opus 4.6), a narrower gap but still above the typical level of PhD-holding human experts. On Humanity's Last Exam, a benchmark designed to be out of reach, Mythos hits 56.8% without tools versus 40% for Opus 4.6.
| Benchmark | Opus 4.6 | Mythos Preview | GPT-5.4 | Gemini 3.1 Pro | Trend |
|---|---|---|---|---|---|
| SWE-bench Verified | 80.8% | 93.9% | n/a | 80.6% | ↑ +13.1 pts |
| SWE-bench Pro | 53.4% | 77.8% | 57.7% | n/a | ↑ +24.4 pts |
| SWE-bench Multimodal | 27.1% | 59% | n/a | n/a | ↑ +31.9 pts |
| GPQA Diamond | 91.3% | 94.6% | n/a | n/a | ↑ +3.3 pts |
| Humanity's Last Exam | 40% | 56.8% | n/a | n/a | ↑ +16.8 pts |
SOURCE: Anthropic, Project Glasswing · Updated 04/2026
The numbers are clear. Mythos dominates on code, multimodal reasoning, and problems designed to be out of reach. The question is whether these results translate into real gains in an actual workflow.
Two months in production: what I actually observed
I've been using Mythos daily since mid-March on the projects I manage for ai-first.fr and GoLive Software. My usage covers three recurring scenarios: TypeScript/Next.js code refactoring, automated code review, and complex React component generation.
How does Mythos handle a 3,000-line refactor?
On a full refactor of the article orchestrator at ai-first.fr (roughly 3,200 lines of TypeScript), Mythos produced a usable result on the first pass. The model correctly identified circular dependencies, proposed a coherent module breakdown, and maintained compatibility with existing tests. Opus 4.6, given the same prompt, needed two to three iterations to reach the same result.
The clearest difference shows up in long instruction following. When I provide a 4,000-token prompt with overlapping constraints (naming conventions, architectural patterns, API compatibility), Mythos respects all of them. Opus 4.6 regularly drops one or two, forcing manual corrections and re-runs.
The real gain on complex tasks runs around 30 to 40% time saved.
But for routine tasks (generating a simple component, fixing an isolated bug, writing a unit test), I measure no perceptible difference. Opus 4.6 delivers an equally good result, often faster, and at a significantly lower cost per token.
What is the impact on speed and cost?
Mythos is noticeably slower than Opus 4.6 in raw response time. In my tests, the first token arrives on average in 2.3 seconds versus 0.8 seconds for Opus 4.6. For long code generation, throughput remains acceptable. For fast-loop iterative debugging, the latency breaks the work rhythm.
On pricing, I already covered the numbers in my article on Mythos pricing. At $125/MTok input, the cost of a long refactoring session adds up fast. For an SMB owner looking to reduce operating costs, running Mythos on tasks that Opus 4.6 handles perfectly well would be a pure waste of money.
My own GSC data on ai-first.fr for May 2026 shows that "claude mythos release date" is one of the most-clicked queries (6 clicks, position 3.1). Many people are still waiting for a public release date. The reality is that Mythos remains limited to restricted access through Project Glasswing. No official release date to this day.
The community is divided, and that's healthy
The debate around Mythos on Reddit reflects exactly what I observe in production: an impressive model on benchmarks, whose real-world performance divides opinion.
Should you trust the skeptics on r/Anthropic?
A Tom's Hardware article, shared on r/Anthropic, triggered a massive debate (1,223 upvotes, 236 comments). The main criticism: the "thousands" of zero-day vulnerabilities announced by Anthropic rely on 198 manual reviews extrapolated statistically. A user on r/theprimeagen sums up the prevailing skepticism: "if a company publishes something without independent audit, it's marketing."
The skepticism is understandable. Anthropic is preparing an IPO. The timing of the announcement, with its coalition of 12 tech giants (Apple, Microsoft, Google, AWS, CrowdStrike), has all the hallmarks of a carefully orchestrated PR campaign. Mythos still has no public release date, which fuels the frustration.
But the reality is more nuanced than a simple "it's all hype." A user on r/ClaudeAI (239 upvotes) defends the statistical methodology: "when I have 1,000 vulnerabilities and verify 200 of them with a 98% confirmation rate, I can extrapolate. That's exactly what they did."
What do the real Rust vulnerabilities prove?
On r/rust, the Rust Foundation confirmed using Mythos to find real vulnerabilities in the standard library (724 upvotes). A heap overflow in slice::join() and an out-of-bounds write in CString::clone_into() were publicly patched. Other more severe vulnerabilities remain under embargo.
The concrete evidence exists. The marketing wraps it poorly, but that doesn't invalidate it.
Denis Atlan, in his column for Journal du Net, goes further. He describes Mythos as "the first persistent, autonomous, and stealthy agent," referring to the KAIROS and AutoDream systems discovered in the leaked Claude Code source code in late March 2026. I had documented AutoDream in detail when the leak came out. What sets Mythos apart isn't raw power, it's the ability to learn from its failures across sessions.
A user on r/claude raises an angle the skeptics overlook: "if Anthropic can build this, others can too, and they won't be forming coalitions." The real question is no longer whether Mythos is as good as advertised, it's what less transparent players have already built.
Mythos vs Opus 4.6: my decision guide
After 60 days of side-by-side usage, here is my ranking by use case. This isn't a synthetic benchmark; it's the result of what I observe every day on the ai-first and GoLive projects.
When is Mythos actually worth its price?
Mythos wins on three specific fronts. Refactoring large codebases (over 2,000 lines touched), automated security auditing, and following complex instructions exceeding 3,000 tokens of structured context. In these cases, the time saved justifies the $125/MTok premium.
Opus 4.6 remains better for everything else: standard code generation, iterative debugging, test writing, quick conversational exchanges. The lower latency (0.8s vs 2.3s to first token) and a cost three to five times cheaper make it the rational choice for 80% of my daily sessions.
According to a Gartner report on enterprise generative AI adoption, only 15% of use cases in 2026 require the reasoning level of frontier models. My field experience confirms that ratio.
"Mythos is a specialist tool, not a universal replacement. Running the most powerful model on all your tasks is like taking a bullet train to go 2 miles."
Vincent, May 2026
For the SMBs I work with, the recommendation is straightforward. Keep Opus 4.6, or an equivalent model connected to your actual business tools, for daily use. Reserve Mythos for high-value one-off missions: critical code audits, complex technical migrations, vulnerability analysis on legacy code.
I've seen too many business leaders rush to the latest model "because it scores higher on benchmarks." The right question isn't "which model is the most powerful?" but "where is my team losing time today?" If the answer involves complex code or application security, the Mythos premium is justified. For everything else, Opus 4.6 gets the job done.
To go deeper, I've compiled a detailed Mythos vs Opus vs Codex comparison and a comprehensive overview of everything we know about Mythos.
Frequently asked questions
Does Claude Mythos have a public release date in 2026?
No, not as of May 18, 2026. Anthropic restricts access to a closed circle of partners through Project Glasswing, which is focused on cyber defense. My GSC data on ai-first.fr confirms that "claude mythos release date" remains one of the most-searched queries. Demand is strong, but no official announcement has been made.
What does 93.9% on SWE-bench Verified actually mean?
It means Mythos correctly solves 469 out of 500 software engineering problems in the benchmark, real tickets verified by human developers. That's 13 points above Opus 4.6 (80.8%) and Gemini 3.1 Pro's best score (80.6%). The jump is significant, but SWE-bench Pro (77.8%) remains the more reliable test because it eliminates training data leakage.
Does Mythos replace Opus 4.6 for everyday development?
No. In my daily usage, Opus 4.6 remains faster (0.8s versus 2.3s to first token), three to five times cheaper per token, and equally effective on routine tasks. Mythos only takes the lead on heavy refactors, security auditing, and following very long instructions (over 3,000 tokens of structured context).
Are the "thousands of zero-days" found by Mythos real?
Anthropic's methodology relies on 198 manual reviews with a 90% confirmation rate, extrapolated to the full set of results. Skeptics challenge this extrapolation, and they are partly right about the lack of independent auditing. However, the Rust Foundation confirmed real vulnerabilities found by Mythos in the Rust standard library (public pull requests on GitHub), which at minimum validates the model's capabilities for real-world code auditing.
How much does Mythos cost compared to Opus 4.6?
Mythos is priced at $125/MTok input, three to five times the Opus 4.6 rate. For a long refactoring session (20,000+ tokens of context), the bill adds up quickly. The cost-to-benefit ratio is only favorable on complex tasks where Mythos saves multiple correction iterations.
Vidéos YouTube
Discussions Reddit
- Anthropic Just Dropped Claude Mythos Preview · r/claude
- Anthropic's Claude Mythos isn't a sentient super-hacker · r/BetterOffline
- Anthropic's Claude Mythos claims rely on just 198 manual reviews · r/theprimeagen
- Mythos is Mostly Hype · r/Anthropic
- Anthropic's Claude Mythos isn't a sentient super-hacker · r/ClaudeAI
- Standard library unsoundness found by Claude Mythos · r/rust