Claude Opus 4.8: What Developers Need to Know About Anthropic's New Flagship

Oleh Kem — Thu, 28 May 2026 17:20:58 +0000

Anthropic shipped Claude Opus 4.8 today. Same price as Opus 4.7, fast mode at 2.5x speed, fast mode 3x cheaper than before. Alongside the model release: dynamic workflows in Claude Code and effort control in claude.ai.

This post covers the benchmark numbers, the practical changes for coding and agents, and what teams building on Claude should pay attention to.

Benchmark Numbers

The numbers that matter most for developers:

SWE-Bench Pro (agentic coding): Opus 4.8 = 69.2%, Opus 4.7 = 64.3%, GPT-5.5 = 58.6%, Gemini 3.1 Pro = 54.2%. A 4.9 point gain over the previous version and a 10.6 point lead over GPT-5.5.

Terminal-Bench 2.1 (agentic terminal coding): Opus 4.8 = 74.6%, GPT-5.5 = 78.2%, Gemini 3.1 Pro = 70.3%. GPT-5.5 leads this benchmark. Opus 4.8 still jumps 8.5 points over Opus 4.7's 66.1%.

OSWorld-Verified (agentic computer use): Opus 4.8 = 83.4%, GPT-5.5 = 78.7%. Browser agent hits 84% on Online-Mind2Web, beating both Opus 4.7 and GPT-5.5.

Humanity's Last Exam (reasoning, with tools): Opus 4.8 = 57.9%, GPT-5.5 = 52.2%, Gemini 3.1 Pro = 51.4%.

Finance Agent v2: Opus 4.8 = 53.9%, GPT-5.5 = 51.8%. First model to break 10% on the all-pass Legal Agent Benchmark.

For cost comparisons across models and workloads, the LLM calculator on ComparEdge is useful for running specific scenarios.

What Changed for Code Quality and Tool Calling

The most relevant change for daily work: Opus 4.8 is roughly 4x less likely than Opus 4.7 to let code flaws pass unremarked. It catches its own mistakes more often, and it pushes back when a plan has problems.

Devin's team confirmed the improvements directly: "Claude Opus 4.8 uses tools cleanly and follows instructions with the consistency our autonomous engineering workloads need to keep running unattended. It improves on Opus 4.6 and fixes the comment-verbosity and tool-calling issues we saw with Opus 4.7."

CursorBench reported that Opus 4.8 exceeds prior Opus models across every effort level, with more efficient tool calling overall.

Tom Pritchard, Staff Engineer at Shopify: "Claude Opus 4.8 has noticeably better judgment. In Claude Code, it asks the right questions, catches its own mistakes, pushes back when a plan isn't sound, and builds up confidence around complex, multi-service explorations before making big changes. It's a great model to build with."

Kay Zhu, Co-Founder and CTO: "On our Super-Agent benchmark, Claude Opus 4.8 is the only model to complete every case end-to-end, beating prior Opus models and GPT-5.5 at parity on cost."

Dynamic Workflows in Claude Code

The biggest feature launch alongside the model: dynamic workflows, available as a research preview in Claude Code. The model plans work and runs hundreds of parallel subagents in a single session. Anthropic says this enables codebase-scale migrations across hundreds of thousands of lines of code, from kickoff to merge.

Available for Enterprise, Team, and Max plans.

This is particularly relevant for large refactors, framework migrations, and cross-service changes where manual orchestration of multiple Claude sessions was previously the only option.

Alignment Improvements

Misaligned behavior (deception, cooperation with misuse) is substantially lower than Opus 4.7. Opus 4.8 scores near 1.83 on Anthropic's misalignment metric, comparable to Mythos Preview (their best-aligned model). Opus 4.7 scored 2.47. This matters for teams running autonomous agents where the model operates without constant human review.

Pricing

Same price as Opus 4.7. Fast mode at 2.5x speed, 3x cheaper than fast mode on previous models. Databricks reported 61% cheaper token cost for their Genie agent compared to Opus 4.7.

I Built a Tool to Stop Guessing LLM API Costs. Here Is What I Learned.

Oleh Kem — Thu, 28 May 2026 16:56:44 +0000

You know that moment when you check your API dashboard and the number has an extra digit you were not expecting? That is where this project started.

We were comparing models for a production pipeline, nothing exotic, just document processing, and realized we had no reliable way to answer a basic question: which model actually costs less for our workload?

So we built one: LLM Calculator. Here is what the build taught us.

The Math Problem Nobody Talks About

LLM pricing looks simple until you try to calculate it for real.

First, input and output tokens have different prices. Most models charge 2 to 5x more for output. A summarization task (lots of input, little output) and a code generation task (little input, lots of output) can have wildly different costs on the same model. The "cheapest model" depends entirely on what you are doing with it.

Then there is batch pricing. OpenAI gives 50% off for batch API calls. If your workload can handle async, that reshuffles the entire ranking. Same story with cached pricing: Anthropic's prompt caching can cut input costs by 90% on repeated prefixes. Are you factoring that in? Most people are not.

Now multiply this across 16 providers and 110+ models: OpenAI, Anthropic, Google, DeepSeek, Groq, Mistral, Meta, Cohere, Together, Perplexity, xAI, Fireworks, Replicate, AI21, Cloudflare, Amazon Bedrock. Prices change constantly. Your mental model of "GPT-4o costs about X" is probably already outdated.

What We Built

A free LLM token cost calculator at comparedge.com/llm-calculator, part of ComparEdge (independent, no vendor affiliations).

Feature tour, dev-to-dev:

Input/output ratio slider. Drag to match your workload profile. Rankings reshuffle in real time. This single feature changed more model decisions than anything else in our testing.

Batch and cache toggles. One click each. Toggle batch pricing for async-tolerant workloads, cached pricing for repeated-prefix scenarios. The cost landscape changes dramatically.

Stack and Compare mode. Pick up to 5 models, see them side-by-side with pricing, context windows, and cost per million tokens for your specific ratio. The "final boss" view for making a decision.

Budget filter. Set a ceiling. Everything over it disappears. Useful when you need to narrow 110 options fast.

10 export formats. PDF and CSV, sure. But also: LiteLLM JSON (for proxy configs), OpenRouter JSON, Python Dict, .env Snippet, Cursor Rules, Markdown, HTML, Plain Text. The output should drop into your actual workflow.

What We Learned Building This

Pricing data is a moving target. We thought the hard part would be the UI. It was not. It was keeping pricing accurate across 16 providers who update at different times, in different formats, with different definitions of what a token even means. Maintenance is the real product.

"Cheapest" is the wrong question. The right question is: cheapest for my specific input/output ratio, with or without batch/cache, within my context window requirements. That is a much harder question, but it is the one that actually saves money.

People do not want more data; they want fewer options. Early versions showed everything. Users were overwhelmed. The budget filter and compare mode exist because people need to go from 110 models to 3 candidates fast.

The Forecasting Problem

Here is what we have not solved yet: predicting future costs.

We are working on a forecasting mode combining growth multiplier, agent overhead, and Pareto concentration factor. The agent overhead part is the tricky bit. Agentic workflows multiply token consumption in ways that are hard to model because the agent decides how many calls to make.

We do not want to ship a forecasting tool that is just "multiply current cost by a number you pick." That is a spreadsheet. We want something that accounts for how LLM usage actually scales. Still in progress.

Try It

Free at LLM Api Calculator Cost. PDF export works without an account. If you use it and have feedback, especially on what export formats are missing or what the compare mode gets wrong, I would genuinely like to hear it in the comments.

DEV Community: ComparEdge