Skip to content
gentic.news — AI News Intelligence Platform

Listen to today's AI briefing

Daily podcast — 5 min, AI-narrated summary of top stories

Opus 4.6 Is Gone from Claude Code: What Developers Should Do Now

Opus 4.6 Is Gone from Claude Code: What Developers Should Do Now

Claude Code users must now work with Opus 4.7 exclusively, as 4.6 has been silently removed, impacting cost and workflow decisions.

Share:
Source: news.ycombinator.comvia hn_claude_code, reddit_claude, gn_claude_codeCorroborated

What Happened — The Silent Removal

Claude Opus 4.1 \ Anthropic

Anthropic has completely removed Opus 4.6 from Claude Code following the release of Opus 4.7. This wasn't a gradual phase-out—developers who had been using 4.6 after previous cache issues were suddenly left without access. The change appears to be part of broader testing around Claude Code's availability, as Anthropic has also been experimenting with removing Claude Code from the Pro plan entirely for about 2% of new prosumer signups.

This follows Anthropic's pattern of model consolidation, where older versions are deprecated quickly after new releases. Unlike some providers who maintain multiple model versions simultaneously, Anthropic is pushing users toward their latest offering.

What It Means For Your Workflow

  1. No More 4.6 in CLI: Your claude code commands now default to 4.7. If you had scripts or aliases specifying 4.6, they'll fail.
  2. Cost Implications: As noted in community discussions, Opus 4.7 comes with approximately 2-2.5x higher costs compared to 4.6 when using the API. For Claude Code users, this translates to hitting usage caps faster.
  3. Performance Trade-offs: While 4.7 offers improvements in reasoning and speed, some developers report the cost increase doesn't always justify the performance gains for routine coding tasks.

Your Options Right Now

Option 1: Adapt to 4.7

If you're sticking with Claude Code, update your workflow:

# Old (no longer works):
claude code --model claude-opus-4-6 analyze myfile.py

# New default:
claude code analyze myfile.py

# Explicit 4.7 (optional):
claude code --model claude-opus-4-7 refactor src/

Update your CLAUDE.md to reflect 4.7's capabilities. Consider adding:

## Model Context

![Claude Opus 4.6 \ Anthropic](https://www.anthropic.com/_next/image?url=https%3A%2F%2Fwww-cdn.anthropic.com%2Fimages%2F4zrzovbb%2Fwebsite%2F569d748607388e6ed42e3ff0ff245d9b0cde6878-3840x2160.png&w=3840&q=75)

- Using Claude Opus 4.7 (4.6 no longer available)
- Be aware of token costs for large refactors
- Break complex tasks into smaller steps

Option 2: Switch to API for Specific Models

If you need 4.6's cost profile for certain tasks, you can still access it via Anthropic's API:

# Example using anthropic Python client
from anthropic import Anthropic

client = Anthropic(api_key="your_key")
response = client.messages.create(
    model="claude-3-5-sonnet-20241022",  # Or other available models
    max_tokens=4096,
    messages=[{"role": "user", "content": "Review this code..."}]
)

This gives you more control but loses Claude Code's integrated workflow.

Option 3: Implement Cost Controls

Since 4.7 uses more tokens, add explicit limits to your prompts:

## Task Constraints
- Keep responses under 2000 tokens
- Suggest incremental changes rather than full rewrites
- Focus on highest-impact fixes first

Monitor your usage more closely with claude code --usage and consider setting up alerts for when you approach limits.

The Bigger Picture

This removal coincides with Anthropic testing Claude Code's removal from the Pro plan for new users. As one comment noted: "When we launched Max a year ago, it didn't include Claude Code... The way people actually use a Claude subscription has changed fundamentally."

Developers should prepare for more changes to Claude Code's availability and pricing. The days of unlimited, low-cost access to cutting-edge models for coding may be ending as usage patterns evolve.

Immediate Action Items

  1. Check your scripts: Update any that reference 4.6 specifically
  2. Review your CLAUDE.md: Add context about using 4.7
  3. Monitor usage: Watch for increased token consumption
  4. Consider alternatives: Evaluate if certain tasks should move to API or other tools
  5. Provide feedback: If the cost/performance ratio doesn't work for you, let Anthropic know through official channels

The silent removal of 4.6 signals that Anthropic is prioritizing model consolidation over backward compatibility. As a Claude Code user, your best defense is adaptability and clear communication about your needs as a developer.

Following this story?

Get a weekly digest with AI predictions, trends, and analysis — free.

AI Analysis

Claude Code users need to immediately audit their workflows for any hardcoded references to Opus 4.6. Update your CLI scripts, documentation, and mental models to work exclusively with 4.7. Adjust your prompting strategy for 4.7's cost structure. Break large refactors into smaller, focused tasks. Use the `--compact` flag more aggressively and consider implementing your own token budgeting in `CLAUDE.md`. For example, add "Keep explanations concise" and "Prioritize code over commentary" to reduce token usage. Explore hybrid approaches: use Claude Code for interactive debugging and exploration, but switch to the API with specific models for batch processing or cost-sensitive tasks. The removal of 4.6 makes model choice less flexible within Claude Code itself, so you may need to maintain separate workflows for different types of coding tasks.
Enjoyed this article?
Share:

Related Articles

More in Products & Launches

View all