Claude Opus 4.7: Benchmarks, xhigh Effort Level, and What Changed

Claude Opus 4.7 is Anthropic's most capable publicly available model as of April 16, 2026 — and if you use the API for agentic coding or production tasks, you should upgrade today. The headline improvements are a 13% lift on coding benchmarks, a new xhigh effort level designed specifically for long agentic runs, and high-resolution vision support at up to 3.75 megapixels. Based on our analysis of the release, Opus 4.7 resolves 3x more production tasks than its predecessor in Anthropic's internal evals — a meaningful leap that closes the gap between what developers delegate to AI and what actually ships.

Released on April 16, Opus 4.7 arrives as Anthropic's public-facing flagship while Claude Mythos Preview — a restricted model with 93.9% SWE-bench scores — stays locked inside covers this routing decision in detail.

The task budget feature makes Opus 4.7 significantly more cost-predictable in production. Capping an agentic loop at 50,000 tokens means you can estimate monthly costs from task volume — a calculation that was difficult before because model behavior on long tasks was hard to bound without budget constraints.

API Migration Guide: From Opus 4.6

The migration is minimal — there are no breaking changes to the Messages API format. The primary change is the model ID. Update from claude-opus-4-6-20260229 to claude-opus-4-7-20260416. If you use the Claude Code CLI, running claude update pulls the latest version, which defaults to Opus 4.7 for agent operations.

Two things to verify after migration:

1. Instruction scope: Test any prompts that previously relied on Opus 4.6's implicit generalization behavior. Where the model used to expand scope silently, it will now follow the literal instruction. Add explicit scope instructions where needed.




2. Effort level: Update agentic loops from effort: "high" to effort: "xhigh" and measure the completion rate improvement against the cost increase. For most agentic coding tasks, the ROI is positive within the first week of production traffic.

For teams using