Anthropic Releases Claude Opus 4.6

Anthropic released Claude Opus 4.6 on February 5, 2026, available through the Claude API at $15 per million input tokens and $75 per million output tokens, with a 200K-token context window in standard usage and a 1M-token context window in beta for enterprise customers with large codebase or document-analysis requirements. Claude Opus 4.6 was positioned as Anthropic’s most capable model for agentic tasks — long-running workflows where the model executes sequences of tool calls, code execution, web searches, and file operations across sessions measured in minutes or hours rather than single-turn exchanges.

Improvements reported by Anthropic centered on coding and computer use: the model could navigate large software repositories, identify bugs across multiple interdependent files, write and run tests to verify fixes, and maintain consistent context about project architecture without losing track of constraints established at the start of a session. Computer use — controlling a desktop through screenshots and cursor actions — saw reliability improvements on multi-step tasks such as filling multi-page forms, navigating web applications with complex state, and executing repeated actions without drifting from the original instruction. SWE-bench Verified scores placed Claude Opus 4.6 among the top models for autonomous software engineering tasks.

Alongside the model release, Anthropic published research from its Responsible Scaling Policy (RSP) evaluation process showing that more capable coding models could discover and demonstrate exploitation paths for serious software vulnerabilities in controlled test environments with less human guidance than previous model generations. The research reflected Anthropic’s dual-use framing: the same capabilities that make a coding agent valuable for security audits — scanning large codebases for logic errors, chaining vulnerability chains across components — reduce the expertise threshold for offensive security research. Anthropic used these findings to set deployment restrictions on vulnerability-research-adjacent uses and to update safeguards in Claude’s system prompt guidelines for API operators.

Why This Moment Mattered

The event is useful to read as a platform signal, not only as a product announcement. In the short term, it gave users and developers something concrete to react to. In the longer term, it became part of a larger pattern in artificial-intelligence, software, computing-history: hardware, software, services, and user expectations were all changing at the same time.

A good technology milestone usually matters for more than one audience. Enthusiasts notice the specifications or the interface first. Developers ask what new assumptions they can make. Companies look at cost, compatibility, and strategy. Ordinary users mostly notice whether the result makes their devices faster, easier, safer, or more useful.

The Broader Context

This period of computing was shaped by several overlapping transitions: faster networks, more capable mobile devices, cloud infrastructure, stronger security expectations, and software that changed continuously after release. Against that background, the milestone was not an isolated headline. It was one piece of a much larger movement away from static products and toward connected platforms.

That context helps explain why some announcements that looked modest at the time became important later. A browser feature, processor change, development tool, or platform policy can alter what future products are able to assume. Once enough users, developers, and vendors adapt, the new assumption becomes normal.

Looking Back

The value of revisiting the moment is that it shows how technology history is built from many medium-sized steps. Some are celebrated immediately, while others become meaningful only after the ecosystem catches up.

Looking back also keeps the story balanced. Progress usually brings tradeoffs: performance against power use, openness against consistency, convenience against control, and speed against stability. The most interesting milestones are the ones that reveal those tradeoffs clearly. This one belongs in that category because it helps explain not just what changed, but why the direction of computing kept moving the way it did.