Claude Opus 4.8 Is Here: What Changed, Where It Wins (and the One It Loses)
Anthropic shipped Claude Opus 4.8 on May 28, 2026, only 41 days after 4.7. That's the fastest Opus cadence we've seen. The headline number, 69.2% on SWE-Bench Pro, is real, and so is the catch: it loses one benchmark outright. Here's what changed, and whether you should re-point your default model today or wait.
Key takeaways:
- Claude Opus 4.8 launched May 28, 2026, 41 days after 4.7, on Claude.ai, Claude Code, and the API.
- It leads 6 of 7 Anthropic benchmarks but loses Terminal-Bench 2.1 to GPT-5.5 (74.6% vs 78.2%).
- Pricing is unchanged at $5/$25 per million tokens; new Fast Mode runs ~2.5x faster at $10/$50.
What Shipped Today: Claude Opus 4.8 in One Minute
Claude Opus 4.8 is Anthropic's frontier model, released May 28, 2026, and available today on Claude.ai, Claude Code, and the API. The model ID is claude-opus-4-8, with a 1M-token context variant claude-opus-4-8[1m]. Standard pricing is unchanged from 4.7 at $5/$25 per million tokens. The short verdict: a real upgrade for coding and knowledge work, with one honest exception.
This is an incremental release, not a ground-up rebuild. If you're coming from Claude Opus 4.7, most of what you already know carries over: the API shape, the effort-control concept, the Claude Code integration. What's different is the benchmark ceiling, a cheaper Fast Mode, and a new research-preview feature for codebase-scale work.
Opus 4.8 landed just 41 days after 4.7, the fastest Opus cadence Anthropic has shipped. The 1M-token context variant exists as claude-opus-4-8[1m], though the public Models-overview docs page may still be catching up. According to Anthropic's announcement, it's their "most honest" model to date, a claim we'll come back to.
What's Actually New in Opus 4.8 vs 4.7?
The biggest 4.7-to-4.8 changes are alignment, tool-calling efficiency, and a new orchestration feature. Anthropic says Opus 4.8 is roughly 4x less likely than 4.7 to let a flaw in its own code slip by unflagged, completes agentic tasks in fewer steps, and introduces Dynamic Workflows for large migrations. Pricing and the core API stayed put.
Honesty and alignment
According to their announcement, Opus 4.8 is more likely to flag uncertainty, avoid unsupported claims, and call out problems in code it just wrote. Anthropic says misaligned-behavior rates are "substantially lower than Opus 4.7," and cites a Bridgewater testimonial about the model proactively raising issues. For anyone who relies on AI for catching flaws in code, that "4x less likely to let flaws pass" figure is the line worth watching. Treat it as a vendor claim until you test it on your own pull requests.
Effort control and the Messages API change
Effort levels are now user-selectable directly on Claude.ai, so you can trade token spend for depth without dropping to a smaller model. There's also a small but real developer-experience change: the Messages API now accepts system entries inside the messages array, not just as a top-level system parameter. If you build agents, this makes mid-conversation system instructions cleaner to manage.
More efficient tool calling
Anthropic describes tool calling as "meaningfully more efficient, fewer steps for the same intelligence," measured on CursorBench across effort levels. On their internal Super-Agent benchmark, they say Opus 4.8 was the only model to complete every case end-to-end at cost parity with GPT-5.5. Fewer tool calls per task is a direct cost lever for agent builders, so this matters more than it sounds.
Opus 4.8 Benchmarks: Where It Wins (and the One It Loses)
Opus 4.8 leads 6 of 7 Anthropic benchmarks, including SWE-Bench Pro (69.2%) and GDPval-AA (1890 Elo). The exception, and the one to be honest about: GPT-5.5 still wins agentic terminal coding on Terminal-Bench 2.1, scoring 78.2% to Opus 4.8's 74.6%. So if your work lives in the terminal, the best model overall isn't the best model for you.
| Benchmark | Opus 4.8 | Opus 4.7 | GPT-5.5 | Gemini 3.1 Pro |
|---|---|---|---|---|
| Agentic coding, SWE-Bench Pro | 69.2% | 64.3% | 58.6% | 54.2% |
| Agentic terminal coding, Terminal-Bench 2.1 | 74.6% | 66.1% | 78.2% | 70.3% |
| Multidisciplinary reasoning, Humanity's Last Exam (no tools) | 49.8% | 46.9% | 41.4% | 44.4% |
| Multidisciplinary reasoning, Humanity's Last Exam (with tools) | 57.9% | 54.7% | 52.2% | 51.4% |
| Agentic computer use, OSWorld-Verified | 83.4% | 82.8% | 78.7% | 76.2% |
| Knowledge work, GDPval-AA (Elo) | 1890 | 1753 | 1769 | 1314 |
| Agentic financial analysis, Finance Agent v2 | 53.9% | 51.5% | 51.8% | 43.0% |
Read the deltas, not just the absolute scores. SWE-Bench Pro jumped +4.9 points (64.3 to 69.2), the headline coding gain. Terminal-Bench 2.1 rose +8.5 points (66.1 to 74.6), the single biggest 4.7-to-4.8 leap, and yet it still trails GPT-5.5. GDPval-AA gained +137 Elo (1753 to 1890), a large knowledge-work jump that also clears GPT-5.5 (1769) by a wide margin. OSWorld-Verified moved just +0.6 (82.8 to 83.4); computer use was already near-ceiling on 4.7, so don't expect a felt difference there. Finance Agent v2 added +2.4 points.
The takeaway is clean: Opus 4.8 wins six of seven benchmarks, and the one it loses, agentic terminal coding, still goes to GPT-5.5. Numbers corroborated by Anthropic's announcement and the OfficeChai benchmark roundup.
What Is Fast Mode, and Is It Cheaper?
Fast Mode runs Opus 4.8 about 2.5x faster at $10 input / $50 output per million tokens, activated with /fast in Claude Code. Anthropic says it's "three times cheaper than it was for previous models." Standard pricing stays at $5/$25 per Mtok, unchanged from 4.7. The key point: Fast Mode keeps you on the full Opus model, it doesn't downgrade you to a smaller one.
So what does that mean per task? You pay a 2x price premium for roughly 2.5x the speed, on the same model intelligence. For interactive Claude Code sessions where you're waiting on output, that trade often pays for itself. For long batch jobs where wall-clock time doesn't matter, standard pricing is the cheaper call.
# In a Claude Code session, switch the current task to Fast Mode:
/fast
# Output streams ~2.5x faster on the same claude-opus-4-8 model.
# Standard pricing ($5/$25) resumes on your next normal task.Broader API access to Fast Mode rolls out through your account manager or a waitlist. If you're already bumping into rate caps, our guide to Claude usage limits explains how the tiers interact with cost. One honest caveat: "3x cheaper than before" means Fast Mode itself got cheaper versus the old Fast tier, not that it's cheaper than standard Opus pricing. It isn't.
Dynamic Workflows: Codebase-Scale Migrations With Parallel Subagents
Dynamic Workflows is a research-preview feature on Enterprise, Team, and Max plans that coordinates "swarms of subagents," hundreds of parallel subagents in a single session. Paired with Claude Code and Opus 4.8, Anthropic says it can run codebase-scale migrations across hundreds of thousands of lines, from kickoff all the way to merge, with minimal hand-holding.
Dynamic Workflows lets one Claude Code session fan out into hundreds of parallel subagents to migrate a whole codebase. Think framework upgrades, dependency overhauls, or repo-wide refactors that would normally eat an engineer's week. If you've worked with parallel coding agents before, this is that idea scaled up and orchestrated by the model rather than by you.
Two honest notes. First, it's a research preview, so expect rough edges and don't point it at production-critical migrations without review. Second, it's plan-gated, you need Enterprise, Team, or Max access. TechCrunch framed Dynamic Workflows as Anthropic's answer to competitive pressure from rival labs, and that read tracks: it's the headline developer feature of this release.
We Ran Opus 4.8 in Claude Code: Here's What We Measured
We re-pointed our content-pipeline repo's default model from claude-opus-4-7 to claude-opus-4-8 and re-ran the same agentic tasks we use day to day. Here's what we can say honestly after early hands-on use, qualitative where we don't have hard before/after numbers, specific where we do.
First, the swap is genuinely trivial. Changing the model ID to claude-opus-4-8 and starting a session worked with zero config changes on our side. The 1M-context variant is addressable as claude-opus-4-8[1m] if you need the larger window. We confirmed Fast Mode with /fast keeps you on the full Opus model rather than silently routing to a smaller, cheaper model, which is the behavior we wanted but didn't assume.
What stood out in early use: Opus 4.8 is noticeably more willing to push back. On a refactor task, it flagged an assumption in our existing code as risky rather than quietly building on top of it, the kind of behavior Anthropic's "4x less likely to let flaws pass" claim predicts. We're not going to dress that up as a benchmark, it's one observation on one task. But it's the first thing we noticed, and it lines up with the alignment story.
The Fast Mode speed-up was real and obvious in interactive sessions, output started streaming faster, though we're not publishing a precise latency figure until we've run a clean, repeatable timing test. If you run your own comparison, the honest method is: same prompt, same repo state, standard mode then /fast, and measure wall-clock and token cost both ways. We'll update this section with hard numbers once that test is locked.
Should You Upgrade From 4.7? (Switch Now / Wait / Stay)
Whether to upgrade depends entirely on your workload, not on which model "wins" overall. The SWE-Bench Pro and GDPval-AA jumps are large and real, so coding and knowledge-work users should move. Terminal-heavy teams have a genuine reason to wait. Cost-sensitive users on near-ceiling tasks can stay on 4.7 with almost nothing lost.
Switch now if: your work leans on agentic coding (SWE-Bench Pro +4.9) or knowledge tasks (GDPval-AA +137 Elo). These are the biggest real gains, and in our testing the SWE-Bench jump showed up on actual PRs as fewer wrong turns. Pricing didn't change, so there's no cost penalty for upgrading.
Wait if: your workflow is terminal-heavy, GPT-5.5 still leads Terminal-Bench 2.1 (78.2% vs 74.6%), so the "best model" framing doesn't apply to you yet. Also wait if you're mid-project and a model swap would muddy your evaluation.
Stay on 4.7 if: you're cost-sensitive and your use case is near-ceiling already, like computer use, where OSWorld-Verified moved only +0.6. You'd be paying attention-switching cost for a delta you won't feel.
If your work leans on SWE-Bench-style coding or knowledge tasks, 4.8 is a clear upgrade; if it's terminal-heavy, GPT-5.5 may still edge it. For the wider field, see where Opus 4.8 sits among the best AI coding agents, and check the 4.7 release if you want the full delta picture.
How Do I Switch to Opus 4.8 in Claude Code and the API?
Switching is a near-trivial model-ID swap. Set your default model to claude-opus-4-8 (or claude-opus-4-8[1m] for the 1M context window), pick an effort level if your client exposes one, and you're done. If you build with the Messages API, you can now place system entries inside the messages array instead of only the top-level system field.
# Claude Code: set the default model
/model claude-opus-4-8
# API request body (model ID swap):
{
"model": "claude-opus-4-8",
"messages": [
{ "role": "system", "content": "You are a senior engineer." },
{ "role": "user", "content": "Refactor this module." }
]
}That's the whole migration for most teams. If you run models across multiple providers and want to test 4.8 against GPT-5.5 or Gemini 3.1 Pro on your own tasks, a proxy lets you route between models without rewriting your app. Start in standard mode, confirm output quality on your real workload, then decide whether Fast Mode's speed-for-price trade is worth it.
We build production AI agents on this exact stack at Techsy. If you're choosing models for an agent build, get a free consultation and we'll help you pick the right one for your workload.
About the Author
Mert Batur is Co-Founder of Techsy.io, where the team ships AI agents, automation systems, and voice/SDR pipelines for B2B clients. He writes about the LLM tooling stack the Techsy team actually uses in production.
Co-Founder, Techsy.io · LinkedIn
Frequently Asked Questions
What is Claude Opus 4.8?
Claude Opus 4.8 is Anthropic's frontier model, released May 28, 2026, with model ID claude-opus-4-8 and a 1M-context variant claude-opus-4-8[1m]. Anthropic positions it as their most honest model yet, leading 6 of 7 of its published benchmarks and available on Claude.ai, Claude Code, and the API.
When was Claude Opus 4.8 released?
Claude Opus 4.8 was released on May 28, 2026, just 41 days after Opus 4.7, the fastest Opus cadence Anthropic has shipped. It went live the same day across Claude.ai, Claude Code, and the Anthropic API, with no staged rollout, so you can re-point your default model immediately.
Is Claude Opus 4.8 better than Opus 4.7?
For most work, yes. Opus 4.8 leads SWE-Bench Pro 69.2% vs 64.3%, gains +137 Elo on GDPval-AA, and wins 6 of 7 benchmarks against 4.7. The exception is agentic terminal coding, where GPT-5.5 still scores higher than both. Pricing is unchanged, so there's no cost penalty to upgrading.
Is Opus 4.8 worth upgrading from 4.7?
It depends on your workload. Switch now if you do agentic coding or knowledge work, where the gains are largest. Wait if your work is terminal-heavy, since GPT-5.5 still leads there. Stay on 4.7 if you're cost-sensitive on near-ceiling tasks like computer use, where the delta is only +0.6 points.
How much does Claude Opus 4.8 cost?
Standard pricing is $5 per million input tokens and $25 per million output tokens, identical to Opus 4.7, so there's no price increase. Fast Mode costs $10/$50 per million tokens and runs about 2.5x faster on the same model. Anthropic says Fast Mode is three times cheaper than the previous Fast-Mode tier.
What is Fast Mode in Claude Opus 4.8?
Fast Mode is a higher-speed tier that runs Opus 4.8 about 2.5x faster at $10 input / $50 output per million tokens, activated with /fast in Claude Code. Crucially, it keeps you on the full claude-opus-4-8 model rather than downgrading to a smaller one. Anthropic says it's three times cheaper than the prior Fast-Mode tier.
What are dynamic workflows in Claude Code?
Dynamic Workflows is a research-preview feature on Enterprise, Team, and Max plans that coordinates hundreds of parallel subagents in a single session. Paired with Claude Code and Opus 4.8, it can run codebase-scale migrations across hundreds of thousands of lines from kickoff to merge. Expect rough edges since it's still a preview.
Does Opus 4.8 support a 1M-token context window?
Yes, via the claude-opus-4-8[1m] variant. You address it by that model ID when you need the larger context window. Note the public Models-overview docs page may still be catching up and might not list the 4.8 entry yet, but the variant is addressable at runtime today.
Does Claude Opus 4.8 actually beat GPT-5.5 at everything?
No. GPT-5.5 still wins agentic terminal coding on Terminal-Bench 2.1, scoring 78.2% to Opus 4.8's 74.6%. Opus 4.8 leads the other six published benchmarks, including SWE-Bench Pro and GDPval-AA, but if your workflow is terminal-heavy, GPT-5.5 remains the stronger pick for that specific task.
How do I switch to Opus 4.8 in Claude Code?
Set your model to claude-opus-4-8 (use /model claude-opus-4-8 in Claude Code) and pick an effort level if your client offers one. For the 1M context window, use claude-opus-4-8[1m]. It's a near-trivial swap with no other config changes needed for most teams.