Introducing Claude Opus 4.7 in Warp
Claude Opus 4.7 is now available in Warp on paid plans and is the default model for auto (genius).
Opus 4.7 brings stronger performance to the coding and agent workflows many Warp users rely on most, and we're excited to make it available to users. In our testing, it especially stood out on tougher coding tasks, including Terminal Bench problems and a tricky concurrency bug that Opus 4.6 couldn't solve.
Where Opus 4.7 stood out
Opus 4.6 was already one of the best models available for developers, so the bar was high. What we saw with Opus 4.7 was stronger performance on the kinds of tasks that matter most in real development workflows:
- harder, multi-step coding tasks
- debugging and problem solving that require more persistence
- coding agent workflows where thoroughness matters more than speed alone
What stood out to us was that Opus 4.7 also broke through on some of the hardest Terminal Bench tasks, solving about 4% of tests that models have historically struggled to pass.
That combination of stronger reasoning and more thorough execution made it feel like a meaningful step forward for Warp users.
Limited-time pricing
Through April 30, 2026, we're also passing through a 50% promotional discount on Opus 4.7 usage. During the promo period, your credits will go twice as far on Opus 4.7.
Try it in Warp
Update to the latest version of Warp, with new features like vertical tabs, and try Opus 4.7 with Warp Agent, or set it as the default model for your cloud-agent runs in Oz.
Related articles
May 14, 2026 · 10 min
Agents Need Feedback Loops, Not Perfect Prompts
For agents doing judgement-heavy work, the starting prompt is only the beginning. The best agents learn what good looks like from the team and improve themselves over time.
May 4, 2026 · 9 min
Open-sourcing our docs and the agents that maintain them
Today, we’re moving our product documentation at docs.warp.dev onto a stack we control end-to-end, and open-sourcing it at github.com/warpdotdev/docs.
Apr 29, 2026 · 16 min
The Block Model Behind Warp's Agentic Development Environment
Warp has come a long way since it initially set out to modernize the terminal. In the screenshot above, an agent is working through a plan alongside a developer's own shell commands — running its own commands, reasoning, proposing a diff — all in the same scroll stream. Five years ago, none of that would have had a place in Warp; today it's a core part of how people use it.
