Anthropic announced Claude Opus 4.8 on May 28, 2026. It is not pitched as a giant architectural break from Opus 4.7. It is a sharper, more reliable version of the flagship model, aimed at the kind of work where small judgment improvements compound: long coding sessions, multi-step agent runs, tool-heavy research, and professional analysis where unsupported confidence is expensive.

The main story is simple: Opus 4.8 keeps regular pricing unchanged at $5 per million input tokens and $25 per million output tokens, while improving benchmark results, tool behavior, effort calibration, and honesty. The model ID is claude-opus-4-8.

What changed

Opus 4.8 builds directly on Opus 4.7, with improvements concentrated in areas that matter for agentic work:

• Better long-horizon coding and long-context behavior
• More reliable tool triggering
• Better recovery after context compaction
• Stronger reasoning effort calibration
• Fewer unsupported claims about whether its own work is correct
• Lower rates of misaligned behavior than Opus 4.7, according to Anthropic’s alignment assessment

The honesty point is the one I would pay closest attention to. Anthropic says Opus 4.8 is about four times less likely than Opus 4.7 to let flaws in its own code pass unremarked. That is not the same as saying the model writes flawless code. It means the model is more likely to notice and say when something may still be wrong.

For agentic coding, that behavior matters. A model that pauses to flag uncertainty is often more useful than a model that confidently reports success after a brittle pass through the task.

Dynamic workflows are the bigger product shift

The model launch landed alongside dynamic workflows in Claude Code. This is the most important product change in the announcement.

Dynamic workflows let Claude plan a large task, split it into subtasks, run many parallel subagents, verify outputs, and then report back with a coordinated result. Anthropic describes use cases like codebase-wide bug hunts, modernization work, security reviews, optimization audits, and large migrations.

The practical implication is that Claude Code is moving beyond “one agent with tools” toward “one supervising model orchestrating many agents.” That changes the kind of work people will try to hand off. A single-file refactor is no longer the interesting case. The interesting case is a migration across hundreds of files where the system has to plan, fan out work, reconcile results, and drive the test suite until it converges.

There is a cost caveat. Dynamic workflows can use substantially more tokens than a normal Claude Code session. The right way to adopt them is not to throw the entire monorepo at the model on day one. Start with a scoped cleanup, a bounded migration, or a codebase-wide audit where the expected output is clear.

Effort is now a first-class control

Opus 4.8 defaults to high effort across Claude surfaces. Anthropic says this gives the best balance of quality and user experience. Users can choose lower effort for faster, cheaper turns, or higher settings for harder work.

The naming depends on the surface:

• In Claude Code, xhigh maps to the higher-effort mode Anthropic calls “extra” in the announcement.
• Claude.ai now exposes effort controls next to the model selector.
• The API documentation describes high as the default for Opus 4.8.

This is a useful shift because “use more thinking” is no longer a vague prompt instruction. It becomes an operating mode. For routine edits, high may be enough. For long-running async workflows, architecture changes, and migrations, xhigh is the more sensible default.

Fast mode gets more interesting

Opus 4.8 also supports fast mode, where the same model can produce output at up to 2.5x the speed. The regular API price is unchanged, while fast mode is priced at $10 per million input tokens and $50 per million output tokens.

That is still premium pricing, but the tradeoff is clearer than before. For interactive coding sessions, fast mode can reduce waiting time without switching to a smaller model. For background workflows, I would still default to regular mode unless latency is the bottleneck.

API changes developers should notice

The Messages API now accepts system entries inside the messages array. That means an agent harness can update instructions mid-task without stuffing everything through a user message or invalidating useful prompt-cache structure.

That sounds small, but it is a real agent feature. Long-running systems often need to update constraints as the environment changes:

• A tool becomes unavailable
• A token budget changes
• A permission boundary gets tighter
• A task moves from exploration to implementation
• A reviewer asks the agent to apply a specific rule for the rest of the run

Opus 4.8 also keeps the Opus 4.7 API constraints: non-default sampling parameters are not supported, and adaptive thinking is the supported thinking mode. If you have old code passing custom temperature, top_p, top_k, or fixed thinking budgets, check the migration guide before swapping model IDs.

The API docs also list a 1M token context window by default on the Claude API, Amazon Bedrock, and Vertex AI, with 200K on Microsoft Foundry. Max output is listed at 128K tokens.

What to test before upgrading

If you already use Opus 4.7, the upgrade path looks straightforward, but I would still smoke-test a few things:

• Long agent traces that rely on context compaction
• Tool calls that previously needed explicit reminders
• Prompts that depend on sampling controls
• Cost on workloads where effort settings change token use
• Any harness that mutates system instructions mid-run
• Claude Code workflows that run unattended for hours

The likely win is not a dramatic improvement on every one-shot prompt. The likely win is fewer derailments during long work, better tool discipline, and more honest reporting when the model is uncertain.

Should you use it?

If you are already paying for Opus, yes, test Opus 4.8 immediately. Same regular price, better agent behavior, stronger honesty, and useful product features around effort and workflows make it the new default candidate for serious Claude work.

If you are cost-sensitive, the answer is more nuanced. Opus remains a premium model. Use it where judgment, codebase context, and autonomy matter. Use cheaper models for routine generation, simple edits, and high-volume background tasks that do not need frontier reasoning.

My read: Opus 4.8 is less about raw intelligence theater and more about operational reliability. That is the right direction. The next frontier is not just “can the model solve the benchmark?” It is “can the model keep working, check itself, ask the right questions, and stop pretending when the evidence is thin?”

That is exactly where agentic systems break in practice. Opus 4.8 is Anthropic tightening that loop.

Learn more

• Introducing Claude Opus 4.8
• What’s new in Claude Opus 4.8
• Introducing dynamic workflows in Claude Code