Claude Code just made Opus 5 the default — 1M context window, and fast-mode pricing that changes the calculus

On 24 July 2026, Anthropic shipped Claude Code 2.1.219, making Claude Opus 5 the default Opus model with a 1M-token context window and $10/$50 per-Mtok fast-mode pricing — a meaningful jump for anyone tracking 'Claude Opus 5' and 'AI coding tools 2026' search terms as a proxy for which AI vendor to standardise on.

Anthropic’s Claude Code changelog for 24 July 2026 (version 2.1.219) confirms Claude Opus 5 is now the default Opus model in Claude Code, replacing Opus 4.8. The headline spec is a 1M-token context window — roughly four times what most teams have been working with day to day — alongside fast-mode pricing of $10 per million input tokens and $50 per million output tokens. Anthropic also quietly retired Opus 4.7 from /fast mode entirely, so fast mode now only applies to Opus 5 and Opus 4.8. The same release raised the default nested-subagent spawn depth from 1 to 3, letting orchestrated agent workflows delegate sub-tasks further before a human needs to step back in.

None of this is an incremental point release. A 1M-token context window means an agent can hold a genuinely large codebase, or a full requirements document plus the relevant service layer, in working memory at once — the kind of context loss that has historically forced developers to re-explain constraints mid-task simply stops happening as often. Combined with deeper subagent nesting, it’s a meaningful step toward AI coding tools that can be handed a larger, less tightly-scoped piece of work and trusted to keep the thread.

So what

If you’re a founder or CTO benchmarking “which AI coding tool should our team standardise on” — a search that spikes every time a frontier lab ships a new default model — this is the kind of release that should move the needle on that decision, not just the marketing headline. A bigger context window and deeper agent delegation reduce the babysitting overhead that’s been the real cost of adopting these tools, which is exactly the kind of operational detail that separates AI-assisted development done well from AI-assisted development done as a gimmick. If you’re weighing how to build model-agnostic tooling or governance around which agents your team runs, that’s the work we do in AI-assisted development engagements — get in touch if you want a second opinion before you commit budget to a particular stack.

← All research

More research.

GitHub Copilot SDK is becoming the Microsoft Copilot SDK: what builders of AI products should know

On 28 October 2026 GitHub said its Copilot SDK is being renamed Microsoft Copilot SDK, the programmable layer for the shared Microsoft and GitHub agent harness. No immediate action is needed.

Read ›

GitHub Agent Merge: Copilot now watches your pull requests and fixes what blocks the merge

On 28 October 2026 GitHub added Agent Merge to pull requests: a 'Watch and fix' option where Copilot repairs failing Actions workflows and merge conflicts in the cloud, optionally with auto-merge.

Read ›

Claude Code 2.1.314 adds a setting that blocks AI file writes outside the project folder

Claude Code 2.1.314 (30 October 2026) adds permissions.blockWritesOutsideWorkingDirectories, so Claude's file-editing tools refuse any path outside the project in every permission mode.

Read ›

GitHub Enterprise now includes Copilot: seats are bundled, AI usage moves to your budget

From 28 October 2026 account-team customers can get Copilot included with every GitHub Enterprise licence, with AI usage metered against an enterprise budget from the first request. Standalone Copilot is $10 per user per month.

Read ›

GitHub Copilot Fusion goes GA: one pick, many models, and a 30% launch discount

On 28 October 2026 GitHub made Copilot Fusion generally available: instead of choosing a model, developers pick an effort level and Copilot routes each task across models. Paid plans get 30% off model costs for a limited time.

Read ›

GitHub Agentic Workflows is generally available: automations written in plain Markdown

On 28 October 2026 GitHub made Agentic Workflows generally available: AI agents that triage issues, analyse CI failures and update docs, defined in Markdown and run inside GitHub Actions with read-only defaults.

Read ›

Start a project

Building with AI? Let's talk.

Tell us what you are building. We'll give you an honest view of the right approach.

Start a projectSee our work