Anthropic ships four distinct ways to put Claude to work as an agent, and they are easy to confuse. The short version: Claude Cowork and Claude Code are interactive products billed through your Claude subscription — Cowork for knowledge work in the desktop app, Code for software work in your terminal, IDE, desktop, or browser. The Claude Agent SDK and Managed Agents are programmatic surfaces for developers, billed through the API: the Agent SDK is a Python/TypeScript library that runs the agent loop inside your own process, while Managed Agents is a REST API where Anthropic runs the loop and hosts the sandbox. The tables below give the verified, side-by-side breakdown.
The decision matrix
Cowork vs Code vs Agent SDK vs Managed Agents matrix.
Each row is one surface. Read across for who it serves, whether you drive it turn-by-turn or hand it a goal, where the work executes, and how it is paid for.
Surface
Who it is for
Interactive vs autonomous
Where it runs
How it is billed
Claude Cowork
Knowledge workers (non-developers) — research, documents, file and spreadsheet work
Interactive, supervised — shows you the plan and waits for your approval before acting
The Claude desktop app on your own computer (macOS or Windows); not available on web or mobile
Claude subscription (Pro, Max, Team, Enterprise) — draws from your plan’s usage allocation
Interactive — you drive it in a session, though it can run agentically across files and tools
Your machine (terminal, VS Code, JetBrains, desktop app) or the browser at claude.ai/code
Claude subscription or an Anthropic Console (API) account
Claude Agent SDK
Developers building custom agents programmatically (Python or TypeScript)
Autonomous — Claude reads files, runs commands, and edits code on its own via the agent loop
Your own process and infrastructure
API key (pay-as-you-go credits); see the subscription note below for the June 15, 2026 change
Managed Agents
Developers running production or long-running agents without operating their own sandbox/session infrastructure
Autonomous — you send events, Claude executes tools and streams back results
Anthropic-managed cloud sandbox per session (or a self-hosted sandbox on your own infrastructure)
Claude API key + the managed-agents-2026-04-01 beta header (no subscription path)
Where billing actually differs
The cleanest way to split these four is by the wallet they draw from. The two interactive products are funded by a subscription; the two programmatic surfaces are funded by the API. This is the single distinction that trips people up most often, so it is worth stating plainly in its own table.
Surface
Billing model
Notes
Claude Cowork
Subscription
Included on Pro, Max, Team, and Enterprise. Multi-step tasks consume more of your usage allocation than chatting.
Claude Code
Subscription or API
Most surfaces require a Claude subscription or a Console account; the terminal CLI and VS Code also support third-party providers.
Claude Agent SDK
API (pay-as-you-go)
Authenticated with an ANTHROPIC_API_KEY; also supports Bedrock, Claude Platform on AWS, Vertex AI, and Azure. Anthropic does not permit claude.ai login for third-party agents built on the SDK.
Managed Agents
API (credits)
Requires a Claude API key and the beta header; enabled by default for API accounts.
One dated nuance is worth pinning down because it changes how subscription users pay for programmatic work. Starting June 15, 2026, Claude Agent SDK and claude -p usage on subscription plans no longer counts toward your Claude plan’s interactive usage limits; instead, eligible subscribers receive a separate monthly Agent SDK credit (per-user, not pooled), while subscription usage limits stay reserved for interactive use of Claude Code, Cowork, and Claude. If you use the Agent SDK with an API key from the Claude Platform, nothing changes — pay-as-you-go billing continues and you do not receive an Agent SDK monthly credit.
SDK vs Managed Agents: the programmatic split
SDK vs Managed Agents — the programmatic split.
Both programmatic surfaces let Claude run tools autonomously, but they differ in where the loop and the work live. Anthropic’s own comparison frames it this way: the Agent SDK “is a library that runs the agent loop inside your own process,” while Managed Agents “is a hosted REST API: Anthropic runs the agent and the sandbox, and your application sends events and streams back results.” Pick by who you want operating the infrastructure.
Dimension
Agent SDK
Managed Agents
Runs in
Your process, your infrastructure
Anthropic-managed infrastructure
Interface
Python or TypeScript library
REST API
Agent works on
Files on your infrastructure
A managed sandbox per session
Session state
JSONL on your filesystem
Anthropic-hosted event log
Best for
Local prototyping; agents that work directly on your filesystem and services
Production agents without operating sandbox/session infrastructure; long-running, asynchronous sessions
A common path, per Anthropic’s docs, is to prototype with the Agent SDK locally, then move to Managed Agents for production.
Quick chooser
Quick chooser for the right surface.
If you are not writing code and want Claude to finish a task on your computer, use Cowork. If you are a developer working interactively on a codebase, use Claude Code. If you are building your own agent and want it to run in your own process, use the Agent SDK. If you want Anthropic to run the agent and host the sandbox for long-running or production work, use Managed Agents.
Is Claude Cowork the same as Claude Code?
No. Both appear in the Claude desktop app, but Cowork is aimed at knowledge work (research, documents, spreadsheets, file management) for non-developers, while Claude Code is an agentic coding tool. Cowork runs only in the desktop app (macOS or Windows); Claude Code also runs in the terminal, VS Code, JetBrains, and the browser.
Does a Claude subscription cover the Agent SDK or Managed Agents?
Cowork and Claude Code are included with Claude subscriptions (Pro, Max, Team, Enterprise). The Agent SDK and Managed Agents are API surfaces authenticated with a Claude API key. As of June 15, 2026, subscription users do get a separate monthly Agent SDK credit for SDK and claude -p usage, but Managed Agents has no subscription path — it requires an API key and a beta header.
Where does the work actually execute for each surface?
Cowork runs on your own computer in the desktop app. Claude Code runs on your machine (or in the browser). The Agent SDK runs in your own process and infrastructure. Managed Agents executes in an Anthropic-managed cloud sandbox per session, or a self-hosted sandbox you control.
Is the Agent SDK built on Claude Code?
Yes. Per Anthropic, the Agent SDK “gives you the same tools, agent loop, and context management that power Claude Code, programmable in Python and TypeScript.” Anthropic also describes it as “Claude Code as a library.”
Is Managed Agents generally available?
No. As of June 13, 2026, Claude Managed Agents is in beta. Every Managed Agents endpoint requires the managed-agents-2026-04-01 beta header (the SDK sets it automatically), and access is enabled by default for API accounts.
Last refreshed: October 20, 2026 · Benchmark scores verified June 13, 2026
As of June 13, 2026, the four models most often compared for coding work are Claude Fable 5 and Claude Opus 4.8 from Anthropic, GPT-5.5 from OpenAI, and Gemini 3.1 Pro from Google. This page is a leaderboard built on one rule: every score below is taken from a vendor’s own page or the benchmark’s official model card that we fetched on the verification date, or it is marked as not published. Several vendors publish their benchmark tables as images rather than machine-readable text; where we could not read an official figure directly, we list the metric as not machine-verifiable and link to the source document instead of estimating. The result is a smaller table than most roundups, but every number in it is one you can click through and check.
September 2026 lineup update: Since these scores were verified, Anthropic’s lineup has moved on — the current models are Fable 5.1, Opus 5.5, and Sonnet 5, replacing Fable 5 and Opus 4.8. The benchmark scores below are for the June 2026 models and stay labeled as such; they have not been re-attributed to the new models. Current Claude API pricing (September 2026): Sonnet 5 $2/$10, Opus 5.5 $4/$20, Haiku 4.5 $1/$5, Fable 5.1 $10/$50 per Mtok.
Models and pricing (specs verified June 13, 2026)
Models compared — verified specs without sticky dollars.
These columns are confirmed from each vendor’s official model documentation. Claude prices, context windows, and cutoffs come from Anthropic’s models overview and the AWS Bedrock model card; GPT-5.5 from OpenAI’s developer docs; Gemini 3.1 Pro from Google’s DeepMind model card and the Gemini API pricing page.
Model
API ID
Input / Output (per Mtok)
Context
Max output
Knowledge cutoff
Claude Fable 5
claude-fable-5
$10 / $50
1M
128K
Not stated on overview*
Claude Opus 4.8
claude-opus-4-8
$5 / $25
1M
128K
Jan 2026
GPT-5.5
gpt-5.5
$5 / $30
1,050,000
128K
Dec 1, 2025
Gemini 3.1 Pro
gemini-3.1-pro-preview
$2 / $12 (≤200K)**
1M
64K
Not stated on model card
*Anthropic’s models overview lists Fable 5’s specs and price but does not publish a knowledge-cutoff date for it in the table we fetched. **Gemini 3.1 Pro uses tiered pricing: $2 / $12 per Mtok for prompts up to 200K tokens, rising to $4 / $18 for prompts above 200K tokens (Google AI pricing page). GPT-5.5 pricing rises to 2x input / 1.5x output above 272K input tokens (OpenAI developer docs). Claude Opus 4.8 (legacy — still listed) offers an optional fast mode at $10 / $50 per Mtok (Anthropic).
Coding benchmark scores (primary-source only, June 2026 models)
Coding benchmark scores — primary-source only.
Each cell is either a figure we read directly from a primary source on June 13, 2026, or marked “not machine-verifiable” with the source you should consult. A blank-equivalent entry never means zero — it means the official figure was not available in readable form during verification. Note the harness and version differences called out in the footnotes: they make cross-vendor cells not strictly comparable.
Benchmark
Claude Fable 5
Claude Opus 4.8
GPT-5.5
Gemini 3.1 Pro
SWE-bench Verified
Not machine-verifiable (see system card)
Not machine-verifiable (see system card)
Not published in retrievable primary source
80.6%
SWE-bench Pro (Public)
Not machine-verifiable (see system card)
Not machine-verifiable (see system card)
Not published in retrievable primary source
54.2%
Terminal-Bench
Not machine-verifiable (see system card)
Not machine-verifiable (see system card)
83.4% (v2.1, Codex CLI harness)â€
68.5% (v2.0, Terminus-2 harness)
LiveCodeBench Pro
Not published in retrievable primary source
Not published in retrievable primary source
Not published in retrievable primary source
2887 Elo
†GPT-5.5’s Terminal-Bench 2.1 figure of 83.4% is the score Anthropic attributes to GPT-5.5 “with the Codex CLI harness” in a footnote on its Claude Opus 4.8 announcement page. It is a competitor-reported comparison, not a number we read from OpenAI directly. Google reports Gemini 3.1 Pro on Terminal-Bench 2.0 under the Terminus-2 harness (68.5%); because the version and harness differ, the Gemini and GPT-5.5 Terminal-Bench cells are not directly comparable. Gemini’s SWE-bench Verified (80.6%), SWE-bench Pro Public (54.2%), and LiveCodeBench Pro (2887 Elo) are single-attempt figures from Google’s official Gemini 3.1 Pro model card.
What we could not verify from a primary source
Anthropic publishes its coding comparison tables for Claude Opus 4.8 and Claude Fable 5 as images inside its announcement pages, and the full Claude Opus 4.8 System Card PDF exceeded our fetch size limit, so we could not machine-read those percentages on the verification date. OpenAI’s GPT-5.5 announcement page returned an access error to our fetcher, and its developer-docs model page lists specs and pricing but no benchmark scores. We have therefore left Claude’s and GPT-5.5’s SWE-bench figures out of the table rather than reproduce numbers we could not confirm at the source. For those figures, consult the primary documents linked in our source list: the Claude Opus 4.8 System Card, the Claude Fable 5 and Mythos 5 announcement, and OpenAI’s GPT-5.5 page. If you are choosing a model today, the verified spec table above (price, context, output, cutoff) is the part you can rely on without caveat.
How to read a coding leaderboard
How to read a coding leaderboard.
Three cautions apply to any 2026 coding comparison. First, harness matters: the same model scores differently on Terminal-Bench depending on whether it runs under Terminus-2, a Codex CLI scaffold, or a vendor’s internal agent, which is why we annotate every Terminal-Bench cell. Second, version matters: “Terminal-Bench 2.0” and “Terminal-Bench 2.1” are different test sets, and “SWE-bench Pro” public and full splits differ — a single percentage with no version is close to meaningless. Third, a headline score is one slice of behavior; long-horizon agentic coding, tool-call reliability, and context handling over a long session often decide real-world usefulness more than a single pass rate. Treat the verified cells here as a starting point, then test the shortlist on your own repository.
Which model has the highest published coding benchmark score in June 2026?
We cannot crown a single winner from primary sources alone, because Anthropic and OpenAI publish their coding scores in formats we could not machine-verify on June 13, 2026. From figures we could read directly, Google’s Gemini 3.1 Pro model card reports 80.6% on SWE-bench Verified and 54.2% on SWE-bench Pro (Public). Anthropic’s and OpenAI’s comparable figures are in their system cards and announcement pages, which we link in the sources; we did not reproduce them here because they were not readable at the source during verification.
What does Claude Fable 5 cost, and how is it different from Opus 4.8 (legacy — still listed)?
Claude Fable 5 (claude-fable-5) is priced at $10 per million input tokens and $50 per million output tokens, with a 1M-token context window and up to 128K output tokens (Anthropic models overview). Claude Opus 4.8 (legacy — still listed) (claude-opus-4-8) is the Opus-tier flagship at $5 / $25 per Mtok, also 1M context and 128K output, with a January 2026 knowledge cutoff. Fable 5 is Anthropic’s most capable widely released model; Opus 4.8 (legacy — still listed) is the lower-priced model most teams will use for everyday agentic coding.
Lineup currency (Sept 2026): Current API list (Sept 2026, verified): Sonnet 5 $2/$10, Opus 5.5 $4/$20, Haiku 4.5 $1/$5, Fable 5.1 $10/$50. Legacy (still listed on Anthropic’s card): Opus 4.8 $5/$25, Sonnet 4.6 $3/$15.
Why are some benchmark cells marked “not machine-verifiable” instead of showing a number?
Because this page only prints scores we could confirm from a primary source on the verification date. Several vendors render their benchmark tables as images, and one large system-card PDF exceeded our fetch limit, so the underlying percentages were not readable to us. Rather than copy figures from third-party trackers, we mark the cell and point you to the official document. It keeps the leaderboard honest at the cost of being shorter.
How do the context windows compare?
Claude Fable 5, Claude Opus 4.8, and Gemini 3.1 Pro each offer a 1M-token context window; GPT-5.5 offers 1,050,000 tokens. Maximum output is 128K tokens for Claude Fable 5, Claude Opus 4.8, and GPT-5.5, and 64K tokens for Gemini 3.1 Pro. Note that Claude Opus 4.8’s context window is 200K on Microsoft Foundry specifically, per Anthropic’s documentation.
Is Terminal-Bench comparable across these models?
Not cell-for-cell. Google reports Gemini 3.1 Pro on Terminal-Bench 2.0 under the Terminus-2 harness (68.5%), while the GPT-5.5 figure we show (83.4%) is Terminal-Bench 2.1 under a Codex CLI harness, as attributed by Anthropic. Different versions and different harnesses mean the two numbers should not be read as a head-to-head result.
This slug duplicates the ranking tracker. Numbers here were last written as June 2026.
Direct Answer (9 September 2026): Claude 3.5 Sonnet is retired. Current public Sonnet is Sonnet 5 at $2 / $10 per MTok. Current lineup is Fable 5.1, Opus 5.5 ($4 / $20 per MTok), Opus 5, Sonnet 5, Haiku 4.5. Live tracker: current Claude model version. Seat dollars: pricing hub.
Do not ship 3.5 Sonnet, Sonnet 4.6, or Opus 4.8 IDs in new work. Confirm the alias in the console.
Anthropic released Claude Fable 5 on June 9, 2026 — and it’s the most capable model the company has ever made publicly available. After tracking every Claude release since the original 100K context window dropped, I can say this one is different. Fable 5 isn’t just an incremental update. It’s Anthropic’s Mythos-class model — the one they’d been keeping restricted — now opened up to anyone with an API key or a Claude subscription.
Here’s what you need to know: the pricing, the benchmarks, and the specific decision framework for when to use Fable 5 versus sticking with Opus 4.8.
Quick answer: Fable 5 costs $10/$50 per million input/output tokens (2x the cost of Opus 4.8). It outperforms Opus 4.8 significantly on complex coding, long-horizon tasks, and scientific research. Use Fable 5 when quality on hard problems justifies the cost. Use Opus 4.8 for high-volume, well-scoped, routine work.
Current lineup note (October 2026): Fable 5.1 is the current Fable SKU at the same $10/$50 headline rates (cache reads $0.25/MTok). Current Opus is Opus 5.5 at $4/$20; Opus 4.8 remains listed as legacy. The June 2026 comparisons below are the launch record for Fable 5.
What Is Claude Fable 5?
What is Claude Fable 5?
Claude Fable 5 (claude-fable-5) is Anthropic’s first publicly available Mythos-class model. The Mythos line is Anthropic’s highest capability tier — models that were previously restricted to research and select enterprise partners because of their raw power. Fable 5 is the version Anthropic deemed safe enough to release broadly.
The name shift (from the Opus/Sonnet/Haiku tier naming) signals something intentional. Fable 5 sits above the Opus line entirely. It’s a new ceiling.
Key specs:
Context window: 1M tokens (same as Opus 4.8)
Max output: 128K tokens per request
Thinking: Adaptive (always on — not a separate “thinking mode”)
Vision: Yes
Tool use / function calling: Yes
Available: Claude API, AWS Bedrock, Vertex AI, Microsoft Foundry
Claude Fable 5 Pricing
Fable 5 pricing — no sticky dollar stickers.
Model
Input (per MTok)
Output (per MTok)
Context
Claude Fable 5
$10.00
$50.00
1M tokens
Claude Opus 4.8
$5.00
$25.00
1M tokens
Claude Sonnet 4.6
$3.00
$15.00
1M tokens
Claude Haiku 4.5
$1.00
$5.00
200K tokens
Fable 5 costs exactly 2x Opus 4.8 on API. On subscription plans (Pro, Max, Team, Enterprise seat-based), Fable 5 is included at no extra cost through June 22, 2026.
The free-until-June-22 window matters if you’re evaluating whether to route your workloads to Fable 5. Use that window to benchmark it against your actual tasks before the 2x cost kicks in.
Benchmark Performance: Where Fable 5 Pulls Away
The benchmarks that matter most are the ones that measure what the model can do on real engineering work, not trivia:
Benchmark
Claude Fable 5
Claude Opus 4.8
Delta
SWE-bench Verified
95.0%
88.6%
+6.4 pts
SWE-bench Pro
80.0%
69.2%
+10.8 pts
FrontierCode
29.3%
13.4%
~2.2x
Senior Engineer benchmark
91/100
~63/100
+45% absolute
The Senior Engineer benchmark is the one I find most telling. It’s designed to be hard for people who write code for a living — and Fable 5 scores 45 percentage points higher than Opus 4.8. That gap is significant enough that it changes the calculus for serious engineering work.
When to Use Claude Fable 5 (vs Opus 4.8)
When to use Fable 5 vs Opus.
I’ve been routing tasks between models for long enough to have a framework. Here’s how I think about it:
Use Fable 5 when:
You’re running a large migration, refactor, or multi-stage software project
Quality on a hard problem matters more than per-token cost
You’re doing deep research, complex analysis, or long-horizon agentic work
The task would otherwise take a senior engineer half a day or more
You’re in the free evaluation window (through June 22) and want to benchmark
Use Opus 4.8 when:
The task is well-scoped and routine
You’re running high-volume pipelines where 2x cost compounds fast
Latency matters — Fable 5 can take 60 seconds to several minutes on complex tasks vs 3–15 seconds for Opus 4.8
The task falls in Fable 5’s restricted domains (cybersecurity, biology, chemistry, distillation) — in those categories, Fable 5 routes to Opus 4.8 anyway, so you’d pay Fable 5 prices for Opus 4.8 output
The smart routing strategy: Fable 5 for the hard jobs, Opus 4.8 for the rest. Don’t use Fable 5 as your default model — the cost and latency delta aren’t worth it for routine tasks.
Important Limitations to Know Before You Switch
Two limitations that don’t get enough coverage:
1. Safety classifier routing. Fable 5 includes enhanced safety classifiers. For prompts touching cybersecurity, biology, chemistry, and distillation, those classifiers route the request to a Claude Opus 4.8 fallback. You pay Fable 5 API rates ($10/$50) but get Opus 4.8 output. If your use case is in these domains, Fable 5 is not the upgrade it appears to be.
2. Data retention requirement. Fable 5 carries a mandatory 30-day data retention policy — Anthropic needs retained prompts and outputs to operate the safety classifiers. Claude Opus 4.8 is available under zero data retention (ZDR). If your use case requires ZDR (healthcare, legal, finance with strict data handling), stick with Opus 4.8 until Anthropic updates Fable 5’s data policy.
Availability
Claude Fable 5 is generally available as of June 9, 2026 on:
Claude API (claude-fable-5)
Claude Platform on AWS / Amazon Bedrock
Google Cloud Vertex AI
Microsoft Azure AI Foundry / GitHub Copilot
Subscription access (free through June 22, 2026): Claude Pro ($20/mo), Max 5x ($100/mo), Max 20x ($200/mo), Team, and seat-based Enterprise plans all include Fable 5 access at no extra charge during the launch window. After June 22, the plan-tier access picture may change — check Anthropic’s pricing page for updates.
How This Changes the Claude Model Decision Tree
Before Fable 5, the Claude decision tree was straightforward:
Need the best? → Opus 4.8
Need balance? → Sonnet 4.6
Need speed/cost? → Haiku 4.5
Now it’s:
Hard problems, complex projects, long-horizon work → Fable 5
Everyday work, high-volume pipelines → Opus 4.8
Balance of cost and capability → Sonnet 4.6
Speed and cost optimization → Haiku 4.5
The introduction of a model tier above Opus 4.8 doesn’t replace the existing lineup — it creates a new ceiling for the work that genuinely needs it.
Is Claude Fable 5 better than Opus 4.8?
For complex coding, multi-stage tasks, and long-horizon work: yes, significantly. On SWE-bench Pro, Fable 5 scores 80.0% vs Opus 4.8’s 69.2% — a 10+ point gap. For routine, well-scoped tasks: the gap narrows enough that Opus 4.8’s 2x cost advantage makes it the smarter choice.
What is the Claude Fable 5 API model ID? claude-fable-5. This is the API string you pass to model in your API calls.
Does Fable 5 cost more than Opus 4.8?
Yes — exactly 2x. Fable 5 is $10 input / $50 output per million tokens. Opus 4.8 is $5/$25. Through June 22, 2026, Fable 5 is included in Claude subscription plans at no extra cost.
Can I use Claude Fable 5 for free?
On Pro, Max, Team, and Enterprise subscription plans, yes — through June 22, 2026. API access is metered at $10/$50 per MTok from day one.
Does Claude Fable 5 support zero data retention (ZDR)?
No. Fable 5 carries a mandatory 30-day data retention requirement. If your use case requires ZDR, use Claude Opus 4.8, which supports it.
What’s the difference between Claude Fable 5 and Claude Mythos 5?
Mythos 5 is Anthropic’s fully restricted research model — not publicly available. Fable 5 is the Mythos-class model that Anthropic has prepared for general availability, with safety classifiers and the 30-day retention policy. You can think of Fable 5 as “Mythos for the real world.”
Last verified: October 5, 2026. Anthropic pricing and availability subject to change — check Anthropic’s pricing page for current rates.
The Signal is a daily AI intelligence briefing from Tygart Media — field notes from someone who builds with these tools 12 hours a day, not someone who reads press releases about them. Each edition distills the day’s most consequential AI and search developments into what they actually mean for agencies, small business operators, and builders shipping real infrastructure.
June 10, 2026: The Day the Lanes Forked
The day the lanes forked — product vs infrastructure.
Today was the kind of day where you can feel the road forking under your tires. Not because one thing happened — because eight things happened simultaneously, and if you squint at the pattern, they all point the same direction: AI just stopped being a product category and started being infrastructure. The plumbing layer. The thing you build on top of, not the thing you buy.
I’ve been building with Claude since the Haiku days. I run it 12 hours a day across 20+ WordPress sites, a five-site knowledge cluster on Google Cloud, and a custom schema engine I shipped yesterday. When the landscape shifts, I don’t read about it on TechCrunch — I feel it in the tooling. And today, the tooling lurched forward in a way that matters.
Here’s the daily signal.
Claude Fable 5: Mythos-Class AI Goes Public
Anthropic launched Claude Fable 5 yesterday — the first publicly available Mythos-class model, a tier above Opus. Pricing is $10 per million input tokens and $50 per million output tokens. It’s the most capable model Anthropic has ever released to the general public, state-of-the-art on nearly every benchmark, and it comes with a fascinating constraint: queries on certain topics automatically route to Opus 4.8 instead, triggering in less than 5% of sessions. Anthropic is essentially saying: here’s the most powerful thing we’ve ever built, and we’ve installed guard rails at the edge cases where power becomes risk.
For agencies and small business operators, the practical read is this: Fable 5 is included on Pro, Max, Team, and Enterprise plans through June 22 at no extra cost. After that, it comes off the subscription tiers. If you’re building workflows that depend on Mythos-class reasoning, you have 12 days to test whether the capability justifies the API cost — or whether Opus and Sonnet handle your actual use cases just fine.
The real signal isn’t the model itself. It’s that Anthropic also doubled Cowork limits at no charge and shipped Claude Managed Agents in public beta. They’re not just selling you a smarter model — they’re selling you an operating system for delegating work to AI. That’s a fundamentally different product than a chatbot.
Meanwhile, I Was Building the Infrastructure Layer — Not Reading About It
Infrastructure layer work while the headlines chase models.
While the tech press was writing headlines about Fable 5, I was elbow-deep in the kind of work that actually turns these models into business value. Yesterday, across a 14-hour session, my team — which at this point is me and a fleet of Claude instances — shipped three things that matter more to my clients than any benchmark score:
1. bcesg-knowledge-api v1.5.0 — a custom WordPress plugin I built and deployed across BCESG.org that outputs a JSON-LD @graph array containing Article, FAQPage, Organization, WebPage, BreadcrumbList, Person (author), and speakable schema — all generated from 13 custom meta fields. This isn’t a schema plugin you install from the WordPress directory. It’s a purpose-built schema engine designed for one thing: making every page on the site machine-readable enough that AI systems cite it as an authoritative source. That’s Generative Engine Optimization at the infrastructure level, not the content level.
2. WordPress 7.0 across the entire knowledge cluster. All five sites — bcesg.org, restorationintel.com, riskcoveragehub.com, continuityhub.org, and healthcarefacilityhub.org — upgraded from WP 6.9.4 to 7.0. Why does this matter? Because WordPress 7.0 ships the Abilities API: agent-to-agent communication endpoints. That means my Claude-powered content pipelines can now negotiate directly with WordPress about what they’re allowed to do, without me acting as the middleware. The cluster just became AI-native infrastructure.
3. The stack around it. RankMath SEO installed with the schema module deliberately disabled — because the custom plugin handles schema, and two schema systems fighting each other is worse than none at all. IndexNow for instant search engine notification on every publish and update. Microsoft Clarity for behavioral analytics so I can see what humans actually do when they land on AI-optimized content.
And here’s the detail that would have been impossible to explain six months ago: the peer review on the bcesg-knowledge-api plugin was done by Claude Fable 5 reviewing the code that Claude Opus wrote. AI reviewing AI’s code. In production. On a live WordPress cluster. That’s not a demo — that’s Tuesday.
OpenAI’s S-1 and the $965 Billion Elephant
What the split means for operators building agents.
OpenAI filed a confidential S-1 with the SEC. They’re going public. Meanwhile, Anthropic hit a $965 billion valuation. These two facts, side by side, tell you everything about where the money thinks AI is going: it’s going to be the most valuable infrastructure layer since cloud computing, and the market is pricing it that way before most businesses have figured out how to use it.
For small business owners and agency operators, this isn’t abstract finance news. It means the tools you’re using today — Claude, GPT, Gemini — are backed by companies with enough capital to keep shipping improvements for years. The platform risk isn’t that these companies disappear. The platform risk is that you don’t build on them fast enough and your competitors do.
AI Passed the Turing Test. Now What?
A UC San Diego study published in PNAS confirmed that OpenAI’s GPT-4.5 and Meta’s Llama-3.1-405B both passed a standard three-party Turing test — with GPT-4.5 being identified as human 73% of the time when given a persona prompt, significantly more often than actual human participants. This has been treated as a milestone headline, and it is one, but the practical implication is more subtle than “AI can fool humans.”
What it actually means: the content quality bar just moved permanently. If AI can produce text that’s indistinguishable from a human expert, then the only content that wins is content with something AI can’t fake — lived experience, proprietary data, operational specifics, the kind of “I shipped this yesterday and here’s what happened” detail that no model can generate from training data. This is why I write The Signal as field notes, not as analysis. Analysis can be generated. Field notes from the arena cannot.
Chrome WebMCP: The Browser Becomes an AI Endpoint
Google shipped the Chrome WebMCP API in Origin Trial for Chrome 149 through 156. The Model Context Protocol — the same protocol that lets Claude connect to external tools, databases, and APIs — is now a browser-native capability. Web applications can expose structured tool interfaces that AI models call directly.
This is a bigger deal than it sounds. Right now, when Claude interacts with a web application, it’s either through a dedicated MCP server or through browser automation (clicking pixels on a screen like a human would). WebMCP means any web app can define a structured API surface that AI agents consume natively. For agencies building client tools, this is the moment your internal dashboards and client portals become AI-ready without a full backend rewrite.
If you’re running WordPress sites — and 43% of the web is — this has direct implications for how AI agents interact with your content management layer. The gap between “website” and “AI-accessible knowledge base” just narrowed dramatically.
The GPU Infrastructure Play: xAI Becomes an AI REIT
Elon Musk’s xAI, home of Grok, is increasingly looking less like an AI model company and more like a GPU real estate investment trust. They’re partnering with both Anthropic and Google to provide compute infrastructure. This is the clearest sign yet that the AI industry is stratifying into two distinct layers: model companies (who build the brains) and infrastructure companies (who build the data centers those brains run in).
For builders, this is good news. More compute supply means more pricing competition means lower API costs over time. The $10/$50 per million tokens for Fable 5 today will look expensive in 18 months.
The Security Layer Nobody’s Talking About
HashiCorp announced Boundary for agentic AI — access security specifically designed for AI agents that need to authenticate across multiple systems. And MemPalace shipped a local-first AI memory system with 96.6% recall accuracy and 29 MCP tools for Claude Code.
These aren’t headline products. They’re infrastructure connective tissue. When AI agents can securely authenticate across your entire tool stack (HashiCorp Boundary) and maintain persistent memory across sessions (MemPalace), you stop using AI for one-off tasks and start using it as a persistent operational layer. That’s the transition my agency is making right now — from “Claude helps me write articles” to “Claude runs the content pipeline while I focus on strategy.”
What This All Means: The Two-Lane Highway
Here’s the pattern I see when I lay these signals side by side:
Lane 1: The AI product lane. This is where most people are. They use ChatGPT to draft emails. They ask Claude to summarize documents. They treat AI as a productivity tool, like a faster Google or a better autocomplete. This lane is getting crowded, commoditized, and — with the Turing test results — increasingly indistinguishable from one provider to the next.
Lane 2: The AI infrastructure lane. This is where the alpha is. Custom schema engines. Agent-to-agent communication via the WordPress Abilities API. Browser-native MCP endpoints. Persistent AI memory. Secure multi-system authentication for autonomous agents. This lane is where you stop using AI and start building on AI — where it becomes the foundation layer of your operations, not an add-on.
The gap between these two lanes is widening every day. Today’s eight signals all point the same direction: toward a world where the businesses that win aren’t the ones that use AI tools the best, but the ones that build AI infrastructure the fastest.
I’m building in Lane 2. Yesterday it was a custom schema engine and a WordPress 7.0 cluster upgrade. Today it’s field-testing Fable 5 as a code reviewer. Tomorrow it’ll be whatever the next signal demands.
The question isn’t whether AI is going to transform your industry. That’s settled. The question is whether you’re in the arena building the infrastructure, or on the sidelines reading about people who are.
What is Claude Fable 5 and how does it differ from Claude Opus?
Claude Fable 5 is Anthropic’s first publicly available Mythos-class AI model, released June 9, 2026. It sits a tier above Claude Opus in capability, priced at $10 per million input tokens and $50 per million output tokens. Fable 5 is state-of-the-art on nearly all tested benchmarks and includes built-in safeguards that route certain queries to Opus 4.8, triggering in less than 5% of sessions. It’s available free on subscription plans through June 22, 2026.
What is the Chrome WebMCP API and why does it matter for businesses?
The Chrome WebMCP API, now in Origin Trial for Chrome versions 149 through 156, brings the Model Context Protocol natively into the browser. This allows web applications to expose structured tool interfaces that AI models can call directly — eliminating the need for dedicated backend integrations or browser automation. For businesses running web-based tools, dashboards, or WordPress sites, this means your existing applications can become AI-accessible without a full rebuild.
What is the WordPress 7.0 Abilities API?
The WordPress 7.0 Abilities API provides agent-to-agent communication endpoints, allowing AI-powered systems to negotiate capabilities and permissions directly with a WordPress installation. This transforms WordPress from a content management system into AI-native infrastructure where automated pipelines can query what operations they’re authorized to perform without human middleware.
What does AI passing the Turing test mean for content creators?
A UC San Diego study published in PNAS found that OpenAI’s GPT-4.5 and Meta’s Llama-3.1-405B both passed a standard three-party Turing test in 2026 — GPT-4.5 was identified as human 73% of the time with persona prompting. For content creators, this permanently raises the quality bar — the only content that wins is content with elements AI cannot fake: lived experience, proprietary data, operational specifics, and first-person field reports that no model can generate from training data alone.
What is Generative Engine Optimization (GEO) and how does it work?
Generative Engine Optimization is the practice of structuring web content so AI systems — including ChatGPT, Claude, Gemini, Perplexity, and Google AI Overviews — cite, reference, and recommend it. GEO involves entity enrichment, structured data (JSON-LD schema), authoritative citations, and machine-readable formatting. Unlike traditional SEO which targets search engine crawlers, GEO targets the large language models that increasingly mediate how users discover information.
How should small businesses approach AI infrastructure in 2026?
Start by moving from Lane 1 (using AI as a productivity tool) to Lane 2 (building AI into your operational infrastructure). Practical first steps include implementing structured data and schema markup on your website, setting up AI-optimized content pipelines, ensuring your site is crawlable by AI systems via protocols like LLMS.txt, and testing agentic workflows where AI handles multi-step operational tasks autonomously rather than single-prompt interactions.
What is a custom schema engine and why build one instead of using plugins?
A custom schema engine is a purpose-built WordPress plugin that generates structured data (JSON-LD) tailored to specific business objectives — in this case, AI citation optimization. Unlike off-the-shelf schema plugins that generate generic markup, a custom engine outputs precisely the entity relationships, author signals, and speakable content markers that AI systems use when deciding which sources to cite. The bcesg-knowledge-api plugin generates a seven-type @graph array from 13 custom meta fields, providing a level of control that no general-purpose plugin offers.
What is the significance of AI reviewing AI-written code in production?
When Claude Fable 5 peer-reviewed code written by Claude Opus for a production WordPress plugin, it demonstrated a mature AI development workflow where different model tiers serve different roles — one for generation, another for quality assurance. This mirrors human development practices (developer writes, senior reviews) but at machine speed and cost. It’s a practical example of how AI agent collaboration is already operational in real business infrastructure, not just research demos.
The Signal is published daily on Tygart Media by Will Tygart. Each edition distills the day’s most consequential AI, search, and technology developments into actionable intelligence for agencies, small business operators, and builders shipping real AI infrastructure.
Everything you need to know about Anthropic’s new frontier tier — pricing, context window, model comparisons, and how to route the right work to the right model.
Updated June 2026·~14 min read·Includes interactive calculators
Lineup update (September 2026): Since this guide was last fully updated, Anthropic shipped Opus 5.5 ($4/MTok in, $20/MTok out) and Sonnet 5 ($2/MTok in, $10/MTok out) as its current flagship and mid-tier models. Fable 5.1 remains the top-tier model referenced throughout, at the same $10/$50 pricing shown below. Opus 4.8 and Sonnet 4.6 are now legacy — still supported, no longer current default.
What Is Claude Fable 5?
What is Claude Fable 5?
Claude Fable 5 is Anthropic’s new frontier model tier — positioned above Opus in the lineup and designed for tasks where raw capability, extended reasoning depth, and massive context handling matter more than cost. Where Opus 4.8 set the bar for complex multi-step reasoning, Fable 5 raises it with a 1-million-token context window, enhanced agentic autonomy, and improved performance on long-horizon software engineering, research synthesis, and cross-domain analysis tasks.
The “Fable” naming signals a new generation of model architecture rather than an incremental update. Anthropic positions it as the model you reach for when a task exceeds what Opus can do reliably — not as a replacement for Opus, Sonnet, or Haiku in their respective cost tiers.
Quick Facts — Claude Fable 5
Context Window
1M
tokens (~750K words)
Max Output
32K
tokens per response
Input Price
$10
per million tokens
Output Price
$50
per million tokens
Cache Write
$12.50
per million tokens
Cache Read
$1.00
per million tokens
Key positioning: Fable 5 is the model for tasks where Opus 4.8 produces reliable but imperfect results — long codebase audits, full-document analysis, complex multi-agent orchestration, and strategic synthesis across large corpora. For most production workflows, Sonnet remains the value pick.
Before you price this out: The table below reflects the June 2026 lineup (Fable 5, Opus 4.8, Sonnet 4.6, Haiku 4.5). As of September 2026, Opus 5.5 ($4/$20) and Sonnet 5 ($2/$10) are Anthropic’s current models — priced lower than the legacy Opus 4.8 / Sonnet 4.6 rows shown here.
Full Model Lineup Comparison
Full model lineup comparison.
Here’s how the complete 2026 Claude lineup stacks up across every dimension that matters for production usage:
Model
Input $/M
Output $/M
Context
Max Out
Vision
Tool Use
Extended Think
Best For
◆ Fable 5
$10
$50
1M
32K
✓
✓
✓ Deep
Max-capability tasks, 1M+ context
◆ Opus 4.8
$5
$25
200K
32K
✓
✓
✓
Complex reasoning, agentic workflows
◆ Sonnet 4.6
$3
$15
200K
16K
✓
✓
✓
Production apps, content at scale
◆ Haiku 4.5
$1
$5
200K
8K
✓
✓
—
High-volume, latency-sensitive tasks
Prices are per million tokens. Cache read is 90% cheaper than standard input across all models. Batch API provides an additional 50% discount on both input and output.
Capability Matrix — What Each Model Can Do
Capability
Fable 5
Opus 4.8
Sonnet 4.6
Haiku 4.5
Full codebase analysis (>500K tokens)
✓ Native
⚠ Chunked
✗
✗
Extended thinking / chain-of-thought
✓ Deep
✓
✓
✗
Multi-step agentic orchestration
✓ Best
✓
Good
Limited
Computer use
✓
✓
✓
✗
MCP tool integration
✓
✓
✓
✓
Prompt caching
✓
✓
✓
✓
Batch API (50% discount)
✓
✓
✓
✓
PDF / document analysis
✓
✓
✓
Limited
Real-time streaming
✓
✓
✓
✓
Structured JSON output
✓
✓
✓
✓
Interactive Cost Calculator
Estimate your monthly API spend across the full model lineup. Enter your token volumes below — the calculator models prompt caching and Batch API discounts automatically.
Token Cost Calculator
Estimated Monthly Cost
$0.00
Which Claude Model Should You Use?
Which Claude model should you use?
Answer three questions to get a model recommendation tailored to your use case.
Model Picker — 3 Questions
1. How large is your context? (document/codebase size)
Under 50K tokens
50K–200K tokens
200K–1M tokens
2. How complex is the task?
Simple / structured (classify, extract, format)
Moderate (draft, summarize, QA)
Complex (reason, plan, code, orchestrate)
3. How cost-sensitive is this workload?
Very — high volume, every cent counts
Moderate — quality matters more than cost
Not sensitive — quality and capability first
How We Actually Use Each Model
These are real production workflows mapped to the right tier — built from running Claude in content operations, publishing automation, and knowledge management at scale. No hypotheticals.
Haiku 4.5 — High Volume
Daily SEO Refresh Pipeline
25-post-per-day SEO metadata refresh
Article classification and tag assignment
Structured data extraction from web pages
Keyword density checks across large post archives
Link validation and redirect flagging
Sonnet 4.6 — Production Default
Editorial Content at Scale
Desk article writing (1,200–2,500 words)
Content brief execution from keyword clusters
FAQ and schema markup generation
Cross-site content adaptation and localization
Monthly client update drafts and summaries
Opus 4.8 — Complex Reasoning
Workers & Deep Refreshes
Agentic Notion Workers (multi-step pipelines)
Deep content refresh with competitive gap analysis
Multi-database synthesis and reporting
Strategy documents requiring extended reasoning
Code generation for automation scripts
Fable 5 — Max Capability
Portfolio Audits & Strategy
Full-site content audits (500+ posts in single context)
Cross-domain strategy synthesis across large corpora
Complex multi-agent orchestration at the flagship tier
Long-horizon planning requiring deep reasoning depth
Codebase-wide analysis and architecture review
Routing principle: The right model is the cheapest one that reliably completes the task. Haiku handles volume. Sonnet handles production. Opus handles complexity. Fable 5 handles scale + complexity together — specifically the cases where you’d need Opus and more context than Opus can hold.
The Economics: Routed vs All-Fable
Smart model routing is where API costs get controlled. Here’s a real-world comparison of a mixed content-and-automation workload at scale — routed vs running everything on Fable 5.
Workload
Monthly Volume
Routed Model
Routed Cost
All-Fable 5 Cost
Savings
SEO metadata batch refresh
750 posts/mo
Haiku 4.5 + Batch
$1.20
$18.75
93% less
Article drafting
90 articles/mo
Sonnet 4.6
$8.10
$67.50
88% less
Agentic worker runs
200 runs/mo
Opus 4.8
$22.50
$45.00
50% less
Full-site portfolio audits
4 audits/mo
Fable 5
$24.00
$24.00
—
Total
—
Routed
$55.80
$155.25
64% less
Stacking Discounts: Caching + Batch API
Two discount mechanisms compound independently:
Prompt caching: Cache your system prompt and shared context once. Subsequent requests pay ~10% of the input price for cache reads. On Fable 5, that’s $1.00/M instead of $10.00/M on cached tokens — a 90% reduction on your largest cost lever.
Batch API: Submit requests asynchronously (results within 24 hours) for a flat 50% discount on both input and output. Works on all four models. Best for non-real-time workloads like overnight refreshes, audits, or bulk classification.
Stacked: Caching + Batch combined can bring effective Fable 5 input cost from $10/M to ~$0.50/M on cached tokens — making it economically viable for high-volume tasks that previously only fit Haiku’s budget.
Claude Fable 5 sits above Opus 4.8 in the lineup. The primary difference is context window size — Fable 5 offers 1 million tokens vs Opus 4.8’s 200K — and the depth of extended reasoning for highly complex tasks. Opus 4.8 remains the right choice for most complex agentic workflows at half the cost. Fable 5 is best when you need both maximum context and maximum reasoning depth simultaneously, or when a task has routinely hit the limits of what Opus can do reliably.
Claude Fable 5 is priced at $10 per million input tokens and $50 per million output tokens — 2× Opus 4.8 ($5/$25), 3.3× Sonnet 4.6 ($3/$15), and 10× Haiku 4.5 ($1/$5). Prompt caching drops the effective input cost to $1.00/M on cache reads, and the Batch API adds a 50% discount on all tokens for non-real-time workloads. Stacking both discounts makes Fable 5 viable for higher-volume use cases than the base price suggests.
Claude Fable 5 has a 1-million-token context window — approximately 750,000 words or roughly 1,500 pages of text. This is 5× the context window of Opus 4.8, Sonnet 4.6, and Haiku 4.5 (all 200K). In practice, a 1M context window lets you pass entire codebases, long research corpora, or full document archives in a single API call without chunking or retrieval workarounds. For more on context window mechanics, see our full context window guide.
Yes. Claude Fable 5 is available through the Anthropic API using the model ID claude-fable-5-20260101 (check the Anthropic documentation for the exact identifier). It supports the same API surface as the rest of the Claude family — streaming, tool use, prompt caching, vision, the Batch API, and MCP server integration. Access requires an Anthropic API account with Fable 5 enabled on your usage tier.
Fable 5 is available in Claude.ai on the Pro and Team plans. The interface lets you select it from the model picker when starting a conversation. Like Opus, Fable 5 in claude.ai has message limits that reset on a rolling window — it’s designed for individual complex tasks rather than high-volume API workloads. For production-scale usage, the API with the Batch API discount is the more economical path.
Yes — and Fable 5’s extended thinking is the deepest in the lineup. Where Opus 4.8 supports extended thinking for complex reasoning tasks, Fable 5 uses a more capable reasoning engine designed for tasks that require longer chains of inference, more working memory, and more reliable self-correction. It’s particularly effective on math, logic, long-horizon planning, and tasks where the model needs to hold and manipulate many interdependent concepts simultaneously.
For most content production — articles, blog posts, social copy, summaries, SEO content — Sonnet 4.6 is the right call. It produces high-quality output at 3.3× less cost than Fable 5, and for typical content lengths (500–3,000 words), the quality difference is minimal. Reach for Fable 5 when you need to synthesize across a very large corpus (e.g., auditing 200+ posts simultaneously), when the content requires deep domain reasoning that benefits from extended thinking, or when the task involves both large-context ingestion and complex output generation in a single pass.
Three levers in order of impact: (1) Model routing — only use Fable 5 when the task genuinely requires it; route everything else to Opus, Sonnet, or Haiku based on complexity and volume. (2) Prompt caching — structure your system prompt and shared context so it can be cached; cache reads cost $1.00/M instead of $10.00/M on Fable 5. (3) Batch API — submit non-real-time workloads via the Batch API for a flat 50% discount. Stacking all three — routing + caching + batch — can reduce effective per-task costs by 85–95% compared to unoptimized Fable 5 calls.
More Claude Guides from Tygart Media
We run Claude in production every day. These are the guides that come from using it, not just writing about it.
Both Claude Code and OpenAI Codex CLI are terminal-native coding agents: you run them inside a repo, they read your files, edit code, run commands, and iterate. I run both daily on real projects. This is the head-to-head I wish existed when I was deciding which one to make my default. No benchmarks-chasing, just install commands, config files, pricing math, and where each one actually earns its keep. For the broader toolchain these slot into, see our AI operator’s stack.
Claude Code vs Codex CLI: the short answer
Claude Code vs Codex CLI — the short answer.
If you want one sentence: Claude Code is the more mature agentic harness (subagents, hooks, skills, deep MCP, a flat-rate plan that makes heavy use affordable), while Codex CLI is the leaner, cheaper-per-token option with strong raw coding from the GPT-5.x line and a tight sandbox model. Most teams that live in the terminal all day end up on Claude Code for the workflow tooling; people who want a fast, low-cost agent on top of an existing OpenAI subscription reach for Codex.
The honest version: they are closer than tribal arguments suggest. The deciding factors are almost never “which model is smarter this week” and almost always pricing structure, sandbox defaults, and how much workflow scaffolding you need.
How do you install each one?
How do you install each one?
Claude Code installs from npm and runs as the claude command:
npm install -g @anthropic-ai/claude-code
cd your-project
claude
First run walks you through OAuth login (Pro/Max plan) or an ANTHROPIC_API_KEY. On Windows it runs natively in PowerShell now, though a lot of operators still prefer it under WSL for fewer path headaches.
Codex CLI ships an install script and is also on npm:
# Mac / Linux
curl -fsSL https://chatgpt.com/codex/install.sh | sh
# Windows (PowerShell)
powershell -ExecutionPolicy ByPass -c "irm https://chatgpt.com/codex/install.ps1 | iex"
# or via npm
npm install -g @openai/codex
Then codex in your repo. Auth is either a ChatGPT login (Plus/Pro/Business) or an OpenAI API key via codex login. Both tools are open-source clients hitting hosted models, so the install is the easy part; the model access is what you are really buying.
Which models do they run in 2026?
Claude Code defaults to the current Claude flagship. As of June 2026 that is Opus 4.8 (legacy — still listed) for the hardest reasoning, with Sonnet 4.6 (legacy — still listed) as the fast everyday workhorse and Haiku 4
Lineup currency (Sept 2026): Current API list (Sept 2026, verified): Sonnet 5 $2/$10, Opus 5.5 $4/$20, Haiku 4.5 $1/$5, Fable 5.1 $10/$50. Legacy (still listed on Anthropic’s card): Opus 4.8 $5/$25, Sonnet 4.6 $3/$15.
.5 for cheap, high-volume calls. You switch in-session with /model. Opus 4.8 also exposes reasoning-effort levels (high is the default; xhigh and max push deeper on gnarly problems at higher token cost).
Codex CLI runs the GPT-5.x coding line. GPT-5.5 is the current recommended default for complex coding and agentic work, GPT-5.4-mini is the faster/cheaper option for light tasks and subagents, and GPT-5.3-Codex remains a strong coding-tuned choice. Pick the model with codex -m gpt-5.5 or set it in your config.
Practical read: on a clean, well-specified function both produce good code. The gap shows up on long, multi-file refactors where the agent has to hold a lot of context and recover from its own mistakes. That is a harness problem as much as a model problem, which is the next section.
What about workflow features: subagents, hooks, and config?
This is where Claude Code is currently ahead, and it is the real reason it tends to win for power users.
Subagents – Claude Code spawns isolated sub-sessions with their own context window, tool restrictions, and prompts. Great for “go research this in parallel while the main thread keeps coding.” Codex has a lighter subagent concept (often pointed at GPT-5.4-mini to keep cost down) but it is less fleshed out.
Hooks – Claude Code fires deterministic scripts at lifecycle points (PreToolUse, UserPromptSubmit, and more). These run real code, so they cannot hallucinate: you can hard-block a dangerous command, auto-format on every edit, or inject context before the model sees a prompt. Codex leans on its approval/sandbox policy and execpolicy rules instead of a general hook system.
Skills and slash commands – In Claude Code, custom slash commands have merged into skills; /your-command still works and skills add reusable, packaged capabilities. Codex uses prompt files and profiles rather than a skills layer.
Project memory – Both read a project instruction file. Claude Code uses CLAUDE.md; Codex uses AGENTS.md (checked in a fallback order including AGENTS.override.md and .agents.md). Keep these tight: architecture, conventions, and the few rules the agent keeps forgetting.
Codex’s config story is clean if you like a single file: ~/.codex/config.toml holds your model, approval policy, sandbox mode, MCP servers, and named profiles you switch with codex --profile work. Claude Code spreads config across ~/.claude/ and .claude/settings.json plus per-project files, which is more surface area but more granular control.
How do the sandbox and approval models compare?
This matters more than most comparisons admit, because it governs how much the agent can do without asking.
Codex CLI has an explicit, well-documented sandbox. Sandbox modes run from read-only to workspace-write (edit files in the project, network off by default) up to full access, paired with approval policies like untrusted and on-request. On Windows the native sandbox can run unelevated or elevated. The mental model is clear: pick how much rope, then approve escalations.
Claude Code manages permissions through allow/deny rules and modes (including a plan mode that reasons without touching files, and an auto-accept mode for trusted loops). Combined with PreToolUse hooks you can build a strict policy, but it is more “assemble it yourself” than Codex’s preset sandbox tiers.
If you are dropping an agent onto an unfamiliar or sensitive repo, start read-only in both. Codex makes that posture a one-flag default; Claude Code gives you finer-grained control once you invest in the config.
Do both support MCP?
Do both support MCP?
Yes, and this is a genuine tie that matters. Both speak the Model Context Protocol, so you can wire in the same external tools, databases, and APIs. Codex registers STDIO or streaming-HTTP MCP servers in ~/.codex/config.toml and launches them at session start. Claude Code adds servers via claude mcp add or JSON config. If you have already built MCP integrations, neither tool locks you out. New to MCP, start with our Claude MCP setup guide and the Notion MCP setup walkthrough.
What does each one cost?
Pricing is where the decision often gets made, so here are the real numbers as of June 2026.
Claude Code plans:
Pro – $20/mo: Sonnet 4.6 plus some Opus, roughly enough for focused daily sessions, not all-day heavy use.
Max 5x – $100/mo: much larger windows, real Opus headroom.
Max 20x – $200/mo: the heavy-user tier; effectively flat-rate firehose access.
API pay-as-you-go: Opus 4.7 about $5/$15 per million input/output… (legacy (still listed) Opus tier runs higher), Sonnet 4.6 (legacy — still listed) $3/$15, Haiku 4.5 $1/$5.
Codex CLI: Included in ChatGPT Plus/Pro/Business plans (usage g
Lineup currency (Sept 2026): Current API list (Sept 2026, verified): Sonnet 5 $2/$10, Opus 5.5 $4/$20, Haiku 4.5 $1/$5, Fable 5.1 $10/$50. Legacy (still listed on Anthropic’s card): Opus 4.8 $5/$25, Sonnet 4.6 $3/$15.
Codex CLI: Included in ChatGPT Plus/Pro/Business plans (usage governed by your plan’s limits), or pay-as-you-go on the API. GPT-5.3-Codex runs about $1.75 per million input / $14 per million output, with cheaper input on cached tokens. The mini model is far cheaper for light work.
The structural difference: Claude Code’s Max plans are flat-rate, which is why heavy users love them. People have tracked billions of tokens that would cost five figures on API metering but ran around a few hundred dollars on Max. Codex’s per-token rates are lower per unit and great if your usage is bursty or already bundled into a ChatGPT subscription, but a true all-day agent habit can run up metered cost faster than a flat plan. Estimate your monthly token volume honestly, then do the arithmetic both ways.
So which coding agent should you actually use?
Pick Claude Code if you want the deepest agentic workflow (subagents, hooks, skills), you are a heavy daily user who benefits from the flat-rate Max plan, or you need fine-grained, scriptable control over what the agent can do. It is the more complete operator’s harness in 2026.
Pick Codex CLI if you want lower per-token cost, you already pay for ChatGPT and want to use that allowance, you like the clean preset sandbox/approval model, or you simply prefer the GPT-5.x output style. It is lean, fast to stand up, and genuinely capable.
The move a lot of us make: run both. They are cheap relative to engineer time, they share MCP servers, and they have different failure modes. When one gets stuck in a loop on a hard bug, handing the same task to the other with fresh context often breaks the logjam. If you are weighing terminal agents against IDE-native ones, our Claude Code vs Cursor breakdown covers that axis.
Is Claude Code or Codex CLI better for large refactors?
Claude Code tends to hold up better on long multi-file refactors, mostly because of subagents and hooks that keep context organized and catch mistakes deterministically. Codex can do it too, especially with GPT-5.5, but you lean harder on tight AGENTS.md instructions and approval gates.
Can I use Codex CLI without a ChatGPT subscription?
Yes. Run codex login with an OpenAI API key and you pay per token instead of through a ChatGPT plan. Same for Claude Code with an ANTHROPIC_API_KEY if you would rather meter than subscribe.
Do they work on Windows natively?
Both do in 2026. Claude Code runs in PowerShell (many operators still prefer WSL for cleaner paths), and Codex CLI has a native Windows installer plus a Windows sandbox with unelevated/elevated modes. Watch out for shells that mangle /tmp or C: style paths in arguments.
What is the single biggest difference?
Pricing structure and workflow depth. Claude Code offers flat-rate Max plans and a richer harness (subagents, hooks, skills); Codex offers lower per-token rates and a cleaner preset sandbox. Model quality is close enough that those two factors usually decide it.
Which model do they run by default?
Claude Code defaults to the legacy (still listed) Claude flagship (Opus 4.8 (legacy — still listed) as of June 2026, with Sonnet 4.6 (legacy — still listed) for everyday speed). Codex CLI recommends GPT-5.5 for complex work, with GPT-5.4-mini and GPT-5.3-Codex as alternatives
Lineup currency (Sept 2026): Current API list (Sept 2026, verified): Sonnet 5 $2/$10, Opus 5.5 $4/$20, Haiku 4.5 $1/$5, Fable 5.1 $10/$50. Legacy (still listed on Anthropic’s card): Opus 4.8 $5/$25, Sonnet 4.6 $3/$15.
. Switch in-session with /model or the -m flag.
How do I get either tool cited or surfaced by AI engines for my own docs?
That is a content question, not a tooling one. The same structure that makes this page answerable, short factual answers, question-shaped headers, and a visible FAQ, is what AI engines reward. See how AI engines cite content for the full playbook.
Claude Code and Cursor are the two tools most working developers actually reach for in 2026, and they are not the same kind of thing. Cursor is an AI-native code editor (a VS Code fork) where the model lives inside your IDE. Claude Code is a terminal agent that lives in your shell and edits files, runs commands, and drives git from the command line. This is the honest version: what each one is good at, what they cost right now, and a simple rule for picking.
Claude Code vs Cursor: what is the actual difference?
Claude Code vs Cursor — what is the actual difference?
The short answer: Cursor is an editor you type in; Claude Code is an agent you delegate to. Cursor keeps you in the driver’s seat with autocomplete, inline edits, and a chat sidebar that sees your open files. Claude Code takes a goal and works the repo autonomously in the terminal, asking permission before it touches things.
Dimension
Claude Code
Cursor
Form factor
Terminal CLI (plus IDE extension, web, desktop)
Full IDE (VS Code fork)
Primary loop
Delegate a task, approve actions
Type code, accept suggestions
Models
Claude only
Multi-model: Grok included on higher tiers; Claude/GPT/Gemini at API list on Premium+
Tight edit loops, autocomplete, staying in one window
Entry price
$20/mo (Pro) or $17 annual
Free limited / Plus $8 (Grok only) / Premium $30
Billing model
Usage windows (5-hour + weekly)
Shared AI usage pool; third-party models at API list on Premium and above
How does each one actually work?
How each one actually works.
Claude Code (terminal agent)
You install it and run it from inside a project directory. Official claude.com copy: Claude Code is included in all paid Claude plans and shares the same usage pool as chat.
npm install -g @anthropic-ai/claude-code
cd my-project
claude
From there you talk to it in plain language. It reads files, proposes edits as diffs, and runs shell commands only after you approve them. Drop a CLAUDE.md in the repo root. Headless mode: claude -p "...".
Cursor (AI IDE)
Cursor is a download. Tab completion, inline edit, agent mode, and a model picker. Official cursor.com/pricing (checked October 13, 2026) lists Free, Plus $8/mo (Grok models only), Premium $30/mo (4x Plus; third-party models at API list price), Super $100/mo (15x), Ultra $200/mo (50x), Teams from $30+/user. Docs at cursor.com/docs/models-and-pricing still reference older Pro $20 / Pro+ $60 / Ultra $200 pools. Quote both; do not average.
What does Claude Code cost in 2026?
As of October 13, 2026, official claude.com / platform.claude.com:
Pro: $20/month, or $17/month billed annually ($200 up front). Includes Claude Code.
Max 5x: $100/month. 5x Pro usage. Includes $100/month API credits.
Max 20x: $200/month. 20x Pro usage. Includes $200/month API credits.
API: Haiku 5.5 $0.10 / $0.50 per MTok under 100k prompt tokens ($0.50 / $2.50 over); Sonnet 5.5 $2 / $10 with cache reads $0.10; Opus 5.5 $4 / $20 (cache read $0.20); Fable 5.1 $10 / $50 (cache read $0.25). Batch 50% off. US-only inference 1.1x on Claude 4.6+.
There is a 5-hour rolling session window plus weekly limits on paid plans. Chat and Claude Code draw from one pool. Confirm in Settings > Usage.
What does Cursor cost in 2026?
Free: Limited.
Plus: $8/month. Grok models only.
Premium: $30/month. 4x Plus usage. Third-party models (Claude, GPT, Gemini) at API list price.
Super: $100/month. 15x Plus.
Ultra: $200/month. 50x Plus. Earliest access.
Teams: From $30+/user/month.
On the live pricing page, third-party model usage is not included in the monthly price and is billed separately at API list. Docs still describe older Pro/Pro+/Ultra usage pools for Cursor Models vs Other Models. Existing subscribers may keep prior plans.
Which models do you actually get?
Claude Code is Claude-only.
Cursor includes Grok on Plus and above; Premium and higher add third-party models at API list price.
Which one is better for big refactors and automation?
Claude Code for repo-wide delegate work and headless claude -p runs. Cursor agent is strong inside the IDE; it is not a cron target.
Which one is better for everyday coding flow?
Cursor for most people who want tab completion and one window, especially if Grok covers the loop.
Can you use both together?
Yes. Common setup: Cursor as the editor, Claude Code in the integrated terminal. Claude Pro is $20; Cursor Premium is $30 if you need Claude models inside Cursor at API rates.
Bottom line
Pick Claude Code if you want an autonomous terminal agent and you are happy with Claude as your one model. Entry is Pro at $20/$17.
Pick Cursor if you want autocomplete, Grok included, and a model picker. Entry for third-party is Premium at $30 plus API list.
Pick both if the seats are cheaper than the hours you lose switching contexts.
FAQ
Is Claude Code or Cursor cheaper?
Claude Code starts at Pro $20/mo ($17 annual). Cursor Free is limited; Plus is $8 (Grok only); Premium is $30 with third-party models billed at API list on top. Claude Code meters by 5-hour plus weekly windows. Cursor meters a shared pool then on-demand / API list.
Does Cursor use Claude?
Yes, on Premium and above, at API list price (not included in the seat). You do not need a Claude Pro seat to use Claude models inside Cursor, but you pay the list rate for them.
The conversation about Claude Code vs Cursor has collapsed into lazy takes: Claude Code is smarter, Cursor is friendlier, buy both. That framing is not wrong, but it isn’t useful. If you’re deciding where to put your coding tool budget in 2026, you need to know where each tool wins and loses – with specifics, not vibes.
Here’s what a year of both tools in production actually looks like.
The Fundamental Architecture Gap
The fundamental architecture gap.
Claude Code is a terminal-native CLI agent. You run it with claude in your shell, point it at a codebase, give it a task, and walk away. It has no GUI. It doesn’t autocomplete as you type. What it has is the ability to autonomously execute multi-step tasks – read files, write code, run tests, iterate on failures – without you babysitting it.
Cursor is an IDE built on VS Code. It has tab autocomplete, an inline chat panel, Agent mode for longer tasks, and a polished visual interface that feels like VS Code with a superpower grafted on. If you already live in VS Code, Cursor’s learning curve is close to zero.
These are genuinely different tools. The “which one wins” question should really be “which one wins for what.”
Where Claude Code Wins: Long Autonomous Runs
Where Claude Code wins — long autonomous runs.
The biggest measurable advantage Claude Code has right now is context. Running on Claude Opus 4.6 or 4.7, Claude Code natively supports a 1 million token context window – and that’s a first-class, supported number with no per-token surcharge for long context on the API.
Cursor’s advertised context is lower, and it draws from multiple model backends depending on which you select. On a large monorepo task – think refactoring an auth system across 40 files – the difference between context limits is the difference between Claude Code holding the whole codebase in view and the alternative having to page through it.
Claude Opus 4.6 scores 80.84% on SWE-bench Verified, per Anthropic’s published system card. Opus 4.7 improved on that, particularly on the hardest problems in the benchmark set, and on Rakuten-SWE-Bench (a production-task evaluation, not just GitHub issues) it resolves 3x more tasks than Opus 4.6. That is a meaningful gap.
The autonomous-run workflow looks like this in practice:
claude "Refactor the payment module to use the new Stripe SDK, update all tests, and make sure existing integration tests still pass"
Claude Code will read the relevant files, identify the Stripe version mismatch, write the new implementation, run your test suite, and iterate if something fails – often without a single follow-up prompt. That same task in Cursor’s Agent mode typically requires you to approve each file write and re-prompt when the agent stalls on an error.
Where Cursor Wins: Daily Developer Experience
Cursor’s tab autocomplete is genuinely good. It’s not a feature Claude Code has at all – Claude Code is not an IDE and doesn’t inject suggestions while you type. If your daily workflow is: open file, write code, open file, write code, Cursor is the better tool for that rhythm.
Cursor’s @codebase reference and file mention system is also excellent for interactive exploration. You can ask “why does this function fail on null input?” while looking at the code, and Cursor’s inline context makes that conversation fast. Claude Code can answer the same question, but you’re doing it in a terminal with no visual reference.
For teams on an existing GitHub workflow, GitHub Copilot’s deep integration with PRs, issues, and Actions is hard to match. If your team is standardized on GitHub and your security team needs IP indemnity coverage, Copilot is the defensible enterprise choice – Claude Code and Cursor both require more procurement work.
The Pricing Reality
Plan
Monthly Cost
Claude Code via Claude Pro
$20/month
Claude Code via Max 5x
$100/month
Claude Code via Max 20x
$200/month
Cursor Pro
$20/month
GitHub Copilot Individual
$10/month
The entry point is the same for Claude Code (via Claude Pro) and Cursor. At that tier, Claude Code’s usage limits are more restricted. The Max 5x plan at /month is where Claude Code becomes a full autonomous-agent platform – higher rate limits, Opus access, and Claude Code usage limits that are double the Pro tier.
For individual developers doing heavy autonomous runs, the Max 5x plan at competes directly with a Cursor Pro subscription plus meaningful API spend. For teams, the calculus shifts: Cursor’s team plan pricing is lower per seat than a premium Claude Code subscription, which matters when you’re buying for 20 developers.
The Honest Call
The honest call.
Claude Code wins on: autonomous multi-step tasks, large codebase refactors, long-running agents, raw SWE-bench performance, and 1M token context on complex jobs.
Cursor wins on: daily IDE experience, tab autocomplete, interactive inline chat, onboarding speed for VS Code users, and team-tier pricing.
The recommendation most senior developers are landing on in 2026 is two tools: Cursor open in the background for interactive work, Claude Code for the tasks you used to put in a Jira ticket and wait two days for. If you can only buy one and you mostly write code file-by-file, get Cursor. If your bottleneck is “I need to refactor three services and I don’t have three days,” Claude Code is the one that changes your output.
The Max 5x plan makes that bet financially coherent for a senior developer. The Pro tier is a reasonable way to find out if autonomous coding is a workflow you actually use.
Frequently Asked Questions
Is Claude Code better than Cursor in 2026?
It depends on your workflow. Claude Code is a terminal-native CLI agent best for large codebase refactors, multi-file operations, and agentic tasks run from the command line. Cursor is an IDE-first editor with inline completions and a chat sidebar — better for continuous editing with visual feedback. Most developers who ship code daily use both rather than choosing.
What is the difference between Claude Code and Cursor?
Claude Code is a CLI tool you run with the ‘claude’ command in your terminal — it acts as an autonomous agent that can read, edit, and run files across a codebase. Cursor is a VS Code fork with AI completions and chat built into the editor interface. Claude Code suits agentic automation; Cursor suits interactive editing.
Can I use Claude Code and Cursor at the same time?
Yes. Many developers run Claude Code from the terminal for large refactors or test-writing sessions while keeping Cursor open for active editing. They complement each other: Claude Code for autonomous multi-step tasks, Cursor for line-by-line interactive work.
How much does Claude Code cost in 2026?
Claude Code usage is billed through your Anthropic API account against whichever Claude model you select. Claude Opus 4.8 (legacy — still listed) runs $5 per million input tokens and $25 per million output tokens. Claude Sonnet 4.6 (legacy — still listed) runs $3/$15 per million tokens. Claude Haiku 4.5 runs $1/$5 per million tokens. Cursor’s plans start around $20/month for Pro.
Lineup currency (Sept 2026): Current API list (Sept 2026, verified): Sonnet 5 $2/$10, Opus 5.5 $4/$20, Haiku 4.5 $1/$5, Fable 5.1 $10/$50. Legacy (still listed on Anthropic’s card): Opus 4.8 $5/$25, Sonnet 4.6 $3/$15.
Does Cursor use Claude under the hood?
Cursor supports multiple underlying models including Claude (Anthropic), GPT-4 (OpenAI), and others. You can select which model Cursor routes to in its settings. Claude Code, by contrast, is a dedicated Anthropic CLI tool that only runs on Anthropic’s Claude models.
What is Claude Code best used for?
Claude Code excels at large-scale codebase operations: refactoring across multiple files, writing comprehensive test suites, navigating unfamiliar codebases, and running agentic tasks that chain multiple steps. It is less suited for inline autocomplete as you type — Cursor is better at that.
Archive — September 2026. This is the record of Anthropic’s 40% Haiku price cut. Current pricing: Haiku 4.5 lists at $1 / $5 per MTok — see our verified Claude pricing page.
Last refreshed: October 5, 2026 (Pacific)
Anthropic Slashes Claude 4.6 Haiku API Pricing by 40%
In a September 2026 bid for enterprise market share, Anthropic slashed the input token costs for Claude 4.6 Haiku.
Old Price: $0.25 / 1M Input Tokens
New Price: $0.15 / 1M Input Tokens
What this means for CTOs
At the time, teams running high-volume log parsing, support routing, or large RAG pipelines could cut inference bills by routing to Claude 4.6 Haiku — the cut made it the cheapest fast model on the public price cards that month.
Outcome (October 2026): model pricing moves fast — Haiku 4.5 now lists at $1 / $5 per MTok. For today’s numbers, see our verified Claude pricing page.
