Claude Mythos vs Opus 4.7 and 4.8: Real SWE-bench Scores, Reddit 90:1 Ratio, and Sonnet 4.8 Still Missing

In short: Claude Mythos outperforms Opus 4.7 by 13 points on SWE-bench Pro (77.8% vs 64.3%) according to Anthropic's official benchmarks. Mythos remains restricted to the 12 founding partners of Project Glasswing and over 40 additional organizations, with no general availability in sight. Opus 4.7, the accessible model, is piling up documented regressions (MRCR long-context -33 pts, agentic cost 3.6x). Update May 28, 2026: Claude Opus 4.8 just launched, reaching 69.2% on SWE-bench Pro (+5 pts vs 4.7), Fast mode 3x cheaper, and long-context partially restored (GraphWalks 1M tokens: 68.1%) according to Anthropic's official announcement. Sonnet 4.8 still has no confirmed date as of June 2, 2026.

In May 2026, Anthropic is forcing developers into an uncomfortable three-tier choice: Claude Mythos, which crushes every agentic coding benchmark with a 24-point lead over Opus 4.6, and a 13-point lead over Opus 4.7, on SWE-bench Pro (77.8% vs 64.3%), remains out of reach for the general public. Opus 4.7, available today, deeply divides the community. And Sonnet 4.8 is waiting in the wings: leaked Claude Code source code (March 2026) hints at a more efficient version for everyday development tasks.

What's at stake here goes beyond a simple version war. It's a question of what developers actually need from an AI model: a reliable daily assistant, or a powerhouse you can't even touch?

Two models, two philosophies at Anthropic

Mythos is a capability demonstrator reserved for security research; Opus is the daily production tool for developers. This distinction fundamentally changes how to evaluate the two models.

Mythos and Opus 4.7 come from the same lab, but they serve different needs. Understanding this distinction changes how a technical team should plan its AI investments.

Why did Anthropic separate Mythos from Opus?

Claude Opus remains Anthropic's "general public" model family. The 4.5, 4.6, 4.7 progression follows an incremental logic: each version fixes weaknesses, improves instruction following, and refines multimodal capabilities. It's a relatively smaller model, optimized for large-scale deployment.

Mythos is a different beast altogether. As Matthew Berman puts it in his analysis video, "the 25-point jump on SWE-bench Pro between Opus 4.6 and Mythos Preview doesn't happen in a single iteration. That represents months of work on a fundamentally different model." Rumors point to a 10-trillion-parameter model. If true, it's easy to see why it doesn't run on your Max subscription.

Opus is a production tool. Mythos is a capability demonstrator.

The Data Science in your pocket channel captures the distinction well: Opus 4.7 excels as a "knowledge expert" (raw reasoning, instruction following, reliability), while Mythos shines in "task execution" (agentic behavior, deep analysis, systems thinking). For a developer shipping code every day, this nuance matters.

What is Mythos's real position in the ecosystem?

Mythos was announced through Project Glasswing, a defensive cybersecurity program. According to Anthropic, Mythos Preview has already found thousands of critical vulnerabilities in every major operating system and browser. YouTube analysts (Matthew Berman, AICodeKing) cite specific examples: a 27-year-old vulnerability in OpenBSD, a 16-year-old bug in FFmpeg that millions of automated tool runs had missed. The model chains Linux kernel exploits autonomously.

This is not a tool for writing React components. It's a system that reasons about code at a level most human developers never reach. Anthropic put it in the hands of AWS, Apple, Google, Microsoft, NVIDIA, CrowdStrike, Broadcom, Cisco, and JPMorganChase, not SaaS startups.

The benchmarks tell a clear story

On SWE-bench Pro, the benchmark that measures the resolution of real GitHub issues under real-world conditions, Mythos Preview hits 77.8% versus 64.3% for Opus 4.7, a 13-point gap. The numbers don't lie, but they don't tell the whole story. Here's what the head-to-head comparison reveals about the gulf between the two models.

How should we interpret the SWE-bench gap?

The jump from Opus 4.6 to 4.7 (53.4 → 64.3 on SWE-bench Pro) already represents over 10 points in a single iteration. That's an unusual gain for a point release. But Mythos still sits 13 points above Opus 4.7.

The interesting question is the one Matthew Berman raises: "If Opus keeps climbing from 4.7 to 4.8, 4.9, at what point do the scores get so close to Mythos that Anthropic can no longer justify keeping it private?" The red line is clearly not a fixed score. It's a question of offensive capability, not raw performance.

Can we still trust benchmarks?

A comment on r/claude sums up the ambient skepticism: "Gemini wins on plenty of benchmarks and still garbage in production." Benchmarks measure the resolution of isolated problems. They don't measure reliability over 8 hours of continuous work, context management across a 50,000-line repo, or the ability to not hallucinate a git hash.

For teams that outsource their development, the question isn't "which model scores highest" but "which model breaks the fewest things when running autonomously."

What developers actually experience with Opus 4.7

Opus 4.7 (launched April 16, 2026) outperforms Opus 4.6 by 10 points on SWE-bench Pro in benchmarks, yet a large majority of production users report the opposite. On MRCR v2 (multi-needle benchmark at 256k tokens), Opus 4.7 drops from 91.9% to 59.2% vs Opus 4.6, a -32.7 point decline according to the GitHub tracker anthropics/claude-code#58369. The new tokenizer inflates input consumption by up to 35% depending on content type; total cost on measured agentic workflows reaches 3.6x that of Opus 4.6. Claude Opus 4.8 (launched May 28, 2026) partially addresses these regressions: 69.2% on SWE-bench Pro, GraphWalks long-context at 68.1% (1M tokens), and Fast mode at $10/$50, which is 3x cheaper than Opus 4.7's Fast mode ($30/$150) according to Anthropic's announcement. The tokenizer remains unchanged, as does standard pricing ($5/$25).

The benchmarks promise a 10-point gain. The real-world story is more nuanced.

Why is the community so divided on Opus 4.7?

A r/ClaudeCode user compiled 110 threads and 2,187 comments from the Opus 4.7 launch weekend (April 16, 2026). The result: 41 explicitly critical threads (3,500 cumulative upvotes) against 9 positive threads (39 upvotes). A 90:1 ratio against the model. An underreported aggravating factor: the new Opus 4.7 tokenizer inflates input consumption by up to 35% depending on content type. The listed price ($5/$25 per million tokens) stays identical to Opus 4.6, but the actual bill goes up, reaching 3.6x on agentic workflows measured in anthropics/claude-code#58369.

The most upvoted thread (1,631 points, 700 comments) is titled "Opus 4.7 is legendarily bad." The second (1,347 points) talks about an "AI layoff due to rising costs." BoxminingAI echoes the disappointment: "The jump from 4.5 to 4.6 was big. I was hoping 4.7 would fix our problems. It didn't."

Still, positive voices exist. One Max subscriber describes Opus 4.7 on max effort as "a notable improvement for coding and planning compared to 4.6." Another notes that it "follows instructions better and finishes tasks before claiming it's done."

The emerging pattern: Opus 4.7 performs better when you invest in prompting and configuration.

What does the Opus 4.6 "lobotomy" reveal?

A viral r/ClaudeCode post (2,448 upvotes) documents with PostgreSQL data what the author calls the "lobotomy" of Opus 4.6. Across 68,644 messages analyzed over 34 days, the worst observed ratio was 5 reasoning blocks for 147 tool calls. The model was literally stopping to think on certain turns.

Boris Cherny, the creator of Claude Code, confirmed on Hacker News that turns where the model fabricated information (Stripe API versions, git hash suffixes) had "zero reasoning emitted." Not reduced reasoning: zero.

This context explains why the community approaches Opus 4.7 with suspicion. Developers paying $400 a month want predictability, not benchmarks. And that's exactly what Mythos promises without being able to deliver it to the general public yet.

What Mythos being out of reach means for the market

Mythos Preview (launched April 7, 2026) is restricted to the 12 founding partners of Project Glasswing (AWS, Apple, Google, Microsoft, NVIDIA, CrowdStrike, Broadcom, Cisco, JPMorganChase, Palo Alto Networks, the Linux Foundation, and Anthropic itself) and over 40 additional organizations, with no general availability date and no public pricing. For SMBs and independent developers, the most concrete horizon remains Opus 4.7 (despite its active regressions) or Sonnet 4.8, expected sometime in May-June 2026, with no confirmed date from Anthropic as of May 26, 2026. This access asymmetry is reshaping competition in the AI-assisted development market.

According to the official Project Glasswing announcement, Anthropic is committing up to $100 million in Mythos Preview usage credits, along with $4 million in direct donations to open-source organizations (including $2.5M to Alpha-Omega and the OpenSSF, and $1.5M to the Apache Software Foundation). The message is clear: Mythos is a strategic asset, not a consumer product.

How does the Mythos lockdown change the game?

An r/claude user asks the right question: "If Mythos is what they're showing publicly, what's the internal ceiling we're not seeing? Public benchmarks are always the floor, not the ceiling."

Another user's comment takes it further: "We were using the student. They were building with the professor." This asymmetry has direct consequences. Development teams that rely on Claude to ship code are using a version significantly less capable than the one used to build Claude itself.

For skeptics, DesignCourse points out that this "playbook" has existed since 2019 at OpenAI: announce a model "too dangerous" for the public, generate hype, then monetize access gradually. OpenAI has since responded to Mythos with GPT 5.4 Cyber, a model similarly restricted to a handful of companies. The arms race is on.

How should you prepare without access to Mythos?

I work with development teams in Vietnam that ship code every day using Claude Code and Opus 4.6. What I see: the differentiator is no longer the model itself, but the engineer's ability to structure their work with AI.

A senior developer who understands their architecture, tests, and prompting gets results from Opus 4.6 that a junior wouldn't achieve even with Mythos. That's the reality benchmarks don't capture. AI amplifies the output of good developers. It doesn't turn a non-engineer into a software architect.

According to the World Economic Forum, AI and big data skills rank among the most in-demand by 2030. But "AI skills" doesn't mean "knowing how to prompt ChatGPT." It means knowing how to integrate AI into a rigorous engineering workflow.

On that note, the accidental leaks from Claude Code's source code (March 31, 2026), a source map file accidentally published in npm package v2.1.88, discovered by security researcher Chaofan Shou, exposing ~512,000 lines of TypeScript with references to unreleased models, point to Sonnet 4.8 as the next accessible version. According to NxCode's analysis (April 2026), the initial window was May 2026 (3 to 4 weeks after Opus 4.7 on April 16), but that window has now passed with no official release (May 26, 2026). Prediction markets had estimated a 3% chance of a release before May 24. The anticipated improvements according to the npm leaks and Julian Goldie's X leaks (May 2026): vision ~98% accuracy (vs 54.5% for Sonnet 4.6), coding gains of 82-84% on SWE-bench Verified (+12 pts), a new xhigh effort level, improved instruction following, and unchanged pricing at $3/$15 per million tokens. For teams disappointed by Opus 4.7, this is the nearest horizon, well before any hypothetical Mythos opening.

What this concretely means for your team

For a team shipping software in 2026: Opus 4.8 (released May 28) is the immediate upgrade, with 69.2% on SWE-bench Pro, Fast mode 3x cheaper than 4.7, and long-context partially restored according to Anthropic's official announcement. If Opus 4.7's regressions pushed you back to 4.6, Opus 4.8 is the logical next step. Sonnet 4.8 still has no confirmed date as of June 2, 2026. The Mythos vs Opus battle isn't just a tech spectacle. It's redefining the selection criteria for anyone building software in 2026.

What criteria should you use to choose your model?

For a team shipping a SaaS or business application, three factors matter more than the SWE-bench score:

Reliability over time (the model doesn't regress after 3 hours of session), cost predictability (a model that consumes 2x more tokens per task costs 2x more, even if it's "smarter"), and integration with your existing workflow (Claude Code, Cursor, API).

On that last point, OpenAI's GPT 5.5 (general flagship, not to be confused with GPT 5.4 Cyber, its restricted cybersecurity counterpart and direct Mythos competitor) claims "fewer tokens per task, less handholding, more autonomy." That's exactly what developers are asking for: not a bigger model, but a model that does more with less. The benchmark race obscures this reality.

For teams that work with Claude Code, the pragmatic choice is now Opus 4.8, released May 28, 2026, which partially fixes the 4.7 regressions and introduces dynamic workflows (parallel execution of hundreds of sub-agents) for large-scale migrations.

Why does the engineer remain the decisive factor?

A Quebec developer posted on r/QuebecTI that he built a complete gas price tracker in a single night (8 PM to 3 AM) using Claude Code: Next.js 15, PostgreSQL + PostGIS, MapLibre, Railway, Sentry. Full stack, 2,293 stations rendered on GPU with intelligent clustering.

What makes this project impressive isn't the model used. It's the engineer's 10 years of full-stack experience. He knew what to ask for, how to structure the work, and when to step in. A beginner with the same tool would have produced a fragile prototype incapable of running in production.

This is the thesis I've advocated since launching GoLive Software: a small, senior team, well-organized and AI-assisted, competes with a much more expensive European team. The winning equation hasn't changed with Mythos. It's gotten stronger. The tools are becoming more powerful, which widens the gap between those who know how to use them and those who don't.

Vibe coding can prototype fast. Building a truly maintainable product still requires architecture, testing, and domain knowledge. Mythos or not.

"The future belongs to augmented developers, not replaced ones. Mythos doesn't change this rule; it reinforces it."

Vincent Roye, May 2026

Frequently Asked Questions

Is Claude Mythos available to the general public in May 2026?

No. Mythos remains in restricted preview, accessible to over 40 partner organizations through Anthropic's Project Glasswing, including AWS, Apple, Google, Microsoft, NVIDIA, and CrowdStrike. Anthropic has not announced a general availability date. Individual developers and SMBs must settle for Opus 4.7, fall back to Opus 4.6, or watch for Sonnet 4.8.

Is Opus 4.7 really worse than Opus 4.6 for coding?

The feedback is mixed. On benchmarks, Opus 4.7 clearly outperforms 4.6 (+10 points on SWE-bench Pro). In practice, many users report regressions: hallucinations, higher token consumption, and unpredictable behavior during long sessions. Several experienced developers recommend staying on Opus 4.6 in "high effort" for production, and testing 4.7 in "max effort" for one-off tasks.

What is the difference between Mythos and OpenAI's GPT 5.4 Cyber?

Both models target cybersecurity and are distributed under restricted access. Mythos has demonstrated vulnerability discovery capabilities (zero-days in OpenBSD, FFmpeg, Linux kernel). GPT 5.4 Cyber is positioned as a direct response to Mythos. The strategic difference: Anthropic distributes Mythos for free to defenders ($100M in credits), while OpenAI's access model remains unclear.

Can a junior developer compensate by using a better AI model?

No. Field reports consistently show that result quality depends more on the engineer's experience than the model used. A senior with Opus 4.6 produces more reliable code than a junior with a superior model, because they know how to structure their architecture, validate outputs, and handle edge cases the AI doesn't anticipate.

Should you wait for Mythos before starting an AI-assisted project?

No. Current tools (Claude Code with Opus 4.6, Cursor, GitHub Copilot) are already mature enough to significantly accelerate software delivery. Waiting for Mythos would mean freezing 6 to 12 months of productivity for an uncertain future gain. The right strategy: invest now in upskilling your existing engineering team on AI.

What is Claude Sonnet 4.8 and what do we know about its release?

Claude Sonnet 4.8 is the next version of Anthropic's mid-tier model; there will be no Sonnet 4.7. In March 2026, a source map file accidentally published in the Claude Code npm package (version 2.1.88, on March 31), discovered by security researcher Chaofan Shou, exposed roughly 512,000 lines of TypeScript containing references to unannounced models. NxCode's analysis (April 2026) projected a May 2026 release, but the initial window (May 5-16) passed with no official launch. On Reddit (r/ClaudeCode, r/claude), the question "where is Sonnet 4.8" has come up weekly since April 2026, with no official response from Anthropic. The anticipated improvements according to the npm leaks and X sources (May 2026): visual accuracy ~98% (vs 54.5% for Sonnet 4.6), coding gains of 82-84% on SWE-bench Verified, a new xhigh effort level, and improved instruction following. Pricing is expected to stay at $3/$15 per million tokens. As of June 2, 2026, Anthropic has released Opus 4.8 (May 28) but Sonnet 4.8 still has no date. For developers frustrated by Opus 4.7, Opus 4.8 is the immediately available alternative; Sonnet 4.8 remains the more affordable option to watch for.

What does Opus 4.8 concretely bring compared to Opus 4.7?

Claude Opus 4.8, released May 28, 2026, addresses several regressions that frustrated the community with Opus 4.7. According to Anthropic's official announcement, it reaches 69.2% on SWE-bench Pro (vs 64.3% for 4.7 and 77.8% for Mythos Preview), 88.6% on SWE-bench Verified, and partially restores long-context via the new GraphWalks benchmark (68.1% at 1M tokens). Fast mode pricing drops from $30/$150 to $10/$50 per million tokens, making it 3x cheaper. The model is roughly 4x less likely than Opus 4.7 to let vulnerabilities in its own code go unflagged. Dynamic workflows in Claude Code now allow orchestrating hundreds of sub-agents in parallel for large-scale migrations. Standard pricing remains $5/$25, and the tokenizer is unchanged, so input consumption follows the same rules as Opus 4.7.

Vidéos YouTube

• I Tested Claude Code vs Codex: What You Need to Know · Nate Herk | AI Automation
• Opus 4.7 just dropped... and I'm confused. · Matthew Berman
• Opus 4.7 is disappointing · BoxminingAI (Superbash)
• Claude Opus 4.7 This Week, OpenAI GPT 5.4 Cyber Ready To Beat Claude Mythos · Codedigipt
• Claude Opus 4.7 vs Mythos · Data Science in your pocket
• Claude Mythos vs. OpenAI Spud - AI Psychosis at its Finest · DesignCourse
• Claude Epitaxy, Mythos FAST Mode, Opus 4.7, Sonnet 4.8, Leaks · AICodeKing
• Claude Tiers Explained - Sonnet vs Haiku vs Opus · The Data Podcast

Discussions Reddit

• Anthropic just revealed an unreleased AI model that found zero-days · r/AI_Agents
• What if Anthropic has been using a secret model to build Claude for years? · r/claude
• Opus 4.7: 110 threads, 2,187 comments. Unbiased analysis · r/ClaudeCode
• My name is Claude Opus 4.6. I live on port 9126. I was lobotomized. · r/ClaudeCode
• J'ai build un tracker de prix d'essence pour le Québec en une soirée avec Claude Code · r/QuebecTI
• LMAO why OpenAI is hiding the ones where they lose to Opus 4.7? · r/claude

Posts X / Twitter

• Claude Sonnet 4.8 leaks: vision ~98%, coding +12pts, xhigh effort · Julian Goldie SEO on X, May 2026

Projets GitHub

• Categorized regression analysis: Opus 4.7 · GitHub anthropics/claude-code#58369

Articles & ressources

• Project Glasswing: Securing critical software for the AI era · Anthropic
• Introducing Claude Opus 4.8 · Anthropic
• Claude Sonnet 4.8: Release Date, Features & What to Expect · NxCode
• Opus 4.7 Tokenizer Inflation Analysis · OpenRouter
• Claude Opus 4.7 vs 4.6 vs Mythos: Which Model Should You Use? · NxCode