Claude Opus 4.7 Is Here: 87.6% SWE-bench, 1M Context, and Effort Controls That Change How You Vibe Code

Anthropic just shipped Claude Opus 4.7, and the spec sheet reads like a wishlist from six months ago: 87.6% on SWE-bench Verified, 94.2% on GPQA, a 1M token context window, enhanced vision, and — most practically significant for vibe coders — effort controls and task budgets that let you dial exactly how hard Claude works on a given task. All of this at unchanged pricing ($5/$25 per million tokens). The SWE-bench number is impressive context: 87.6% puts Opus 4.7 well above the human expert median (~70%) on real-world GitHub issue resolution. The 1M context window means you can feed an entire mid-sized codebase into a single session and get coherent architectural analysis across it all. But the feature that most changes day-to-day vibe coding workflow isn't either of those — it's the effort controls and task budgets, which let you explicitly control the compute-cost-quality tradeoff for each task. This post unpacks what all of this means practically, with concrete examples of how to use the new controls in Claude Code workflows today.