“The feature I was using yesterday disappeared this morning. There was no announcement, no email.”
— Reddit, r/ClaudeAI, April 21, 2026.
>
>
https://claude.com/pricing
What This Article Covers
- The timing and exact changes of Claude Code’s disappearance from Claude Pro
- Anthropic’s official stance and actual behavior observed in the field
- The hidden context of this change (its connection to enterprise pricing plan changes)
- 4 realistic response paths for individual developers and IT instructors
- Comparison with similar cases (GitHub Copilot) and future trends
Introduction — “That $20 was for Claude Code”
On April 21, 2026, Claude Pro users worldwide experienced the same thing almost simultaneously. Entering the claude command in the terminal resulted in an authentication error, or the official documentation had been quietly updated overnight. The phrase “Using Claude Code with your Pro or Max plan” from yesterday morning had changed to “Using Claude Code with your Max plan” by this morning.
For countless individual developers, indie hackers, students, and IT instructors like myself who subscribed to the $20/month Pro plan, Claude Code was not just a “nice-to-have” feature. It was the reason they paid that $20. That agent that reads multifiles in the terminal, plans refactoring, and executes shell commands. It was gone.
Anthropic initiated this change without an official announcement, and Hacker News and GitHub issue trackers were the first to erupt. Days later, Anthropic’s Product Manager Amol Avasare posted on X, explaining that “This is a small test on ~2% of new prosumer signups. Existing Pro and Max subscribers aren’t affected.” However, the support documentation had already removed all “Pro or Max” references.
This article will summarize what happened, why it happened, and how you (and I) should proceed.
Timeline of Events — What Changed and How
April 8, 2026 — First Observation
Issue #45236 was opened on the GitHub anthropics/claude-code repository. The title was “[BUG] Breaking Change: Claude Code CLI Removed from Pro Plan Without Notice”. Certain new subscribers began receiving messages like “This plan does not support Claude Code” in the CLI despite having paid for the Pro plan.
April 10, 2026 — Clue in the Documentation
Comparing archived versions of Anthropic’s support documentation reveals that the phrase “Using Claude Code with your Pro or Max plan” was still present in the April 10 snapshot.
April 21, 2026 — Complete Change in Notation
The same support document was replaced with “Using Claude Code with your Max plan”. The indication of Claude Code inclusion for the Pro plan was also removed from the official pricing page on both mobile and desktop. At this point, Reddit, X, and Hacker News simultaneously ignited.
Same Day — Anthropic’s Explanation
Anthropic’s Amol Avasare publicly stated:
“This is a small test on ~2% of new prosumer signups. Existing Pro and Max subscribers aren’t affected.” (This is a small test targeting approximately 2% of new subscribers. Existing Pro and Max subscribers are not affected.)
Current Status: Many existing Pro subscribers reportedly can still access Claude Code via the web app and CLI. However, the official documentation and pricing page notations have already been unified to “Max plan only,” meaning that Claude Code inclusion in the Pro plan is effectively no longer a guaranteed promise.
Why Did This Happen? — Three Hidden Contexts
1. Preceding Changes in Enterprise Pricing Plans
According to The Information, Anthropic had already transitioned enterprise customers to a pay-as-you-go model based on millions of tokens (MTok) rather than a flat fee. Researchers tracking actual usage found that the previous flat-rate subscription fees were set much lower than the actual infrastructure costs. The reduction of Claude Code in the Pro plan is interpreted as the individual user version of this trend.
2. Economic Importance of Claude Code
As of 2026, Anthropic’s annualized revenue reached approximately $14 billion, with about $2.5 billion reportedly coming solely from Claude Code. This means Claude Code is no longer an add-on feature to Claude chat but an independent revenue engine, and a structure that bundles it for a near-unlimited $20 flat fee is unsustainable.
3. Industry-Wide Phenomenon
Competitor GitHub Copilot also removed the Claude Opus model from its Individual (Pro) plan around the same time, moving it to the more expensive Pro+ plan. Cursor, Codex, and others are also undergoing similar tier restructuring. This is a pervasive signal that “the era of $20 flat-rate unlimited AI coding tools is coming to an end.”
️ Response Methods — 4 Realistic Options
Depending on your usage patterns and budget, the following four paths are realistic:
Path ① Upgrade to Max Plan
This is the path officially indicated by Anthropic.
| Plan | $100/month | 5 times | Individual developers who regularly hit Pro limits |
| Max 20x | $200/month | 20 times | Full-time Claude Code users as primary work tool, utilizing Agent Teams |
– Pros: Retain existing workflow, single integrated subscription.
– Cons: Price is 5-10 times higher. Overinvestment for IT instructors who only use it for lecture demonstrations and preparation.
Path ② API Pay-as-you-go
Obtain an API key from platform.claude.com and connect it to Claude Code. Approximately $5 in free credits are provided upon new signup.
# Configure Claude Code to run with an API key
export ANTHROPIC_API_KEY="sk-ant-xxxxx"
claude| Model | Input (per MTok) | Output (per MTok) |
| Sonnet 4.6 | $3 | $15 |
| Opus 4.6/4.7 | $15 | $75 |
– Pros: If used only 2-3 times a month, it can cost less than $5. Pay only for what you use.
– Cons: Cost prediction is difficult, and the default “Extended Thinking” consumes a large number of output tokens. It is essential to set an upper limit with an environment variable like MAX_THINKING_TOKENS=8000.
Path ③ Switch to Alternative Tools
| Tool | Price | Key Strengths | Weaknesses |
| GitHub Copilot Pro | $10/month | VS Code integration, affordable | Weak terminal agent features |
| Cursor Pro | $20/month | Multi-model selection, editor integration | Lacks Agent Teams-level autonomy |
| Gemini CLI | Free (1,000 req/day) | Zero cost, easy to experiment | Weak at complex multi-file refactoring |
| Codex CLI (OpenAI) | $20/month~ | Active recent improvements | Weaker planning compared to Claude |
Path ④ Migrate to Local LLM
This incident has led to the resurgence of this faction. The performance of models running on consumer hardware has rapidly improved, and coding-specific open-source models are already at a practical level.
- Models: Llama family, Mistral, DeepSeek-Coder, Qwen-Coder, etc.
- Runtimes: Ollama, LM Studio, llama.cpp
- Editor Integrations: Continue.dev, Cline, aider, etc.
Pros: Once hardware is in place, marginal costs approach zero. Immune to subscription cancellations, feature removals, and tier changes.
Cons: Initial hardware cost (typically RTX 4090 or M-series Mac with 64GB+ RAM recommended), setup costs, and planning/agent capabilities one step below top-tier commercial models.
Realistic Strategy from an IT Instructor/Cloud Expert Perspective
For those whose primary use is lecture preparation and demonstrations, like myself, the following combination is reasonable:
- Normal Use: Maintain Pro plan + API key backup setup. If Claude Code continues to work with Pro, use it as is; if it stops, immediately switch to API by pre-registering
ANTHROPIC_API_KEY. - Intensive Project Period: Temporarily upgrade to Max 5x (monthly subscription cancellation possible).
- Lecture Demonstration Backup: Always prepare an “independent” alternative path with Gemini CLI or local Llama. If Anthropic experiences an outage during a live demo, the demonstration will fail.
- Student Guidance: From now on, do not definitively teach “Claude Pro = Claude Code.” The billing system itself should be treated as an independent topic.
⚠️ Cautions — Common Pitfalls
- Do not rely on the statement “existing subscribers are safe.” Since the documentation already states “Max only,” it could be fully implemented at any time.
- Check the default “Extended Thinking” setting when switching to an API key. If tens of thousands of thinking tokens, which are billed as output tokens, accumulate, the bill can significantly exceed expectations.
- Do not use subscription plans for CI/CD automation calls. Anthropic’s terms of service only permit interactive use for subscription plans; using them for automation can lead to account suspension. Automation must use API pay-as-you-go.
- “Access to Claude Code” is different from “sufficient usability.” Pro has a limit of approximately 44,000 tokens per 5 hours, and if Opus is used by default, it’s common for it to be exhausted in 10-15 prompts.
✅ Summary
On April 21, 2026, Claude Code quietly began to be removed from Claude Pro. Anthropic states it’s a “2% new user test,” but official documentation has already been revised to “Max only.” This is not an isolated incident but a signal of the end of the flat-rate era for AI coding tools, connected to enterprise pricing changes and GitHub Copilot’s model restructuring.
Your possible responses fall into four categories: ① Max upgrade, ② API pay-as-you-go, ③ alternative tools like Copilot, Cursor, Gemini CLI, or ④ local LLM migration. For professionals with many lectures and demonstrations, a hybrid strategy of maintaining the current Pro plan while simultaneously preparing an API key and a local backup is the safest.
“The era of solving everything with a single subscription” is over. From now on, designing a portfolio of tools for different uses is the fundamental skill for AI tool subscriptions.
Conceptual Diagram — Decision Flow for 4 Response Paths
The diagram below guides you on which path to choose based on your monthly usage frequency and budget in the current situation.
┌─────────────────────────────────┐
│ Claude Code가 필요한가? │
└────────────┬────────────────────┘
│ YES
▼
┌──────────────────────────────┐
│ 월 사용 빈도는? │
└────┬──────────┬──────────┬───┘
│ │ │
주 1~2회 거의 매일 풀타임
│ │ │
▼ ▼ ▼
┌─────────────┐ ┌─────────┐ ┌────────────┐
│ API 종량제 │ │ Max 5x │ │ Max 20x │
│ ($0~$20) │ │ ($100) │ │ ($200) │
└──────┬──────┘ └────┬────┘ └─────┬──────┘
│ │ │
└──── 예산 제약이 심하다면 ┘
│
▼
┌──────────────────────────────┐
│ 대안: Copilot / Cursor / │
│ Gemini CLI / 로컬 LLM │
└──────────────────────────────┘Structure Summary: Usage frequency is the first fork in the road, and budget constraints are the second. For users who use it 1-2 times a week, API pay-as-you-go is the cheapest option. If budget constraints are severe and autonomy requirements are low, fully migrating to Gemini CLI or local LLMs offers the most long-term freedom.
##
Leave a Reply