9. Models and cost
"Claude Code picks a model by alias (opus, sonnet, haiku, fable) that tracks the newest version for your provider, plus an effort level that sets how hard it reasons on each step. Today the default on the Anthropic API and every paid plan is Opus 5.5 at medium effort, with a 1 million token window built in. /model switches models, /effort changes reasoning depth, /fast buys speed on Opus at a higher per-token price, and /usage shows what a session cost and what is eating your plan limits. For a team, the levers are admin settings (a model allowlist, an effort cap, spend limits) and two habits that move cost the most: clear between unrelated tasks, and match the model to the job instead of leaving Opus on for everything."
If you can also explain why a mid-session model switch costs more than it looks (the prompt cache), you've answered the follow-up before it's asked.
8 pictures, in order.
Use the arrow keys or the dots. Tap a picture to see it full size.
The facts someone can check.
Aliases and defaults
| Alias | What it does |
|---|---|
default |
Clears overrides. Opus 5.5 on Pro, Max, Team, Enterprise and the API; Sonnet 4.5 on Microsoft Foundry |
opus, sonnet, haiku |
Latest of each family for your provider. On the Anthropic API: Opus 5.5, Sonnet 5.5, Haiku 5.5 |
fable |
Fable 5.1, for the hardest and longest tasks. Never a default; select it yourself |
best |
Fable where available, otherwise the same as opus |
opusplan |
Opus in plan mode, Sonnet once it executes |
opus[1m], sonnet[1m] |
Ask for the 1M window. No effect when the model already has it natively |
Aliases move. On Bedrock and Google Cloud's Agent Platform, sonnet still means Sonnet 4.5; on Foundry, opus means Opus 4.6. To pin, use the full model name (claude-opus-5-5) or ANTHROPIC_DEFAULT_OPUS_MODEL.
Which model a session runs on
In priority order: /model in the session, claude --model at launch, ANTHROPIC_MODEL, the model field in settings, then ANTHROPIC_DEFAULT_MODEL.
/model <name>saves. Typing a name, or pressing Enter in the picker, switches now and saves your default. Presssin the picker for this session only.- Project and managed settings reapply every launch, and the startup header names the file that set the model.
- A skill's
model:lasts for the rest of the turn that invoked it. A subagent resolves its model from the per-call choice, then its frontmatter, thenCLAUDE_CODE_SUBAGENT_MODEL, then the session's model. A resumed session keeps the model it was saved with. - Admins restrict choices with
availableModelsin managed settings. The allowlist covers/model,--model, settings, subagents, skills and fast mode. - Each model has its own prompt cache. A mid-session switch rereads the whole conversation uncached; Claude Code asks you to confirm while the cache is warm.
Effort
| Level | When to use it | Default on |
|---|---|---|
low |
Quick exchanges you review: brainstorming, a first sketch, a rename | |
medium |
Day-to-day work with a clear scope | Opus 5.5, Sonnet 5.5, Haiku 5.5 |
high |
Bug fixes where checking and edge cases matter | Most other models |
xhigh |
Deeper reasoning at higher token spend | Opus 4.7 |
max |
Hard problems Claude works through alone. Can overthink | None. Applies to the current session only |
- Resolution order: explicit (
CLAUDE_CODE_EFFORT_LEVEL,--effort,/effort), then settings (a level saved per model undermodelSettings, oreffortLevel), then the model's default. - A top-level
effortLevelin user settings doesn't count for Opus 5.5. It is the older form; Opus 5.5 uses a per-model saved level or its ownmediumdefault. - In Anthropic's testing, Opus 5.5 at
mediummatches or exceeds Opus 5 athigh. Moving from Opus 5, start atmedium. ultrathinkin a prompt asks for deeper reasoning on that one turn.ultracodeis a setting, not a level./effort autoclears your saved level for the active model.- Admins cap effort with
maxEffortLevel(any plan or provider) or per-role limits on Enterprise; the lower cap wins. - On Opus 5.5, Sonnet 5.5, Haiku 5.5 and Fable 5.1 with an API key or subscription, changing effort keeps the prompt cache. On most other setups it doesn't.
Context window
- Native 1M: Fable 5.1, Fable 5, Sonnet 5 and later, Haiku 5.5, Opus 4.7 and later. No
[1m]needed. - Opus 4.6 and Sonnet 4.6 reach 1M only through their
[1m]variant, which depends on your plan. - Native-1M sessions auto-compact at about 967K tokens.
/autocompact 500kcompacts earlier for the current model (range 100K to 1M);CLAUDE_CODE_DISABLE_1M_CONTEXT=1holds every model to 200K. - On the Anthropic API, tokens past 200K carry no premium. The exception is Haiku 5.5, which costs more on prompts over 100K tokens.
Fast mode
- The same Opus, up to 2.5x faster, at a higher price per token: $8 / $40 per million input / output tokens on Opus 5.5, $10 / $50 on Opus 5 and Opus 4.8. Those three are the only supported models.
- Research preview. Anthropic API and subscriptions only: not on Bedrock, Agent Platform, Foundry, or Claude Platform on AWS.
- On subscriptions it draws on usage credits only, never the plan's included usage. Team and Enterprise start with it off until an Owner enables it.
- Turn it on at the start. The first switch-on bills the whole conversation so far as uncached input at fast rates, and fast and standard speed keep separate caches.
- Toggle with
/fastor Option+O on macOS.fastModePerSessionOptIn: truemakes every session start with it off.
Reading /usage (aliases /cost and /stats)
- The Session block is a local estimate at list price, unless an admin sets
modelPricingto show contracted rates. It resets on/clear. For subscribers it is not billing. - The Prompt cache line shows the share of input served from cache, misses and their likely cause, and whether the cache is warm.
- On Pro, Max, Team and Enterprise, the plan breakdown attributes recent usage to skills, subagents, plugins and MCP servers, and recommends changes that touch at least 10% of usage. Press
fto apply the ones Claude Code can,dorwfor 24 hours or 7 days. It covers this machine only. - Background jobs (summaries for resume, status checks) use under $0.04 per session.
Costs for a team
Across enterprise deployments, the average is about $13 per developer per active day and $150 to $250 per developer per month, with 90% of users under $30 per active day. Pilot a small group to set your own baseline.
| Setup | See spend | Cap spend | Per-user numbers |
|---|---|---|---|
| Claude for Teams or Enterprise | Spend report in org analytics | Seat allowance, then usage-credit limits | Spend CSV; Enterprise Analytics API |
| Claude Console (API) | Console usage page | Workspace spend limits | Console dashboard; Claude Code Analytics API |
| Bedrock, Agent Platform, Foundry | Cloud billing console | Cloud budget controls | OpenTelemetry or an LLM gateway |
OpenTelemetry works on every setup and is the only option that streams per-user tokens and cost into your own monitoring in near real time.
Console rate-limit recommendations per user, by team size:
| Team size | TPM per user | RPM per user |
|---|---|---|
| 1 to 5 | 200k to 300k | 5 to 7 |
| 5 to 20 | 100k to 150k | 2.5 to 3.5 |
| 20 to 50 | 50k to 75k | 1.25 to 1.75 |
| 50 to 100 | 25k to 35k | 0.62 to 0.87 |
| 100 to 500 | 15k to 20k | 0.37 to 0.47 |
| 500+ | 10k to 15k | 0.25 to 0.35 |
Habits that move the number: /clear between unrelated tasks, Sonnet for most coding with Opus for hard reasoning, plan mode before big changes, workflow text moved from CLAUDE.md into skills, and subagents for noisy work like test logs. Agent teams use about 7x the tokens of a standard session when teammates run in plan mode. When spend is unexpectedly high, the docs trace it to long sessions that were never cleared and Opus left as the default.
Answer out loud, then flip the card.
Mark each one honestly. Cards you miss stay flagged for review, in this browser.
A developer ran /model sonnet yesterday, but today's session started on Opus. Why?
/model sonnet did save Sonnet to their user settings, but something with higher priority reapplies at launch: a model in project or managed settings, ANTHROPIC_MODEL in their shell, or an organization default set to override user choices. The startup header names the settings file when project or managed settings set the model. Two other causes: they resumed a session, which keeps its saved model, or Claude Code couldn't write ~/.claude/settings.json.
What is the difference between fast mode and lowering effort?
Fast mode keeps the same model and the same quality and makes responses faster by paying more per token; it works only on Opus 5.5, Opus 5 and Opus 4.8. Lowering effort makes Claude think less per step, which is faster and cheaper but can lower quality on hard tasks. They combine: fast mode with low effort is the quickest setup for straightforward work.
The CFO wants Claude Code spend per developer. Where does that come from?
It depends on how they access Claude. Teams and Enterprise: the spend report in org analytics, with CSV export, and the Enterprise Analytics API. Console: the Claude Code dashboard and the Claude Code Analytics API. Bedrock, Agent Platform or Foundry: Claude Code sends nothing back to Anthropic, so use OpenTelemetry or an LLM gateway that tracks spend per key. OpenTelemetry works on every setup. And /usage on a laptop is an estimate, not a report.
How does an admin keep costs predictable across 500 developers?
Managed settings: availableModels to limit which models people can pick, maxEffortLevel to cap effort, fastModePerSessionOptIn (or fastMode: false) so fast mode is never left on by accident, and CLAUDE_CODE_SUBAGENT_MODEL to run subagents on a cheaper model. Then spend caps where the bill lives: usage-credit limits on Teams and Enterprise, workspace limits on the Console, budget controls in the cloud. Set modelPricing so /usage shows contracted rates. Start with a pilot to set a baseline.
A developer sees "You've hit your session limit." Will switching to Haiku get them working again?
No. Session and weekly limits on subscription plans are shared across every model. Switching only helps after a model-specific message such as "You've hit your Opus limit." Their options are /usage-credits to request usage beyond the allowance, if credits are on, or waiting for the reset, which Claude Code can do and then continue the task automatically.
Does the 1M context window cost extra, and should a team turn it on?
Current models have it natively; there is nothing to turn on. On the Anthropic API, tokens past 200K carry no premium, except Haiku 5.5 above 100K. But every request carries the whole conversation, so a long session costs more per message whatever the price per token. Sessions compact at about 967K by default. To hold them smaller, use /autocompact or CLAUDE_CODE_DISABLE_1M_CONTEXT=1, and teach /clear between tasks.
When does changing model, effort or speed in the middle of a session cost more than it looks?
Each model keeps its own prompt cache, so a model switch makes the next request reread the whole conversation uncached. Claude Code asks you to confirm while the cache is warm. Effort changes keep the cache on Opus 5.5, Sonnet 5.5, Haiku 5.5 and Fable 5.1 with an API key or subscription, but invalidate it on most other setups. Fast mode keeps a separate cache, and the first switch-on bills the whole conversation at uncached fast rates, so turn it on at the start.
A Max subscriber asks what the dollar figure in /usage means for them.
Nothing for billing. It is computed locally from token counts at list price, and subscribers pay by plan. What matters to them is further down: the plan usage bars, and the breakdown that attributes recent usage to skills, subagents, plugins and MCP servers, with recommendations they can apply with f. For API users the figure is an estimate too; the Console is the authoritative bill.
Wrong answers that sound right.
Before you tap, say why each one is wrong.
Three moves in a fresh project.
Facts checked against code.claude.com/docs/en/model-config, /costs, /fast-mode, /prompt-caching, /sub-agents, /settings-reference and /commands on 2026-10-25. Claude Code ships fast: confirm anything that matters against the official docs.