Detailed Analysis
A Reddit thread on r/ClaudeAI has surfaced user observations that Claude Opus 4.6, labeled as "(legacy)," has reappeared in the model picker within the Claude Desktop app's Code tab. The original post includes screenshots showing the model listed as a selectable option alongside newer versions, prompting other community members to confirm they are seeing the same behavior. The reappearance struck users as unexpected, given that newer iterations of the Opus line — specifically Opus 4.7 — have since been released, making the continued visibility of a labeled-legacy model noteworthy to the user base.
The phenomenon is rooted in how Anthropic manages the Claude Desktop model picker: the dropdown is controlled server-side, meaning Anthropic can add, remove, or relabel models without requiring a client-side update from users. Claude Opus 4.6, which launched on February 5, 2026, with a 1 million token context window, has been explicitly retained on official supported model lists alongside newer releases like Sonnet 4.6 and Opus 4.7. The "(legacy)" designation likely reflects Anthropic's internal aliasing system, in which generic handles like `opus` resolve to the latest available model, while version-specific identifiers such as `claude-opus-4-6` remain accessible but are flagged to signal that a newer generation exists.
A compounding issue documented in GitHub discussions and support threads is that Claude Code exhibits a model selection bug: even when Opus 4.7 is chosen via the picker, the system sometimes serves Opus 4.6 underneath. Users have identified workarounds — including invoking the CLI directly with `claude --model claude-opus-4-7`, using the in-session `/model` command, or setting the environment variable `ANTHROPIC_MODEL` — to reliably reach the intended model. The `/status` command can be used to verify which model is actually active at runtime, helping users detect the discrepancy. These issues have been tracked in open GitHub issues on the `anthropics/claude-code` repository.
This situation reflects broader tensions in managing rapidly iterating AI model families within consumer-facing products. As Anthropic releases incremental updates to the Opus, Sonnet, and Haiku lines at an accelerating pace, legacy versioning creates surface area for user confusion, particularly when older models persist visibly in UI elements. The decision to retain explicit version numbers in the picker, rather than consolidating access behind a single rolling alias, offers power users granular control and reproducibility — valuable in coding workflows where model behavior consistency matters — but introduces the tradeoff of an increasingly cluttered interface and potential mislabeling confusion.
The broader trend this episode illustrates is the challenge of model lifecycle management as AI platforms mature. Anthropic, like other frontier labs, must balance backward compatibility for users and developers who may have workflows tuned to specific model behaviors against the communicative goal of directing users toward the best available options. The "(legacy)" label is a soft deprecation signal rather than a removal, suggesting Anthropic is threading that needle carefully. As model families grow more complex and version cadences accelerate through 2026, clearer in-product documentation, changelog surfacing, and perhaps automated migration prompts within the desktop app will likely become necessary to prevent continued community confusion of this kind.
Read original article →