Claude Opus 4.6 support has not been formally dropped. Anthropic’s model deprecations page still lists claude-opus-4-6 as Active and says retirement is “not sooner than February 5, 2027.”
The confusion makes more sense if you separate three different layers. API lifecycle status means Anthropic still supports a specific model ID. Recommended default means which model Anthropic wants new users to start with. Picker availability means whether that model appears in a particular product UI. Right now those layers do not line up cleanly: Anthropic documents 4.6 as active, recommends Claude Opus 4.7 as the top-end starting point, and has at least one user report in a GitHub issue saying 4.6 disappeared from a Claude Desktop model picker.
Did Anthropic actually drop Claude Opus 4.6 support?
Not based on Anthropic’s published lifecycle docs.
Anthropic’s model deprecations page is the canonical source for support status. It defines Active, Legacy, Deprecated, and Retired, and it lists claude-opus-4-6 as Active. The same page says retirement is not sooner than February 5, 2027 and that developers with active deployments get at least 60 days’ notice before retirement for publicly released models.
What Anthropic did deprecate on April 14, 2026 was claude-opus-4-20250514, not claude-opus-4-6. Anthropic’s stated replacement for that older model is claude-opus-4-7.
| Model | Anthropic status | Date noted by Anthropic | Recommended replacement |
|---|---|---|---|
claude-opus-4-6 |
Active | Retirement not sooner than Feb. 5, 2027 | None required |
claude-opus-4-20250514 |
Deprecated | Deprecated Apr. 14, 2026; retires June 15, 2026 | claude-opus-4-7 |
That naming is a real gotcha. A deprecation notice for Opus 4 is easy to misread as a deprecation notice for Opus 4.6, but Anthropic’s docs treat them differently.
Why users thought support disappeared
The strongest evidence is not a deprecation notice. It is a user report in a GitHub issue.
In issue #49689 in anthropics/claude-code, filed on April 17, 2026, a user wrote that after the April 16 launch of Opus 4.7, Opus 4.6 no longer appeared in the Code tab model picker in Claude Desktop, and that the remaining Opus option mapped to 4.7. That is verified as a user report. It is not verified as a platform-wide Anthropic change, and there is no public Anthropic confirmation in the cited material that 4.6 was removed across all surfaces.
That distinction matters. The current evidence supports at least one surface showing different behavior, not a company-wide removal of Claude Opus 4.6 support.
Anthropic’s own recommendation pages also helped create that impression. On the models overview page, Anthropic says:
“If you’re unsure which model to use, consider starting with Claude Opus 4.7”
The same page calls Opus 4.7 Anthropic’s “most capable generally available model” and says it shows a “step-change improvement in agentic coding over Claude Opus 4.6.” If you combine that recommendation with a user report in a GitHub issue that 4.6 vanished from one picker, it is easy to see why people concluded support had ended.
What Anthropic changed instead
Anthropic changed recommendations and, based on a user report in a GitHub issue, likely changed at least one product surface. That is different from ending Claude Opus 4.6 support in the API.
A compact view of the three layers looks like this:
| Model | API lifecycle status | Recommended default | UI picker availability |
|---|---|---|---|
claude-opus-4-6 |
Active on Anthropic’s deprecations page | Not the preferred starting model on current docs | User-reported missing from the Claude Desktop Code tab picker; not confirmed platform-wide |
claude-opus-4-7 |
Presented by Anthropic as current model | Anthropic says to start here if unsure | Reportedly the visible Opus choice in that same user report |
The Claude Opus product page now centers Opus 4.7. Anthropic says 4.7 is available to Claude Pro, Max, Team, and Enterprise users, and to developers through the Claude Platform and partner clouds. Its API quick start uses claude-opus-4-7.
The models overview page also tells existing users of 4.6 to “consider migrating to Claude Opus 4.7.” That is recommendation language. It is not retirement language.
Anthropic’s docs still mention 4.6 in technical capability notes. The overview says “Opus 4.7, Opus 4.6, and Sonnet 4.6 support up to 300k output tokens” in the batches API context. That is verified documentation, and it would be odd wording if Anthropic had already ended 4.6 entirely.
A separate thread added more confusion: some developers say Claude Code performance or Opus 4.6 quality feels worse than before. VentureBeat reported those complaints and said Anthropic employees denied intentionally degrading models to manage capacity. Those performance claims remain unproven in the cited reporting. The better-supported story here is narrower: support status in Anthropic’s docs does not fully match what at least one user reported seeing in a picker.
What this means for Claude users and developers
If you use the API with the explicit model ID claude-opus-4-6, Anthropic’s published docs say Claude Opus 4.6 support is still active. The lifecycle page is the source that matters most for formal status changes.
If you use Claude through product UIs, especially the Claude Desktop model picker, do not assume that “active in docs” means “visible everywhere in the UI.” The evidence so far is a user report in a GitHub issue for at least one selector, not proof of a universal removal.
A practical checklist:
- API teams: confirm whether you call
claude-opus-4-6directly or rely on a moving alias. - Product users: check which Opus models are actually selectable in your plan and client.
- Migration planning: treat Anthropic’s current docs as a push toward Claude Opus 4.7, even though 4.6 remains active.
- Benchmarking: test 4.6 and 4.7 on your own coding and agent workflows before switching production traffic.
- Change monitoring: watch Anthropic’s deprecations page for any formal Anthropic model deprecation notice tied to
claude-opus-4-6.
Anthropic has not formally ended Claude Opus 4.6 support, but its UI and recommendation changes made some users think it had.
Key Takeaways
- Anthropic’s deprecations docs list
claude-opus-4-6as Active, with retirement not sooner than February 5, 2027. - Anthropic did deprecate
claude-opus-4-20250514on April 14, 2026, and recommendsclaude-opus-4-7as the replacement. - Anthropic’s docs and product pages now position Claude Opus 4.7 as the preferred top-end model.
- The claim that 4.6 vanished from a selector comes from a user report in a GitHub issue about the Claude Desktop model picker, not from a formal Anthropic announcement.
- The verified mismatch is between API support status, recommended default, and UI availability, not a documented end to Claude Opus 4.6 support.
Further Reading
- Anthropic model deprecations, Canonical lifecycle status for Claude models, including Opus 4.6 active status and retirement guidance.
- Anthropic models overview, Canonical model recommendation page showing Opus 4.7 as the preferred top-end model.
- Anthropic Claude Opus product page, Product page positioning Opus 4.7 as Anthropic’s most capable generally available model.
- GitHub issue: Opus 4.6 removed from Code tab picker, Practitioner report that Opus 4.6 disappeared from one Claude Desktop model selector after Opus 4.7 launched.
- VentureBeat report on Claude performance complaints, Journalism summarizing user complaints, Anthropic responses, and the broader debate around perceived performance degradation.