Updated June 12, 2026: Added Claude Fable 5 — Anthropic’s new top-tier model released June 9, 2026 at $10/$50 per million tokens.
Claude AI pricing changed significantly in mid-2026. Claude Fable 5 launched June 9 as the new most-capable model — above Opus 4.8 in the lineup at $10 input / $50 output per million tokens. The Team Premium tier and Enterprise self-serve path arrived earlier in the year. This guide covers every plan, every model, and every cost as of June 12, 2026 — verified directly from claude.com/pricing.
Individual Plans: Free, Pro, and Max
Individual plans — Free, Pro, Max.
Claude offers three individual tiers. The Free plan costs nothing and gives you access to chat on web, iOS, Android, and desktop. You get web search, memory across conversations, file creation with code execution, desktop extensions, and the ability to connect Slack and Google Workspace services through connectors. Free users can access extended thinking for complex work and use remote MCP integrations. The limitation is usage volume — you hit rate limits faster than paid users.
The Pro plan costs $20 per month billed monthly or $17 per month with an annual subscription ($200 billed upfront). Pro includes everything in Free plus significantly more usage, access to Claude Code and Claude Cowork, unlimited Projects for organizing chats and documents, Research mode, access to additional Claude models, and Claude for Microsoft 365 and Outlook.
The Max plan starts at $100 per month and offers two tiers: $100/month for approximately 5x more usage than Pro, or $200/month for approximately 20x more usage than Pro. Max users get higher output limits for all tasks, early access to advanced Claude features, and priority access during high-traffic periods.
Team Plan: Standard and Premium Seats
Team plan — standard and premium seats.
The Team plan serves groups of 5 to 150 users and comes in two seat types. Standard seats cost $25 per seat per month billed monthly or $20 per seat per month billed annually. Standard seats include all Claude features plus more usage than Pro. Premium seats cost $125 per seat per month billed monthly or $100 per seat per month billed annually, offering 5x more usage than standard seats.
Team plans include Claude Code and Claude Cowork, Microsoft 365 and Slack integrations, Enterprise search across the organization, central billing and administration, single sign-on (SSO), admin controls for connectors, enterprise desktop app deployment, and the ability to mix and match seat types. Content is not used for model training by default on Team plans.
Enterprise Plan: Self-Serve and Sales-Assisted
Enterprise pricing follows a seat-plus-usage model: $20 per seat with usage billed at API rates that scale with model and task. Anthropic now offers two Enterprise paths: a self-serve option where organizations can sign up at claude.ai/create/enterprise without contacting sales, and a traditional sales-assisted path for organizations needing custom contracts, MSAs, purchase orders, or usage commitments.
Enterprise includes everything in Team plus admin-set user and org spend limits, role-based access with fine-grained permissioning, SCIM, audit logs, compliance API, custom data retention controls, network-level access control, IP allowlisting, HIPAA-ready offerings, and Claude Security (currently in beta). As of June 2026, Anthropic is running a promotion: $1,000 in Claude Code and Claude Cowork credits for every seat activated by July 2.
API Pricing: Per-Token Costs for Every Model
API per-token costs — stale-proof shapes.
All API prices are per million tokens (MTok). Current models as of June 2026:
Fable 5 (New — June 9, 2026)
Input: $10/MTok. Output: $50/MTok. Prompt caching write: $12.50/MTok. Prompt caching read: $1.00/MTok. Fable 5 is Anthropic’s first Mythos-class model released for general availability — the highest-capability Claude model as of June 2026. It supports a 1M token context window with 128K max output and adaptive thinking always on. Two important constraints: (1) mandatory 30-day data retention (zero data retention not available), and (2) safety classifiers route certain domain prompts (cybersecurity, biology, chemistry, distillation) to an Opus 4.8 fallback at Fable 5 API rates. Full Fable 5 breakdown →
Opus 4.8
Input: $5/MTok. Output: $25/MTok. Prompt caching write: $6.25/MTok. Prompt caching read: $0.50/MTok. Opus 4.8 is Anthropic’s most intelligent model, optimized for agents and coding. It supports a 1M token context window with flat-rate pricing — no surcharge for long contexts.
Sonnet 4.6
Input: $3/MTok. Output: $15/MTok. Prompt caching write: $3.75/MTok. Prompt caching read: $0.30/MTok. Sonnet 4.6 balances intelligence, cost, and speed. It also supports a 1M token context window at flat rates.
Haiku 4.5
Input: $1/MTok. Output: $5/MTok. Prompt caching write: $1.25/MTok. Prompt caching read: $0.10/MTok. Haiku 4.5 is the fastest and most cost-efficient model with a 200K token context window.
Cost Optimization Features
Batch processing saves 50% on all token rates for asynchronous workloads. Prompt caching reduces repeated context costs by up to 90% — cached reads cost roughly 10% of standard input rates. Combining both strategies can reduce costs by up to 95%. US-only inference is available at 1.1x standard pricing for workloads requiring data residency. Fast mode for Opus 4.8 runs at 2x standard pricing with up to 2.5x faster speeds.
Platform Feature Pricing
Managed Agents cost $0.08 per session-hour for active runtime, plus standard token rates. Web search costs $10 per 1,000 searches (not including input/output tokens for processing). Code execution includes 50 free hours daily per organization, with additional hours at $0.05 per container-hour.
Legacy Model Pricing
Opus 4.7 and Opus 4.6 retain the same $5/$25 per MTok pricing as Opus 4.8. Sonnet 4.5 and Sonnet 4 maintain $3/$15. The older Opus 4.1 and Opus 4 remain at their higher legacy rates of $15/$75 per MTok — making the current-generation Opus models 66.7% cheaper than their predecessors for the same token volume.
Frequently Asked Questions
How much does Claude AI cost?
Claude AI is free to use with usage limits. The Pro plan costs $20/month ($17/month annual), Max starts at $100/month, Team starts at $20/seat/month (annual), and Enterprise is $20/seat plus usage at API rates.
Is Claude AI free?
Yes. Claude offers a permanent free tier with access to chat, web search, memory, code execution, desktop extensions, and extended thinking. The free plan has lower usage limits than paid plans.
What is the most capable Claude API model?
Claude Fable 5, released June 9, 2026. API ID: claude-fable-5. Priced at $10 input / $50 output per million tokens — 2x the cost of Opus 4.8. It scores significantly higher than Opus 4.8 on SWE-bench (80% vs 69.2% on Pro) and the Senior Engineer benchmark (91 vs ~63 out of 100). Use Fable 5 for complex engineering tasks and long-horizon agentic work where quality justifies the cost.
What is the cheapest Claude API model?
Haiku 4.5 at $1/MTok input and $5/MTok output. With batch processing (50% off) and prompt caching (90% off reads), effective costs can drop below $0.10/MTok for cached inputs.
Does Claude offer a student discount?
Anthropic does not offer an individual student discount as of June 2026. However, they have an Education plan for universities that provides comprehensive institution-wide access at discounted rates for students, faculty, and staff.
What is the difference between Claude Pro and Claude Max?
Pro costs $20/month and provides a standard amount of usage. Max costs $100/month (5x usage) or $200/month (20x usage) and adds higher output limits, early access to features, and priority access during peak times.
Ready to build with Claude?
Claude Seed Kits give you a pre-configured skill file, 20 tested prompts, and a setup guide tailored to your use case. Install in minutes and start getting real output immediately — $47 each.
All fall, Microsoft has been selling one idea: the future is the AI PC — a Copilot+ machine with a dedicated neural chip (an NPU), Recall, Click to Do, a thousand dollars and up, and your old laptop need not apply.
I had a $400 budget laptop on my desk — an AMD Ryzen 5 7520U, 16 GB of RAM, no NPU — and a hunch that the whole framing was backwards. The AI-first laptop was never about the chip. It’s about architecture.
A few hours later, that $400 laptop had a private AI brain, voice control, and a control panel I run from my phone. On the things that actually matter for operating a machine, it does more than the Copilot+ PC it’s supposedly too cheap to be. Here’s the exact build.
The thesis: AI-first is architecture, not a chip
AI-first is architecture, not a chip.
The trick is to stop asking your laptop to be the supercomputer. Split the job:
The brain lives in the cloud. The heavy reasoning runs on a frontier model (I use Claude) with effectively unlimited horsepower. No NPU on Earth competes with that.
The body lives on your laptop. Your machine becomes the always-on hands: it holds your private data, runs small models locally for anything sensitive, and executes the actions the brain decides on.
An NPU optimizes a handful of on-device Windows features. Architecture gives you an actual operator. Guess which one you feel every day.
Step 0 — Make it always-on
An operator rig is a little server, and servers don’t nap. My laptop kept sleeping and killing background jobs, so the first move was to take that off the table (while plugged in):
Screen never blanks, never sleeps, and it keeps running with the lid closed — while still sleeping on battery as a safety. Now it’s a real always-on host.
Step 1 — A private AI brain that lives on the laptop
A private AI brain that lives on the laptop.
The local engine is Ollama; the chat interface is open-webui (running in Docker). If you want the multi-agent version of this idea, I’ve also written up building a free AI agent army with Ollama and Claude. The only thing standing between me and a private, offline ChatGPT was one wrong setting — open-webui was pointed at a dead address. The fix was to aim it at the host:
The proof: a 3-billion-parameter model (Llama 3.2) introduced itself in about 10 seconds at ~12 tokens/second — on the CPU, no NPU, no discrete GPU. Fast enough for real Q&A, drafting, and summaries. Seven models sit ready on disk, and the whole thing is reachable from my phone over a private network.
Everything here runs offline. For anything I don’t want leaving the machine, that’s the entire point.
Step 2 — Voice that never leaves the machine
Voice that never leaves the machine.
A local Whisper speech-to-text container (OpenAI-compatible API) became a push-to-talk dictation tool: hold a key, talk, release, and the text drops into whatever app is focused. I verified the pipeline without even touching the mic — Windows text-to-speech generated a clip, the local Whisper transcribed it, and it round-tripped clean:
Spoken: “Testing one two three. This is the private local transcription engine.” Whisper heard: “Testing 1-2-3. This is the private local transcription engine.”
Windows has built-in dictation (Win+H) and Copilot voice too — but those ship your audio to the cloud. The local version does the same job, and your voice never leaves the laptop.
Step 3 — Turn your phone into the control panel
Using Tailscale (a private mesh network), every service on the laptop is reachable from my phone — without exposing anything to the public internet. I added a tiny web page (one small nginx container) as a mobile operator console: one tap to the local AI, automations, status, and finance dashboards. Pin it to the home screen and the laptop is in your pocket.
The honest scoreboard vs. a Copilot+ PC
Capability
Copilot+ PC ($1,000+)
This $400 laptop
Private AI running on the device
Limited (small NPU models)
✅ Full Ollama stack, 7 models
An AI that operates the machine
❌
✅ Runs commands, edits files, fixes things
Private, offline voice dictation
❌ (cloud)
✅ Local Whisper
Phone control panel
❌
✅ Tailscale operator console
Recall / Click to Do / Cocreator
✅ (needs the NPU)
❌
Screenshots everything you do
⚠️ Recall does, by design
✅ No — nothing is recorded
I’m being fair: the NPU-only features are genuinely off the table on cheap hardware. But for operating your computer — and for privacy — the architecture beats the chip.
Why this matters more than it looks
The quiet headline isn’t “I saved money.” It’s where the data lives. Microsoft’s flagship AI-PC feature, Recall, works by screenshotting everything you do. This build does the opposite: the sensitive payload stays on your machine, and the cloud is used only for the heavy thinking that doesn’t need your private files.
That’s not just a hobbyist’s preference. It’s the exact requirement for anyone in a regulated field — healthcare, legal, finance — who can’t send client data to a third party but still wants real AI leverage. The cheap laptop isn’t the story. The architecture is.
Frequently asked questions
Do I need a Copilot+ PC or an NPU to run local AI?
No. Any laptop with around 16 GB of RAM and a modern CPU can run small local models. An NPU accelerates certain Windows features but is not required for Ollama or local chat.
Is local AI actually private?
Yes. With Ollama, the model runs on your own machine and works with no internet connection — nothing is sent to a cloud service.
What is the difference between Ollama and open-webui?
Ollama is the engine that runs the models. open-webui is the friendly chat interface that sits in front of it.
How fast is a local model on a budget laptop?
On a CPU-only AMD Ryzen 5 with 16 GB of RAM, a 3-billion-parameter model answered at roughly 12 tokens per second — fine for quick questions, drafting, and summaries. Larger models run slower.
Can I use it from my phone?
Yes. Over a private Tailscale network you can reach your laptop’s AI and tools from your phone without exposing anything to the public internet.
Is this better than a Copilot+ PC?
For operating your machine and for privacy, this setup does more. For NPU-specific Windows features like Recall and Click to Do, a Copilot+ PC is required.
Want this on your machine?
Tygart Media builds privacy-first, local-AI operator setups — especially for teams in regulated industries that need real AI leverage without sending data to the cloud. Reach out and we’ll scope it to your hardware.
The short version: In Claude Code, the prompt that asks whether to “Always Allow” or “Allow Once” isn’t really about security. It’s a question about your own systems. If you keep choosing Always Allow, the work is recurring — go build the automaton. If it’s honestly Allow Once, it’s a one-off — let it go instead of trying to remember it.
I spend most of my day inside Claude Code, and a tiny piece of the interface has been living rent-free in my head. Every time the agent wants to run a command, edit a file, or hit an API, it stops and asks: Always Allow, or Allow Once?
On the surface that’s a permission prompt. Click the box, move on. But after the hundredth time, I started to notice the choice was telling me something about how I actually work — and where I was leaving time on the table.
“Always Allow” means: go build the automaton
Always Allow means: go build the automaton.
Always Allow vs Allow Once: quick reference
Always Allow vs Allow Once — quick reference.
Signal
Always Allow
Allow Once
Task type
Recurring, repeating work
One-off, situational
Right response
Build an automation
Let it go — don’t memorize it
Security posture
Persistent permission for that tool+action
Single-use, no persistent grant
What it reveals
A system worth building
An edge case not worth systemizing
Risk if overused
Broad standing permissions accumulate
Missed automation opportunity
Here’s the pattern. If I find myself reaching for Always Allow, it’s because I’ve seen this exact action before. I’ll see it again. I trust it enough to stop being asked.
That’s not a permission decision. That’s a build order.
If an action is safe, repeatable, and I do it constantly, the right move isn’t to keep approving it forever — it’s to take it out of the prompt entirely. Turn it into a tool. Wrap it in a script. Register it as a skill. Put it on a cron so it runs whether I’m at the desk or not. The “Always Allow” click is the moment the work earns its own piece of infrastructure.
Most people stop at the click. They grant the permission and feel productive because the friction went away. But friction that shows up every single day isn’t friction you should approve — it’s friction you should engineer out. Every “Always Allow” is a quiet little flag waving at you: this deserves to be an automaton.
“Allow Once” means: let it go on purpose
The other side is just as useful, and it’s the part people get wrong.
When the honest answer is Allow Once — this is a weird one-off, I’m not going to do it again — the temptation is to write it down. Save the command. Add it to a doc. File it away just in case it ever comes back.
Resist that. A one-off doesn’t deserve a permanent home in your memory or your system. The cost of storing it isn’t the disk space — it’s the upkeep. Every note you keep is something you now have to organize, search past, keep current, and trip over later. Knowledge you save but rarely touch quietly rots, and stale knowledge is worse than none.
The way I think about it: it’s more fit to sift through the dirt than to re-sift the knowledge. If a one-off ever does come back, re-deriving it from scratch is cheap — you dig through the dirt once and you’re done. But re-sifting a giant pile of “just in case” notes, over and over, every time you go looking for the thing you actually need? That’s the expensive part. Forgetting a one-off on purpose is a feature, not a failure.
Why re-deriving usually beats remembering
This is really a question of economics, and it’s the same math whether you’re managing an AI agent or your own head.
Storing knowledge has two costs people forget about: the cost to keep it accurate, and the cost to find the signal inside it later. A one-off has a low chance of ever being needed again, so the expected payoff of saving it is tiny — while the drag it adds to everything else you’ve stored is real and permanent. Recurring work is the opposite: high chance of reuse, so it’s worth paying once to encode it well and never think about it again.
So the rule of thumb falls out on its own:
Recurring → encode it. Build the tool, the skill, the cron. Pay once, reuse forever.
One-off → forget it on purpose. Do the thing, then let it go. If it ever comes back, dig it up fresh — it’ll be faster than you think.
The mistake is doing it backwards: hand-running the recurring stuff every day because you never built the automaton, while hoarding a graveyard of one-off notes you’ll never open again. That’s how you end up busy and buried at the same time.
How to act on the tell in Claude Code
How to act on the tell in Claude Code.
Next time that prompt pops up, treat it as a tiny decision point instead of a speed bump:
You reached for “Always Allow.” Stop for a second. Ask: what would it take to make this prompt never appear again? An orchestration step, a saved skill, a scheduled job, a hook? Put it on the list. The prompt just told you what to build next.
You reached for “Allow Once.” Do it, then genuinely drop it. Don’t screenshot it, don’t file it. Trust that if it matters, it’ll show up again — and the second sighting is your real signal to build.
You’re not sure. That’s fine — “Allow Once” is the safe default. Two or three “Allow Once” clicks for the same action is the universe telling you it was an “Always Allow” the whole time.
None of this is really about Claude Code. The tool just happens to put the decision right in front of you, every day, in a little box. Most systems make you guess where your time is leaking. This one points at it and asks you to choose. (It pairs well with knowing when to use Plan Mode and when to skip it — same instinct, a different prompt.)
Recurring work wants to become an automaton. One-off work wants to be forgotten. The prompt already knows which is which. The only question is whether you’re listening.
Frequently asked questions
What’s the difference between “Always Allow” and “Allow Once” in Claude Code?
“Allow Once” approves a single action one time; the next identical action prompts you again. “Always Allow” approves that action or pattern going forward, so Claude Code stops asking. Functionally, “Always Allow” is how you tell the tool an action is safe and routine.
Should I use “Always Allow” in Claude Code?
Use it when an action is safe, repeatable, and something you do often — but treat each “Always Allow” as a signal to eventually build that action into a tool, skill, hook, or scheduled job so it leaves the prompt entirely.
Is “Always Allow” a security risk?
It can be if you grant it to broad or destructive actions. Keep “Always Allow” for narrow, well-understood operations, and lean on “Allow Once” for anything unfamiliar, destructive, or outward-facing.
When should I turn a Claude Code action into an automation?
When you’ve granted — or wanted to grant — “Always Allow” for it. That’s the tell that the work is recurring, and recurring, trusted work is worth encoding once as a tool, skill, hook, or cron so you never approve it by hand again.
Why shouldn’t I save one-off commands?
Because storing knowledge has ongoing costs — keeping it accurate, and sifting past it to find what you actually need. A one-off has little chance of reuse, so it’s usually cheaper to re-derive it later than to maintain it forever.
What does “more fit to sift through the dirt than to re-sift the knowledge” mean?
It means re-deriving a rarely-needed answer from scratch — sifting the dirt once — is cheaper than maintaining and repeatedly searching a hoard of saved notes, which is re-sifting the knowledge every time. For one-offs, forgetting is the efficient choice.
Frequently Asked Questions
What does ‘Always Allow’ mean in Claude Code?
When Claude Code asks to run a tool or shell command, ‘Always Allow’ grants a persistent permission for that specific tool and action combination. Claude will not ask again for that combination in future sessions. ‘Allow Once’ grants permission only for the current request — Claude will ask again next time.
Is it safe to click Always Allow in Claude Code?
It depends on the action. Always Allow for read operations (reading files, querying a database) is generally low risk. Always Allow for write or execute operations (editing files, running shell commands) creates persistent permissions that compound over time. The best practice is to use Always Allow deliberately for actions you will genuinely repeat, and Allow Once for anything new or situational.
What is the deeper meaning of Always Allow vs Allow Once?
The choice is a signal about your own workflow. If you keep clicking Always Allow for the same action, that’s the system telling you the task is recurring and worth automating. If it’s genuinely Allow Once, the task is a one-off and you shouldn’t try to systemize it. The prompt is less about security and more about recognizing patterns in your own work.
How do I review or remove Always Allow permissions in Claude Code?
Run ‘claude permissions list’ to see what standing permissions you’ve granted. Use ‘claude permissions reset’ to clear them, or edit the .claude/settings.json file in your project directory to remove specific entries. Review these periodically — accumulated Always Allow grants are a common source of unexpected autonomous behavior.
Does Always Allow apply to a specific project or globally?
By default, permissions granted with Always Allow are scoped to the project where you granted them (stored in .claude/settings.json). If you use the –global flag, they apply across all projects. Be cautious with global Always Allow grants for write/execute operations — they persist across every codebase you open.
Most of what a working AI system does happens in silence. The operator sees the output. The operator does not see the labor. The labor — the prompts that ran, the data that was queried, the small decisions made hundreds of times across a session, the loops that were entered and exited — happens in a quiet room the operator usually does not enter.
There is a small but important practice in periodically going to the quiet room and watching the work happen.
Why most operators don’t do this
The quiet room is dull. The labor is repetitive. Watching the system work is much less satisfying than reviewing the system’s output. The dashboard is the highlight reel; the quiet room is the practice. Most operators, given the choice, watch the highlight reel.
This is reasonable in the short term. It is dangerous in the long term. The operator who only ever sees the output develops an intuition for the output and no intuition for the labor. When the output is wrong, the operator who has been watching the labor knows which step to look at. The operator who has been watching only the output is stuck.
What the quiet room teaches
It teaches the texture of the system’s reasoning. Where the system pauses. Where it overcommits. Which kinds of inputs produce which kinds of paths. What looks like efficiency is actually default behavior versus actual judgment.
It teaches what the system does badly. Every working system has a set of small recurring inefficiencies — wasted lookups, redundant verifications, paths that loop slightly more than necessary. Most of these are invisible from the output. They are visible from the labor. Watching them gives the operator a real sense of what to optimize and what to leave alone.
It teaches when to trust. The operator who has spent time in the quiet room has a calibrated sense of where the system is reliable and where it is reaching beyond its competence. That calibration is not in the output. It is only in watching the work.
The practice
The practice is small. Once a week, instead of reviewing only the output, spend twenty minutes in the labor. Read the trace of a session that produced something. Watch the prompts the system used, the tools it called, the decisions it made about which path to take. Note where the labor surprised you — positively or negatively. Update the working model.
This is unglamorous. It does not produce anything. It does not show up in the dashboard. It is a deposit in an account the operator will draw on six months from now when something does not look right and the operator has to decide whether to trust the system’s read.
The closing read
The output is the public face of the system. The quiet room is where the system is actually built. The operator who knows only the public face will, eventually, be surprised by the system. The operator who has been to the quiet room periodically — even briefly, even unsystematically — will not be. That is most of what calibration is. There is no shortcut for the labor of watching the labor.
The Architecture of Delegation: Moving Beyond the Chat Interface
The architecture of delegation — beyond the chat interface.
I spent today wiring Claude Code to boss around the Gemini CLI, clearing a 1,256-post WordPress tagging backlog without a single hallucinated tag. If you operate an agency or manage technical strategy at any reasonable scale, you already know the fundamental truth about current AI tools: the chat interface is a massive bottleneck. Copying, pasting, and waiting for a typing animation isn’t a workflow; it’s theater. Real, scalable throughput requires system-to-system communication and architectural delegation.
The goal for today wasn’t just to write a python script. The goal was to establish a functional hierarchy between two distinct AI systems operating locally on my machine. Claude Code, operating directly in my terminal, would act as the lead engineer and orchestrator. It would handle the logic, map out the API calls, write the Python bridges, and manage the error handling. Gemini, accessed via its official command-line interface, would act as the high-context, high-throughput worker.
The setup was brutally simple but effective. I installed the Gemini CLI using a standard node package manager command (npm install -g @google/gemini-cli) and authenticated it with a Google One AI Ultra account. This gave my local environment direct, command-line access to Google’s most capable models without needing to manage raw API keys or custom curl requests. From there, Claude Code was instructed to shell out via bash, calling the gemini command non-interactively to pass massive data payloads for processing, and then ingesting the structured output back into the orchestration pipeline.
It is an assembly line in the truest sense. Claude builds the machinery and defines the parameters; Gemini operates the heavy press, stamping out classifications at a volume that would break a standard chat context window.
Quantifying the Backlog and the Taxonomy Threat
Before you throw compute at a problem, you have to measure it accurately. I directed Claude to run a full audit of tygartmedia.com using the native WordPress REST API. The numbers came back clean, but the scale of the maintenance debt was daunting.
Total published posts: 2,529 individual pieces of content.
SEO infrastructure: RankMath confirmed healthy and active across the board.
Existing tag vocabulary: 931 distinct, strategically established tags.
The deficit: 1,256 posts sitting entirely untagged, orphaned from the site’s primary taxonomy.
In the past, solving this was a lose-lose proposition. It was either a job for a junior employee spending three agonizing weeks in the wp-admin panel, or it was a job for a messy automated script that inevitably hallucinates a thousand new, slightly misspelled tags. When you let an LLM tag 1,256 posts without strict, physical constraints, you don’t get an organized site. You get “Marketing”, “marketing”, “digital-marketing”, and “Digital Marketing Strategy” added as four completely separate taxonomy terms, permanently bloating your wp_terms table and diluting your internal link equity.
The constraint I set for this pipeline was absolute. The system had to read the 1,256 untagged posts, assign 5 to 8 highly relevant tags to each post, and only use tags from the exact 931-item vocabulary we already had. Zero deviation. Zero hallucination. If a perfect tag didn’t exist in the vocabulary, the system had to settle for the closest existing match rather than inventing a new one.
The Pilot Test and the Strict JSON Constraint
We started small to validate the pipeline. Claude pulled a pilot batch of 10 untagged posts from the WordPress API, along with the complete, raw list of 931 acceptable tags. It packaged this massive block of text into a single, dense prompt and fired it over to the Gemini CLI.
The instruction was clear and unforgiving: read the text of the posts, evaluate them against the vocabulary, and return ONLY a valid JSON object. I did not want markdown formatting. I did not want a polite introductory sentence. I needed a raw JSON string mapping each specific post_id to an array of its assigned tag IDs.
If you’ve spent any significant time wrestling with large language models, you know that asking for strict adherence to a vocabulary and strict, unformatted JSON output is exactly where things usually break down. Models inherently want to chat. They want to explain their reasoning. They want to invent a 932nd tag because it felt slightly more semantically accurate for a specific paragraph.
Gemini didn’t flinch. It processed the prompt and returned a raw, perfectly formatted JSON string directly to the standard output. Claude parsed it in memory, validated the suggested tags against the local vocabulary list, and found a 100% match rate. Every single tag suggested by Gemini was real. There was no conversational filler, no missing structural brackets, and no invented taxonomy. Claude immediately took that JSON, formatted the correct POST requests, and pushed the updates back to WordPress via the REST API.
Scaling Up: Hitting the Windows Bottlenecks
With the pilot completely successful, it was time to scale. Processing 1,256 posts one by one is inefficient, both in terms of time and system calls. We grouped the remaining posts into chunks of 25. This meant Claude would need to loop through roughly 50 distinct batches. For each batch, it would dynamically construct the prompt with the 931 tags and the 25 new post payloads, call Gemini, parse the resulting JSON, and patch the WordPress database.
That is where the friction started. Building a local orchestration pipeline means you are no longer just dealing with AI limitations; you are dealing with local OS limits. Windows had two specific, technical walls waiting for us.
Failure 1: WinError 2 (File Not Found)
The initial Python orchestration script used the standard subprocess.run(['gemini', '-p', prompt]) command to invoke the CLI. It failed almost immediately with a WinError 2. The issue? When npm installs global packages on a Windows machine, it doesn’t create a raw binary; it creates a .cmd wrapper. Python’s subprocess module doesn’t automatically resolve these wrappers unless you pass shell=True, which introduces a host of security and string parsing headaches. The clean, robust fix was forcing Claude to locate the executable and use the absolute, fully qualified path to gemini.cmd in the subprocess call. It’s a minor detail, but one that breaks entire automation pipelines if you don’t know what you’re looking at.
Failure 2: “The command line is too long”
Once the executable actually resolved, the script crashed again on the very first batch. Windows threw a fatal error: “The command line is too long.” Windows enforces a strict character limit on command-line arguments—roughly 8,191 characters depending on the exact environment. Our dynamically generated prompt, containing the full text of 25 blog posts and 931 taxonomy terms, hovered around 20KB. Trying to pass that payload via the standard -p argument flag was physically impossible for the operating system to handle.
The solution was architectural. Instead of trying to cram the prompt into an argument, Claude rewrote the Python script to pipe the prompt directly into Gemini’s standard input (stdin). By restructuring the workflow to write the 20KB payload to a temporary text file on disk, and then piping it via a standard input redirect (gemini < prompt.txt), we bypassed the OS argument limit entirely. The data flowed, and the pipeline spun back up to full speed.
The Verdict: The Orchestrator vs. The Worker
The orchestrator vs the worker.
Watching this script hum through 50 consecutive batches crystalized a specific, actionable opinion about the current state of local agentic workflows. You do not need one god-model to do everything; you need specialized roles operating within a hierarchy.
Claude Code is unmatched as an orchestrator. It understands the local filesystem, it navigates REST API documentation with ease, it writes robust, defensive Python, and it can dynamically debug Windows-specific OS errors on the fly. But using Claude for the repetitive, high-volume, token-heavy classification of thousands of posts is an expensive and slow use of a strategic brain. It is the equivalent of having your lead architect nailing drywall.
Gemini, operating locally via its CLI, proved to be the ultimate high-throughput worker. It absorbed the massive context window of 931 tags and 25 full articles simultaneously, over and over again, without degrading in quality. It maintained absolute discipline over the JSON output structure across 50 separate invocations. It didn’t need to understand how the WordPress API worked, and it didn’t need to know how to write Python. It only needed to process the classification task it was handed and get out of the way.
When Gemini acts as the worker and Claude acts as the boss, you get the absolute best of both architectures. You get the system-level problem-solving and environmental awareness of Claude, combined with the raw, reliable, high-context processing power of Gemini.
Tomorrow’s Takeaway
Tomorrow’s takeaway.
If you operate an agency and have a massive backlog of unstructured data—whether it is untagged content, uncategorized financial transactions, or messy CRM records—stop trying to fix it manually inside a browser window. The chat interface is dead for real, scalable work.
Tomorrow, install an agentic CLI like Claude Code. Give it access to a high-context execution model via a secondary CLI, like Gemini. Tell the orchestrator to write a local script that batches your data, hands the batches to the execution model, forces a strict, structured JSON return, and posts the results directly back to your database or CMS. Expect the script to break on local OS limits. Fix the pipes, use standard input instead of arguments for massive payloads, and let the machines clear the backlog while you focus on actual strategy.
Every automated system has a cognitive budget. When you are building an AI agency or managing a large-scale content pipeline, that budget is measured in two ways: the literal dollar cost of API credits and the “judgment tokens” spent on complex reasoning. Claude, specifically the 3.x and 4.x Sonnet and Opus series, currently holds the crown for high-judgment work. It understands nuance, follows complex instructions, and writes with a cadence that feels human. But it is also a resource you have to husband carefully.
The most expensive mistake an operator can make is burning Claude’s judgment tokens on labor that requires zero creativity. If a task involves a fixed vocabulary, a strict JSON schema, and a predictable input-output loop, you don’t need a poet; you need a foreman to watch a crew of laborers. In my current architecture, Claude is the Foreman—the one who decides the strategy and handles the edge cases—while Gemini serves as the Crew. This isn’t just about saving a few dollars on a Tuesday; it’s about architectural resilience and maximizing the throughput of your most capable models.
Yesterday, I detailed the orchestration pattern that allows these two models to talk to each other. Today, I want to look at the raw numbers and the operational rationale behind why my best Claude work actually runs on Gemini hardware. When you stop treating LLMs as a single-vendor solution and start treating them as tiered compute, the math of your business changes overnight.
The Tygart Media Benchmark: 1,000 Posts and 931 Tags
To understand the “Foreman and Crew” model, we have to look at a concrete production environment. We recently moved over 1,000 legacy posts for Tygart Media through a full metadata audit. This wasn’t a “write a summary” task. This was a “categorize these posts using only these 931 specific tags” task. This is what we call a bounded subtask. The model cannot invent new tags. It cannot be “creative.” It must map unstructured text to a strictly defined vocabulary.
Running this through Claude Opus or even Sonnet 3.5 is technically superior in terms of accuracy, but the cost-to-benefit ratio is skewed. Gemini, particularly when accessed through a Google One AI Premium subscription, allows for a “marginal zero” cost structure for high-volume, bounded tasks. We processed 50 batches, involving approximately 300,000 input tokens and 25,000 output tokens. Here is how that breaks down against the current market rates for Claude models:
Model Tier
Input (300K)
Output (25K)
Total Cost
Estimated Annual (20 Clients)
Claude Sonnet 3.5 ($3/$15)
$0.90
$0.38
$1.28
$307.20
Claude Opus ($15/$75)
$4.50
$1.88
$6.38
$1,531.20
Gemini (AI Ultra Subscription)
$0.00*
$0.00*
$0.00
$0.00
*Cost is covered by the existing $19.99/mo subscription already used for storage and workspace tools.
A $6 saving in a single day is a rounding error. But scale that across 20 client sites on a monthly cadence, and you are looking at $1,500 a year in reclaimed margin. More importantly, you are preserving Claude’s rate limits for the tasks Gemini cannot do—like the actual synthesis of the articles or the high-level strategy decisions that Claude 3.5 handles with far more grace.
Defining the Bounded Subtask
Defining the bounded subtask.
The success of this model hinges on knowing where the Foreman ends and the Crew begins. You cannot simply ask Gemini to “write like Claude.” It won’t. Gemini’s prose style often leans toward the repetitive or the overly structured. However, Gemini excels at what I call Bounded Subtasks. These are tasks where the “walls” of the output are clearly defined.
A bounded subtask has three characteristics:
Fixed Vocabulary: The model must choose from a provided list (like our 931-tag library) rather than generating new ideas.
Structural Rigidity: The output must be valid JSON or a specific markdown format. Gemini is exceptionally good at following “System Instructions” that demand valid code blocks.
Low Context Sensitivity: The task doesn’t require “remembering” what happened three articles ago. It only needs the text in front of it and the rules provided.
By routing these specific “labor” tasks to Gemini, we ensure that zero hallucinations occur. When you give Gemini 931 tags and tell it “only use these,” its adherence to those boundaries is remarkably stable. In our Tygart Media run of 1,000 posts, we saw zero instances of the model inventing a tag that wasn’t in the provided schema. That is the “Crew” doing exactly what they were told, while the “Foreman” (Claude) is free to handle the complex orchestration logic in the background.
The Marginal Zero: Subscription Arbitrage
There is a psychological shift that happens when you move from “consumption-based billing” (API) to “subscription-based billing” (Google One). When you are paying by the token, every experiment feels like a withdrawal from a bank account. You hesitate to run a second pass. You skip the extra validation step to save $0.15.
When you use Gemini through the AI Ultra subscription (routed through a local bridge or automated CLI), the marginal cost of the next 100,000 tokens is zero. This changes the way you build. You can afford to be “wasteful” with tokens to ensure quality. You can run three different prompts on the same text and have the Foreman (Claude) pick the best one. This “Subscription Arbitrage” is the secret weapon of the independent operator. You are already paying for the Google storage and the workspace; why not use the compute that comes bundled with it to handle your data processing?
This doesn’t mean Gemini is “better” than Claude. It means Gemini is “cheaper labor” for the specific tasks where its performance is “good enough.” In engineering, “good enough” at zero marginal cost is almost always superior to “perfect” at a premium.
Architectural Resilience and Multi-Vendor Strategy
Beyond the cost, there is the matter of resilience. If your entire agency or software stack is built on a single LLM provider, you are not a business; you are a feature of that provider. Rate limits, outages, or sudden changes in model weights can break your pipeline in an afternoon.
By splitting the workload between Claude (Foreman) and Gemini (Crew), you build a multi-vendor layer into your architecture by default. If Anthropic has a service disruption, the Crew can still process the tagging and the data—perhaps with a slightly more manual oversight—while you wait for the Foreman to come back online. If Google throttles your subscription, you can temporarily route the Crew’s work to Claude Sonnet.
This decoupling is essential for systems thinkers. It allows you to swap out components without re-writing the entire logic of your application. Your “Foreman” logic stays the same; you just change which “Crew” you are sending the batches to. This is the difference between building a fragile script and building a durable system.
What You Should Do Tomorrow
What you should do tomorrow.
If you are currently running a pipeline that relies solely on Claude, I am not suggesting you switch. I am suggesting you audit. Look at your logs and identify the tasks that don’t require Claude’s soul. Look for the tagging, the JSON formatting, the data extraction, and the basic categorization.
Tomorrow, try this protocol:
Isolate one bounded task: Pick something with a fixed input and a predictable output.
Set up a Gemini bridge: Use the API or a subscription-linked CLI to route that specific task.
Keep Claude as the orchestrator: Let Claude handle the “why” and the “how,” but let Gemini handle the “what.”
Measure the token savings: Don’t just look at the dollars. Look at how many Claude rate-limit tokens you’ve reclaimed for higher-value work.
The goal isn’t to use less AI; it’s to use the right AI for the right job. My best work runs on Gemini because it allows Claude to be the best version of itself. Stop hiring master carpenters to move boxes. Hire the crew, keep the foreman, and scale the system.
Published: May 25, 2026 | Last fact-check: May 25, 2026 against Anthropic docs and Claude Code v2.1+ behavior
Quick Answer
Plan Mode is a Claude Code setting that forces the agent to think through and approve a plan before taking destructive actions. Trigger it with Shift+Tab pressed twice in the terminal (the first press cycles to Auto-Accept Mode; the second lands on Plan Mode). Use it for risky multi-step work; skip it for simple read-only or contained edits.
How to enable it, when it pays off, and when it gets in your way below.
Plan Mode (sometimes called “planning mode”) is one of the more underused features in Claude Code in 2026. It changes how the agent works in a specific, measurable way: before Claude Code edits files, runs commands, or modifies state, it produces a plan and waits for your approval. You see what it intends to do, you say yes or no, and only then does it act.
For the right kind of task, Plan Mode is the difference between a clean execution and a regrettable one. For the wrong kind of task, it is friction that slows you down. This guide separates the two.
Claude Code Plan Mode vs Auto Mode: When to Use Each
Plan Mode vs Auto Mode — when to use each.
Scenario
Use Plan Mode
Use Auto Mode
Unfamiliar codebase
Yes — review the plan first
Only if you know it well
Large multi-file refactor
Yes — catch scope creep early
Not recommended
Simple bug fix (< 5 lines)
Overkill
Yes
Adding a new feature
Yes — plan clarifies approach
Acceptable for small features
Writing tests
Optional
Yes, usually safe
Touching database migrations
Yes — irreversible changes
No
CI/CD pipeline changes
Yes
No
What Plan Mode Actually Does
What Plan Mode actually does.
In default mode, Claude Code is allowed to take actions as it reasons. It can read files, write files, run bash, edit code, all in one conversational flow. This is the strength of Claude Code as an agent — it gets work done without asking permission for every step.
In Plan Mode, Claude Code’s behavior changes:
You describe the task.
Claude Code investigates the codebase (read-only operations are still allowed).
Claude Code drafts a plan listing every file it intends to change, every command it intends to run, and every decision point.
You read the plan. You approve it, modify it, or reject it.
Only after approval does Claude Code start writing files or running commands.
The plan is presented in the terminal as a structured outline. You can ask Claude Code to revise the plan, add steps, remove steps, or change the order. Iterating on the plan is fast because no actions have been taken yet.
How to Enable Plan Mode
How to enable Plan Mode.
There are four ways to activate Plan Mode in Claude Code:
Shift+Tab pressed twice. Each press of Shift+Tab cycles through the three permission modes: Default → Auto-Accept → Plan → Default. Two presses lands on Plan Mode. The status bar shows ⏸ plan mode on when active.
The /plan slash command. Type /plan at the start of any prompt to enter Plan Mode for that turn only. Useful for one-off plans without flipping the whole session.
The –permission-mode plan flag at startup. Start the session in Plan Mode from the command line.
Headless mode for scripts and CI.claude --print --permission-mode plan "your task" for automation that should never edit files.
# Start session in Plan Mode
claude --permission-mode plan
# Or mid-session — press Shift+Tab TWICE
# (first press = Auto-Accept Mode, second press = Plan Mode)
# Or one-shot Plan Mode for next prompt only
/plan
Plan Mode is persistent within a session — it stays on until you cycle out with another Shift+Tab. Close and reopen Claude Code and it defaults back to off. Toggle it on for risky work, leave it on for the whole session if you are doing higher-risk work end-to-end.
Important: Plan Mode is a hard read-only sandbox enforced at the tool level. Claude Code physically cannot edit files, run commands, or modify state while Plan Mode is active. This is not a suggestion or a soft check — the write tools are unavailable.
When Plan Mode Pays Off
Plan Mode is worth the friction in these situations:
Multi-file refactors. When the agent will touch 5+ files, you want to see the list before it starts editing. A small confusion about which files to change becomes a big mess fast.
Database migrations or schema changes. Anything that touches durable state and is hard to undo benefits from a confirmed plan.
Production code paths. If a session affects code that ships to users, the plan checkpoint is cheap insurance.
Ambiguous instructions. When you are not sure how the agent will interpret your request, Plan Mode surfaces the interpretation before any work happens.
New repository onboarding. When you do not yet know the codebase well, Plan Mode lets the agent show you what it learned during investigation before it acts.
Long-running batch jobs. Approving a plan for 200 file edits and then walking away is safer than launching 200 edits blind.
When Plan Mode Gets In the Way
Plan Mode is not free. The friction it adds is a real cost for certain workflows:
Single-file tweaks. Asking Claude Code to fix a typo or rename a variable does not need a plan. The plan takes longer than the fix.
Tight feedback loops. When you are iterating quickly — try a change, see the result, adjust — Plan Mode slows the loop. Default mode wins here.
Read-only investigation. If you are asking questions about the codebase (“how does this auth flow work”), there is nothing to plan. Plan Mode is irrelevant.
Work in a sandbox. If you are working in a throwaway directory or branch where mistakes are cheap, the safety net of Plan Mode is overkill.
The decision is not “is Plan Mode good.” It is “is the cost of approval less than the cost of an unintended action.” For risky multi-step work, yes. For cheap iteration, no.
Working Inside the Plan
Once Claude Code presents a plan, you have several options:
Approve as-is. Tell Claude Code to proceed. It executes the plan in order.
Approve with modifications. Tell Claude Code to remove specific steps, reorder them, or add additional steps. It revises the plan and re-presents.
Ask questions. Drill into specific steps. “Why are you editing file X?” Claude Code explains the reasoning.
Reject and restart. If the plan is wrong-shape, tell Claude Code so. It will rebuild the plan from a corrected understanding.
Cancel. Exit Plan Mode entirely if you’ve decided this is not the right task or session for it.
The plan is conversational. You are not stuck with the first draft. Iterating on the plan is much cheaper than iterating after the work is done.
What Plan Mode Does Not Protect Against
Plan Mode is not a sandbox. The plan, once approved, executes for real. Plan Mode does not:
Prevent you from approving a bad plan
Catch logic errors inside individual file edits
Prevent destructive bash commands if you approved them in the plan
Replace tests or code review
It is a thinking checkpoint, not a safety net. The human still owns the decision.
Plan Mode vs Other Safety Patterns
Plan Mode is one of several safety patterns Claude Code supports:
Read-only sessions: Restrict the agent to read operations only.
Per-tool permissions: Approve each tool use individually as it happens.
Plan Mode: Approve a batch of intended actions before execution begins.
Auto-accept mode: The opposite — accept all tool uses without asking. Fast and risky.
Per-tool permission is more granular but slower. Plan Mode is bulkier but faster once approved. Use the right tool for the situation; do not assume one is always correct.
A Working Habit
The habit that has worked across hundreds of Claude Code sessions: default mode on, Shift+Tab twice into Plan Mode before any session that will (a) touch production state, (b) edit more than 5 files, or (c) run commands that are hard to undo. Shift+Tab again to cycle back to default for everything else.
The shortcut becomes muscle memory in a week. Once it is muscle memory, the cost of Plan Mode drops to nearly zero, and you can use it liberally on anything that even smells risky.
Plan Mode is a Claude Code setting that forces the agent to produce a written plan and wait for your approval before making changes. It surfaces what the agent intends to do so you can adjust it before any work happens.
How do I enable Plan Mode in Claude Code?
Press Shift+Tab twice in the terminal (the first press cycles to Auto-Accept; the second lands on Plan Mode), type /plan as a slash command, or start the session with –permission-mode plan. The status bar shows ⏸ plan mode on when active.
When should I use Plan Mode?
For multi-file refactors, database migrations, production code paths, ambiguous instructions, new repositories you don’t know yet, and long-running batch jobs. Skip Plan Mode for single-file tweaks, tight iteration loops, and read-only investigation.
Does Plan Mode make Claude Code slower?
Yes, for short tasks — the plan adds latency that is not worth it on quick edits. For long or risky tasks, the plan is faster than fixing mistakes afterward.
Can I edit the plan before approving it?
Yes. Tell Claude Code to revise the plan — add steps, remove steps, reorder. Iterating on the plan is much cheaper than iterating after execution.
Is Plan Mode the same as a sandbox?
Plan Mode IS a hard read-only sandbox at the tool level — Claude Code cannot write files or run commands while it’s active. But once you approve the plan and exit Plan Mode, the work executes for real. Plan Mode prevents accidental writes during planning; it does not prevent you from approving a bad plan.
What’s the difference between Plan Mode and per-tool permissions?
Per-tool permissions ask you to approve each tool use individually as it happens (more granular, slower). Plan Mode batches all intended actions into one plan you approve up front (bulkier, faster once approved).
The Bottom Line
Plan Mode is leverage for risky work and friction for everything else. Make Shift+Tab+Shift+Tab muscle memory. Use Plan Mode whenever the cost of an unintended action exceeds the cost of approval — multi-file refactors, production changes, ambiguous specs. Skip it on cheap iteration. That single rule will save you more headaches than any other Claude Code habit.
Published: May 25, 2026 | Last fact-check: May 25, 2026 — current model lineup: Opus 4.7, Sonnet 4.6, Haiku 4.5
Quick Answer
A Claude Code router is any layer that decides which Claude model handles which request — Opus for hard reasoning, Sonnet for daily work, Haiku for fast cheap tasks. Anthropic ships some built-in routing, but the most leveraged users build their own routing rules on top to optimize cost and latency.
Built-in routing, manual model selection, and the third-party router landscape below.
“Claude Code router” is a phrase that means different things to different people in 2026, and the differences matter for what you should actually build or buy.
It can mean (1) Anthropic’s built-in logic that picks a model when you do not specify one, (2) third-party tools that route between Anthropic models and other LLMs through one Claude Code interface, or (3) custom routing rules you build yourself to match models to tasks. This guide walks through each, when each makes sense, and the trade-offs.
Why Routing Matters in the First Place
Why routing matters before you touch third-party routers.
Claude is not one model. It is a family. As of 2026 the production tiers are roughly:
Claude Opus 4.7 — $5/$25 per million tokens. Current flagship. Best for hard, ambiguous, multi-step reasoning and agentic coding.
Claude Sonnet 4.6 — $3/$15 per million tokens. The workhorse. Within ~1 point of Opus on coding benchmarks at 40% less cost. Right answer for 80% of daily work.
Claude Haiku 4.5 — $1/$5 per million tokens. Fast and cheap. Right answer for high-volume formulaic tasks: classification, extraction, formatting, routing, simple Q&A.
Output costs 5x input across all three tiers. Prompt caching cuts cached input costs by ~90%. Batch API cuts everything by 50% if you can wait up to 24 hours.
Using Opus for everything is wasteful. Using Haiku for everything is sloppy. Routing — matching the model to the task — is how you get the best output for the lowest cost. For someone running Claude Code several hours a day, intelligent routing is the difference between a $100/month Max bill and a $1,000/month API bill for the same work.
Anthropic’s Built-In Claude Code Routing
When you launch Claude Code without specifying a model, it picks a default. As of 2026 the default for most users is Sonnet, with Opus accessible via flags or settings, and Haiku used internally for some sub-tasks like tool selection and simple file operations.
You can override the default at session start:
# Start Claude Code with Opus for a tough refactor
claude --model claude-opus-4-7 # current flagship
# Or set it in your settings.json
{
"model": "claude-sonnet-4-6" // current workhorse
}
Anthropic also routes internally: when Claude Code uses sub-agents for parallel work, it can route those sub-agents to lighter models automatically. This routing is opaque to you and generally well-tuned. You usually do not need to think about it.
Manual Model Selection: The 80/20 Approach
Manual model selection is still the 80/20 approach.
For most users, manual routing beats automatic routing. The rule:
Opus when you hit a wall. Architectural decisions, hard refactors, ambiguous specs, anything that requires real reasoning.
Haiku for batch. Classification, taxonomy assignment, metadata generation, SEO meta descriptions, anything formulaic at volume.
This 80/20 split is achievable with two or three commands and zero infrastructure. It is the right starting point.
Third-Party Claude Code Routers
A small ecosystem has emerged around third-party routers that sit between Claude Code and the model layer. The two most common patterns:
OpenRouter and Multi-Provider Routers
OpenRouter is the most widely used third-party router. You point Claude Code at OpenRouter as the API endpoint, and OpenRouter routes your requests to Claude (or to GPT, Gemini, DeepSeek, Llama, etc.). Why use it:
You want fallback when Anthropic has an outage.
You want to mix Claude with other models on a per-task basis.
You want a single billing surface across providers.
You want BYOK (bring your own key) routing where you mix your own provider keys.
The trade-off: latency adds a few hundred milliseconds per call, and some Anthropic-specific features (prompt caching, certain beta tools) work less smoothly through the proxy.
Custom In-House Routers
Larger teams build their own routing layer. A typical pattern: a small Python or TypeScript service that inspects the incoming request, applies routing rules (length thresholds, task type detection, cost ceilings), picks a model, and forwards the call to Anthropic.
This is overkill for most individuals. It pays off when you have:
Strict cost controls that need enforcement, not suggestion
Multi-tenant usage where different customers get different models
Compliance requirements that need request inspection and logging
A real engineering team that can maintain the service
Routing Rules That Actually Work
If you are going to invest in any routing logic, these are the rules that pay back:
By task type. Code review → Opus. New code generation → Sonnet. Format conversion → Haiku.
By input length. Long context (40K+ tokens) where you need careful reasoning → Opus. Long context where you need extraction → Sonnet with prompt caching.
By cost ceiling. Anything over a threshold token count gets a hard cap or downgrade.
By time of day. Overnight batch jobs route to cheaper models. Interactive daytime work routes to your preferred quality tier.
By failure recovery. If a Sonnet call returns a low-confidence or refused response, retry once with Opus before giving up.
Most of these rules are five lines of code each. The discipline is more about deciding the rules than implementing them.
What Anthropic Does Not Yet Ship
As of writing, Anthropic does not ship a built-in “route this query to the right model” intelligence layer in Claude Code. The model you set is the model you get for the session, with the exception of internal sub-agent routing.
This is likely to change. The shape of where Claude Code is going — more autonomy, longer sessions, more parallel agents — implies more sophisticated internal routing. For now, the routing decisions worth making are the ones you make yourself.
Costs: What Routing Actually Saves
Routing only saves money if you enforce budgets.
Concrete example. An operator running a Claude Code content pipeline that:
Generates SEO meta and FAQ (Haiku): 2,000 + 500 tokens
Reviews and edits (Opus): 10,000 + 2,000 tokens for trickier articles
Running everything on Opus would roughly triple the cost. Running everything on Sonnet would save vs Opus but produce noticeably weaker meta-generation than Haiku at similar quality. Routing by task type saves real money — often 40-60% versus a single-model approach — without sacrificing output quality.
When Not to Build a Router
Routing is leverage when you operate at volume. If you run Claude Code casually — a couple of hours a day, one task at a time — you do not need a router. You need to learn the three models well enough to pick the right one by feel. Build a router only when (a) cost is a real line item in your budget, (b) you are running multiple workflows that have genuinely different model needs, or (c) you want fallback infrastructure for resilience.
A Claude Code router is any layer — Anthropic’s built-in defaults, a third-party tool like OpenRouter, or custom code — that decides which Claude model handles a given request.
Does Claude Code have built-in routing?
Partial. Claude Code picks a default model (Sonnet) and routes internal sub-agent tasks to lighter models. It does not automatically promote your main session to Opus when a task gets hard.
What’s the difference between OpenRouter and a custom router?
OpenRouter is a hosted multi-provider gateway with billing and fallback built in. A custom router is something you build to enforce your own rules. OpenRouter is right for most teams. Custom routers are right for teams with strict requirements.
Should I use OpenRouter with Claude Code?
Useful if you want fallback, multi-provider mixing, or unified billing. Less useful if you only use Claude and want Anthropic-specific features like prompt caching to work optimally.
How do I pick the right Claude model for a task?
Default Sonnet. Opus for hard reasoning, architectural decisions, ambiguous specs. Haiku for high-volume formulaic tasks (classification, formatting, metadata).
How much can routing save me?
For volume users, 40-60% versus running everything on Opus, with no measurable drop in output quality if the routing rules are sensible.
Is there a cost to routing through OpenRouter?
OpenRouter adds a small markup on token pricing in exchange for the routing and aggregation features. For most users this is acceptable; for very high volume, going direct to Anthropic is cheaper.
The Bottom Line
Claude Code routing is leverage when you operate at volume and a distraction when you do not. Start by learning the three Claude models by feel and picking manually. Add OpenRouter if you want fallback. Build a custom router only when cost or compliance actually justifies the engineering. The router is not the goal; the right model on the right task is the goal.
Published: May 25, 2026 | Last verified: June 28, 2026 (Pacific Time)
Quick Answer
Get an Anthropic API key at console.anthropic.com → API Keys → Create Key. The key starts with sk-ant- and is shown once — copy and store it in a password manager immediately. Add billing credits before making API calls.
Full setup, security, and usage walkthrough below.
An Anthropic API key is the credential that lets your application, script, or tool call Claude programmatically. Whether you are wiring Claude into Claude Code, building an internal agent, or integrating Claude into a SaaS product, the API key is the first step. This is the complete reference for that key — pricing, billing, security, rotation, and organization controls. If you just need to create your first key, our step-by-step guide to getting an Anthropic API key walks through it in about five minutes; this page is what you read next.
Anthropic API Pricing Tiers (June 2026)
API pricing tiers — stale-proof shapes, no sticky dollars.
All models support 50% Batch API discount for non-real-time requests. Fable 5 is free on Pro/Max/Team through June 22, 2026. Prices verified June 12, 2026.
What an Anthropic API Key Is (and Isn’t)
What an API key is — and is not.
The Anthropic API key authenticates requests to the Anthropic Messages API. It identifies which workspace and organization is making the call, what model permissions it has, and where to bill the token usage.
What an API key is not: a login. You cannot use an API key to sign into claude.ai. The web interface and the API are separate billing surfaces. Your Pro or Max subscription does not grant API credit by default; API usage requires its own billing setup.
Creating a key (the short version)
Creating a key — the short version.
Create a key at console.anthropic.com → API Keys → Create Key; it starts with sk-ant-, is shown once, and will not work until billing is added. For the full walkthrough — including the no-key OAuth option and the four errors that trip people up on the first request — see our step-by-step guide to getting an Anthropic API key. The rest of this page is the reference you will want once the key exists.
Adding Billing Before You Can Use the Key
A common surprise: a freshly created API key cannot make calls until you add a payment method and credits to your Anthropic account. The key exists, but every request returns a billing error.
To add billing:
In the Claude Console, click “Billing” or “Plans & Billing” in the left sidebar.
Add a payment method (credit card; Anthropic also supports invoicing for enterprise).
Either pre-purchase API credits or enable auto-recharge. Most users enable auto-recharge with a low threshold to avoid hitting empty mid-job.
Set a monthly usage limit if you want a safety cap.
Once billing is set up, your API key works.
Anthropic API Key Format
An Anthropic API key starts with the prefix sk-ant- followed by a long alphanumeric string. The full key is roughly 100 characters. If your key does not start with sk-ant-, you have copied something incomplete.
Different key types exist:
Live keys (sk-ant-api...): Production calls, real billing.
Admin keys (sk-ant-admin...): Workspace admin operations, not for inference calls.
Most developers only need a live key.
Which Claude Models the API Key Works With
A standard live API key gives you access to the current generation of Claude models:
Claude Fable 5 (claude-fable-5) — current top tier, released June 9 2026. $10/$50 per million tokens. Anthropic’s first Mythos-class model. Note: carries a mandatory 30-day data retention requirement (no zero data retention option). Full breakdown here.
Claude Opus 4.8 (claude-opus-4-8) — second tier, released April 16 2026. $5/$25 per million tokens. Supports zero data retention.
Claude Sonnet 4.6 (claude-sonnet-4-6) — released February 17 2026. $3/$15 per million tokens. The production default for most workloads.
Claude Haiku 4.5 (claude-haiku-4-5) — released October 15 2025. $1/$5 per million tokens. Fast and cheap for high-volume work.
Earlier model versions (Sonnet 4, Opus 4.6, Haiku 3.5, etc.) are still callable by their specific snapshot IDs until Anthropic announces deprecation. Check the deprecation timeline in the Claude Console for any model you depend on in production.
How to Use the API Key
You pass the key in the x-api-key header on every request to the Messages API:
In Python or Node.js, the official SDKs read ANTHROPIC_API_KEY from your environment automatically. You should never hardcode the key in source code.
Security: How to Not Leak Your Key
Anthropic API keys leak constantly. Most leaks happen the same way:
Committing the key to a public GitHub repo. The single most common leak. GitHub scans for known credential patterns and notifies Anthropic; your key gets auto-revoked within minutes. You will know because your calls suddenly start failing.
Pasting the key into a shared chat or document. Anyone with access becomes a credential holder.
Putting the key in client-side JavaScript. A browser app shipping its API key to users is giving the key away. Always proxy through a backend.
Logging the key. Any logging system that captures HTTP headers can leak the key. Mask sensitive headers in your logger config.
The good rule: treat your API key like a credit card number, because that’s what it functions as.
Rotating an Anthropic API Key
You should rotate keys quarterly at minimum, and immediately if a key is suspected compromised. Rotation in the Claude Console:
Go to API Keys.
Create a new key with a fresh name (e.g., “Claude Code Laptop 2026 Q3”).
Update your application’s environment variable or secret manager to use the new key.
Verify the new key works.
Revoke the old key.
The five-minute rotation is far cheaper than dealing with a leaked key that was used by an attacker for hours before you noticed.
Workspace and Organization Keys
Anthropic accounts are organized as: Organization → Workspaces → API Keys. Most individuals only use one of each. Teams use multiple workspaces to separate environments (production, staging, dev) or projects.
Each key belongs to one workspace. Billing rolls up to the organization. If you need separate billing visibility per project, separate workspaces are the lever.
Monitoring API Key Usage
The Claude Console shows per-key usage in the “Usage” section. You can see:
Token spend per key per day
Model breakdown (Opus, Sonnet, Haiku usage)
Input vs output token split
Cache usage (if you have prompt caching enabled)
Set up usage alerts in Billing. The Anthropic console can email you when daily or monthly spend crosses a threshold. This is the cheapest insurance against a runaway loop or compromised key.
Frequently Asked Questions
How do I get an Anthropic API key?
Sign in to console.anthropic.com, open API Keys in the sidebar, click Create Key, name it, and copy the key immediately. You cannot retrieve the full key after closing the creation modal.
Is the Anthropic API key free?
The key itself is free to generate. Using it costs money — Anthropic bills per token at the API pricing in effect. You must add billing credits before the key works.
Does my Claude Pro or Max subscription include API credits?
No. Pro and Max subscriptions cover the chat interface and Claude Code (with usage caps). API usage is billed separately against your Anthropic account.
What does an Anthropic API key start with?
Live API keys start with sk-ant-api. Admin keys start with sk-ant-admin. The key is roughly 100 characters long.
What happens if my Anthropic API key gets leaked?
Anyone with the key can use it to make API calls billed to your account until the key is revoked. If you suspect a leak, revoke immediately in the Claude Console and check Usage for any suspicious activity.
Can I use the same API key for Claude Code and my own app?
You can, but you should not. Use separate keys per environment (Claude Code Laptop, Production Backend, Local Dev). Separate keys make revocation surgical instead of catastrophic.
Where should I store my Anthropic API key?
In a password manager (1Password, Bitwarden) for personal use, or in a secret manager (AWS Secrets Manager, GCP Secret Manager, HashiCorp Vault) for production. Never commit it to a repo or hardcode it in source.
How do I rotate an Anthropic API key?
Create a new key in the Claude Console, update your application to use the new key, verify it works, then revoke the old key. Rotate quarterly as a baseline.
Get alerted when Claude pricing or limits change
We track Anthropic’s models, pricing, and limits daily and send a short note when something changes that affects what you pay or build. Occasional, no spam.
The Bottom Line
Getting an Anthropic API key is a three-minute process. Keeping it safe is a discipline. Use a password manager, rotate quarterly, never put the key in client-side code, and set usage alerts in the Claude Console. Treat the key as production infrastructure, not a developer toy, and it will serve you for years without incident.
You have your key. Now hit the ground running.
The Solo Builder Seed Kit includes a ready-made Claude skill file, 20 tested prompts for solo operators, and a step-by-step setup guide. Paste your API key, install the skill, and you’re building — $47.
Go to console.anthropic.com, sign in or create an account, then navigate to Settings > API Keys. Click ‘Create Key’, give it a name, and copy the key immediately — it is only shown once. You’ll need to add a credit card and funds to your account before making API calls.
Is there a free tier for the Anthropic API?
Anthropic does not offer a persistent free tier for the API. New accounts may receive a small initial credit to test the API. After that, all usage is billed at standard token rates. The free tier of claude.ai (the chat interface) is separate from API access.
How much does the Anthropic API cost?
As of June 2026: Claude Haiku 4.5 costs $1 input / $5 output per million tokens. Claude Sonnet 4.6 costs $3/$15. Claude Opus 4.8 costs $5/$25. Claude Fable 5 (newest, released June 9) costs $10/$50 per million tokens. The Batch API offers 50% off for non-real-time workloads.
How do I keep my Anthropic API key secure?
Never commit API keys to version control. Store them in environment variables or a secrets manager (AWS Secrets Manager, GCP Secret Manager, Vault). Use separate keys per application so you can rotate or revoke them independently. Set spending limits in the Anthropic console to cap accidental runaway costs.
What happens if my Anthropic API key is compromised?
Go to console.anthropic.com > Settings > API Keys immediately and click Revoke next to the compromised key. Create a new key and rotate it into your applications. Review your usage logs for unexpected spend. Anthropic will not refund charges made with a compromised key unless you contact support promptly.
Can I use my Anthropic API key with Claude Code and Claude Cowork?
Claude Code (the CLI tool) uses your API key when you run it outside a claude.ai subscription context. Claude Cowork (the desktop app) uses your subscription, not a raw API key. For self-hosted integrations, scripts, and Agent SDK workflows, your API key from console.anthropic.com is what you need.
Published: June 9, 2026 | Last fact-check: June 10, 2026 against Anthropic’s pricing page. Rates change — always verify at anthropic.com/pricing before commitments.
Quick Answer
Claude Code is included with Pro ($20/month), Max 5x ($100/month), Max 20x ($200/month), and Team Premium seats ($100/seat annual, 5-seat minimum). Team Standard does NOT include Claude Code. API-only billing is also available: Sonnet 4.6 at $3/$15 per million tokens, Opus 4.8 at $5/$25, Haiku 4.5 at $1/$5. Most individual developers get the best value from Max 5x at $100/month.
Full pricing breakdown and which tier fits which user below.
Claude Code pricing in 2026 is structured around two paths: subscription plans (Pro, Max, Team) that include Claude Code with usage caps, and API-only access where you pay Anthropic per token used. Most users choose a subscription. Heavy enterprise users sometimes choose the API path, and some use both.
This guide breaks down what each tier actually costs, what you get, and which path makes sense for which kind of user. The price ceiling sits at the Max $200/month plan for individuals, and at custom enterprise contracts above that.
Claude Code Subscription Plans (2026)
Claude Code subscription plans — stale-proof.
Claude Code pricing: model cost breakdown (June 2026)
Model
Input $/MTok
Output $/MTok
Context
Best for in Claude Code
Claude Fable 5
$10
$50
1M tokens
Most demanding reasoning, maximum capability
Claude Opus 4.8
$5
$25
1M tokens
Complex refactors, long-horizon agentic coding
Claude Sonnet 4.6
$3
$15
1M tokens
Daily development — best cost/capability ratio
Claude Haiku 4.5
$1
$5
200k tokens
Fast lookups, simple completions, cost control
Prices from platform.claude.com as of June 10, 2026. Batch API reduces costs by 50%. Prompt caching can reduce input costs significantly for repeated context. Claude Code bills through your Anthropic API account.
Claude Code subscription vs API billing
Subscription vs API billing paths.
Option
How billed
Best for
Claude Max plan
Flat monthly ($100 or $200)
Heavy daily Claude Code users who want predictable costs
API pay-as-you-go
Per token used
Variable usage, cost-optimized workflows, teams
API with caching
Per token (cached inputs discounted)
Long system prompts or repeated context (e.g., large codebase)
Anthropic offers four consumer-facing tiers that include Claude Code:
Small teams; collaboration but NO Claude Code access
Team Premium
$100/seat/month (annual, 5-seat minimum)
Engineering teams; required for Claude Code on Team plans
Enterprise
Custom
Larger orgs with security/compliance needs
Critical note for Team customers: Team Standard does NOT include Claude Code. You need Team Premium seats ($100/seat annual, $125/seat monthly) for any developer who needs Claude Code access. You can mix Standard and Premium seats on one team — useful when only part of your org codes.
What Each Tier Actually Includes
Pro: $20/month
Pro gives you access to Claude.ai (the chat interface), Claude Desktop, and Claude Code via the CLI. Usage limits are tighter than most committed users prefer — running multi-file refactors or long agent sessions hits the cap quickly. Pro is reasonable as a starting point. It is not adequate for serious daily Claude Code work.
Max 5x: $100/month
The 5x designation refers to the rough multiplier on usage limits compared to Pro. For most individual developers who use Claude Code several hours per day, this tier provides enough headroom to work without running into limits constantly. It is the sweet spot for solo operators and small consultancies.
Max 20x: $200/month
20x headroom for users who run Claude Code as an always-on agent — overnight jobs, batch processing, multi-hour orchestration. If you find yourself routinely worried about hitting limits on the 5x tier, the 20x tier removes that worry.
Team Standard: $20-25/seat/month (5-seat minimum)
Team Standard gives a small group shared admin, SSO, SCIM, shared projects, usage analytics, and centralized billing. It is collaboration infrastructure. Crucially, Team Standard does not include Claude Code access — any developer who needs Claude Code must be on a Premium seat.
Team Premium: $100-125/seat/month (5-seat minimum)
Team Premium adds Claude Code to the Team Standard feature set. At $100/seat annual, the per-seat economics match individual Max 5x ($100/month) while adding team management. For an engineering team of 5+ developers using Claude Code daily, Team Premium is a straight upgrade over individual Max subscriptions. You can mix Standard and Premium seats on one team — non-coding teammates can sit on Standard while developers get Premium.
Claude Code via API: Pay-Per-Token
The alternative to a subscription is using Claude Code with API credentials directly. You provide an Anthropic API key, and your token usage gets billed against your Anthropic account at API rates.
API pricing (per million tokens, May 2026 standard rates):
Claude Haiku 4.5: $1.00 input / $5.00 output — cheapest current-generation model, ideal for classification, routing, summarization at volume
Claude Sonnet 4.6: $3.00 input / $15.00 output — best price-to-quality ratio; the production default
Claude Opus 4.8: $5.00 input / $25.00 output — current flagship; complex reasoning and agentic coding
Prompt caching: cached reads at 10% of standard input rate — up to 90% savings on repeated context
Batch API: 50% off both input and output if you can wait up to 24 hours for results
Output:input ratio: consistently 5x across all current-generation models
One catch with Opus 4.8: list price is identical to Opus 4.8, but Anthropic shipped a new tokenizer that can produce up to 35% more tokens for the same input text. Your effective bill per request can go up even though the rate card did not. Worth knowing before you switch your default model.
For heavy users, the API path can be cheaper than Max, but you give up the predictability of a flat monthly fee. For lighter users, the API path is almost always more expensive than Pro.
How to Decide: Subscription vs API
How to decide: subscription vs API.
The decision tree is simpler than it looks.
You use Claude Code less than an hour a day: Pro at $20/month.
You use Claude Code several hours a day: Max 5x at $100/month.
You run Claude Code as an unattended agent or for batch work: Max 20x at $200/month, or API with prompt caching enabled.
You’re a team of 5+ developers: Team Premium at $100/seat/month (annual; $125 monthly), or look at Enterprise.
You have unpredictable spikes: API with budget alerts gives you the most control.
What’s Not Included in Subscription Plans
Even on Max 20x, a few things still cost extra or fall outside the standard plan:
Anthropic API tokens for non-Claude Code use: If you build apps that call the Anthropic API directly, those tokens bill against API credits, not your Max subscription.
Third-party MCP servers with their own costs: Many MCP servers are free, but some integrate with paid services that bill you separately.
Storage and infrastructure costs: Where you actually run Claude Code (your laptop, your cloud VM) still costs whatever it costs.
Hidden Value: Why Max Pays Back Quickly
$100/month sounds steep until you compare it to what Claude Code replaces. For an operator running multi-step content workflows, infrastructure automation, or coding tasks that would otherwise require additional contracting hours, the Max plan typically pays back inside the first week of the month.
One concrete example: drafting and publishing a single SEO-optimized WordPress article with full schema, taxonomy, internal linking, and AEO/GEO optimization takes a human content team 3-5 hours. Running it through a Claude Code pipeline takes 15 minutes of supervised work. The output quality difference is small; the cost difference is large.
This is the framing that matters: Claude Code pricing is not “how much does the AI cost.” It is “how much labor does the AI replace.” On that framing, Max 5x is the cheapest line item in most knowledge-work budgets.
Annual vs Monthly Billing
Anthropic offers a discount for annual prepayment on Pro and Max tiers — generally around 20% off. If you are confident in your usage pattern, the annual prepay is the right call. If you are still evaluating, monthly gives you flexibility to change tiers as your needs shift.
New for June 15, 2026: the Agent SDK Credit Pool (Dual-Bucket Billing)
Starting June 15, 2026, Anthropic splits subscription usage into two buckets: interactive Claude Code sessions keep drawing from your normal plan limits, while unattended Agent SDK work (claude -p, cron jobs, CI pipelines, scripts) draws from a new monthly credit pool — Pro $20, Max 5x $100, Max 20x $200, Team Standard $20/seat, Team Premium $100/seat — with overage billed at standard API rates.
Practical impact: if you run any headless automation on a subscription today, that usage stops counting against your interactive limits and starts metering against the credit pool. Light automation — a nightly script or two — fits comfortably inside Pro’s $20 pool; sustained agent fleets will spill into API-rate overage, at which point a dedicated API key is usually easier to manage. Full mechanics, worked examples, and what to do before the cutover: Claude Agent SDK dual-bucket billing — what changes June 15, 2026. To model your own numbers, use the interactive calculator on our main Claude pricing page.
Claude Code is included with Claude Pro ($20/month), Max 5x ($100/month), or Max 20x ($200/month). API-only usage is billed per token at separate rates.
Is there a free version of Claude Code?
No. Claude Code requires either a paid Claude subscription (Pro, Max, or Team) or API credentials with a funded account. The Claude free tier does not include Claude Code.
What’s the difference between Max 5x and Max 20x?
The numbers refer to roughly how much usage you get relative to Pro. Max 5x ($100/month) suits daily developers. Max 20x ($200/month) suits heavy users running agent workflows or long batch jobs.
Can I use Claude Code with just an API key instead of a subscription?
Yes. Claude Code accepts an Anthropic API key for authentication. You pay per-token usage at API rates instead of a flat subscription fee.
Is Claude Code cheaper than GitHub Copilot or Cursor?
At the entry level, Copilot ($10/month) and Cursor Pro ($20/month) cost less than Max. Per unit of output for serious work, Claude Code on Max often comes out cheaper because of how much it can do per session.
Does Team pricing include Claude Code?
Only Team Premium ($100/seat annual, $125/seat monthly, 5-seat minimum) includes Claude Code. Team Standard does NOT include Claude Code. You can mix Standard and Premium seats on the same team so non-coding teammates can sit on Standard while developers get Premium.
What happens if I hit my Claude Code usage limit?
On Pro and Max, Claude Code slows or pauses until your usage window resets (typically rolling 5-hour windows on Pro, longer reset cadences on Max). You can upgrade tiers anytime for immediate additional capacity.
The Bottom Line on Claude Code Pricing
For most serious users: Max 5x at $100/month. For light users: Pro at $20/month. For heavy agent workloads: Max 20x at $200/month or API with prompt caching. The pricing is competitive with other AI coding tools, and the value relative to labor it replaces makes Max the cheapest line item on most knowledge-work budgets.
More Claude Code Pricing Questions: Plans, Seats, and Limits
Is Claude Code free?
Claude Code is not free. It requires a paid subscription: Pro ($20/month), Max 5x ($100/month), Max 20x ($200/month), or Team Premium seats ($100/seat/month annual). The Free tier does not include Claude Code. API-only access is also available at standard token rates.
What is the cheapest plan that includes Claude Code?
Pro at $20/month is the cheapest Claude subscription that includes Claude Code. However, Pro has tighter usage limits and heavy Claude Code sessions will hit the cap quickly. For daily developer use, Max 5x at $100/month provides much more headroom.
Does Claude Code use API tokens from my subscription?
Claude Code usage counts against your subscription plan’s included usage, not against separate API credits. Subscription plans and API access are billed separately — a Pro subscription does not give you API credits. If you need programmatic API access alongside Claude Code, you need both.
How does Claude Code pricing compare to GitHub Copilot?
GitHub Copilot costs $10–$19/month for individuals. Claude Code starts at $20/month (Pro) with usage limits, or $100/month (Max 5x) for heavier use. Claude Code offers a larger context window and stronger reasoning for complex multi-file tasks; Copilot has tighter IDE integration. For pure code completion, Copilot is cheaper. For agentic coding and large-context work, Claude Code is more capable.
Can I use Claude Code on a Team Standard plan?
No. Team Standard ($25/seat/month annual) does not include Claude Code. Only Team Premium seats ($100/seat/month annual) include Claude Code. You can mix Standard and Premium seats on one Team plan — assign Premium only to developers who need Claude Code.
What happens to Claude Code usage when I hit my plan limit?
When you hit your included usage limit, you can continue on Pro, Max 5x, and Max 20x using extra usage billed at standard API rates with a spending cap you set. This prevents surprise overages while keeping Claude Code available for critical work beyond your plan ceiling.
Claude Code API and Model Questions
How much does Claude Code cost in 2026?
Claude Code bills through your Anthropic API account based on which model you use. As of June 2026: Claude Opus 4.8 costs $5/$25 per million input/output tokens; Claude Sonnet 4.6 costs $3/$15 per MTok; Claude Haiku 4.5 costs $1/$5 per MTok; Claude Fable 5 (the new June 2026 flagship) costs $10/$50 per MTok. There is no separate Claude Code subscription — usage is API-billed. Heavy users may find the Claude Max plan ($100–$200/month flat) more cost-effective.
What is the cheapest way to use Claude Code?
Use Claude Haiku 4.5 ($1/$5 per MTok) for simple tasks and Claude Sonnet 4.6 ($3/$15 per MTok) for most development work. Enable prompt caching for large codebases — repeated context (like a long system prompt or frequently referenced file) is cached and billed at a significant discount. Use the Message Batches API for non-real-time work to get 50% off standard rates. Reserve Opus 4.8 or Fable 5 for tasks that genuinely require maximum capability.
Does Claude Code have a subscription plan?
Claude Code itself does not have its own subscription — it bills through your Anthropic API account. However, the Claude Max plan ($100/month for 5x usage limits, or $200/month for 20x limits) can cover Claude Code usage. If you’re using Claude Code heavily every day, Max may be more cost-effective than pure pay-as-you-go API billing. Check platform.claude.com/docs/en/about-claude/pricing for current plan details.
Which Claude model should I use with Claude Code?
Claude Sonnet 4.6 is the best default for most Claude Code workflows — it offers near-Opus intelligence at half the price ($3 vs $5 per input MTok) and supports extended thinking. Use Claude Opus 4.8 for complex multi-file refactors or architecturally difficult problems where output quality is worth the premium. Claude Fable 5 (launched June 10, 2026) is available for maximum capability tasks. Use Haiku 4.5 for fast, cheap lookups and simple completions.
Does Claude Code support prompt caching?
Yes. Claude Code supports Anthropic’s prompt caching feature. For workflows where you repeatedly pass the same large context — a codebase system prompt, a long CLAUDE.md file, frequently referenced documentation — prompt caching stores that context and bills repeated reads at a discounted rate. This can significantly reduce costs for projects with large persistent context. See platform.claude.com/docs/en/build-with-claude/prompt-caching for implementation details.
How do I track my Claude Code API spending?
Monitor usage at platform.claude.com — the console shows token usage and cost by model, date range, and API key. Set spending limits on your API key to cap maximum monthly spend. For teams, use separate API keys per project or environment to attribute costs. The usage dashboard updates in near-real time so you can catch runaway spend before it compounds.
