Beginner 1 concept to know first

Models & Effort

The two dials behind every answer: which Claude model does the work, and how much effort it spends thinking and checking before it replies, trading speed and tokens for depth.

The animation needs JavaScript; every step is described below.

0:15

Know these first

1 concept · basics first
  1. Context

    The context window is everything Claude can see in a session: your messages, the files it reads, tool output and auto-loaded instructions. It fills as you work, and Claude Code compacts it when it gets full.

  2. Models & Effort · you are here

Two settings shape every answer Claude Code gives you. The model decides which Claude does the work. Effort decides how hard it works on each step: how much it thinks, tests and double-checks before replying. Both trade the same things against each other: speed, tokens and depth.

Choosing a model

Run /model to open a picker, or /model opus to switch straight away; that also saves it as your default for new sessions (press s in the picker to switch for this session only). You can also launch with claude --model opus, set ANTHROPIC_MODEL, or put "model" in a settings file.

Most people use aliases rather than version numbers: opus for complex reasoning, sonnet for daily coding, haiku for simple tasks, and fable for the hardest, longest-running work. Aliases move to newer versions over time; to pin one, use a full name such as claude-opus-5-5. Two special values: default clears your override and uses your account’s default model, and opusplan uses Opus while you’re in plan mode and Sonnet once it starts executing.

A model switch also reaches subagents that inherit the session’s model, unless their definition sets its own.

Choosing effort

On models that support it, effort controls adaptive reasoning: the model decides on each step whether and how much to think. The levels are low, medium, high, xhigh and max, though which ones exist depends on the model. Opus 5.5 and Sonnet 5.5 default to medium; most other models default to high.

Set it with /effort (a slider, or /effort high), the --effort flag, the CLAUDE_CODE_EFFORT_LEVEL variable, or an effort field in a skill or subagent’s frontmatter. For a single hard turn, put ultrathink in your prompt instead of changing the level. Unless you set it through that environment variable, max lasts for the current session only.

Need it faster rather than deeper? /fast turns on fast mode: the same Opus model, configured for faster output at a higher price per token.

The catch

Higher effort means more thinking tokens, and you pay for those even when they’re hidden. The docs warn that max can overthink. The same level name also isn’t calibrated the same way on every model, so retest when you switch rather than carrying a level over. A practical split: low effort while you’re steering each step, higher when Claude must verify on its own.

Where it sits

Before this

Context
Models & Effort

Leads to

Nothing yet.

The ideas underneath · Field Guide

Further reading from claude.dev

Posts from Anthropic's developer blog that go deeper. Summaries are ours; the posts are Anthropic's.

  • Using Claude Code: Spending your effort

    Hands-on runs of the same builds at each effort level, plus benchmark results showing where extra effort pays off (edge-case-heavy work) and where it barely moves the needle.

  • What a task costs on Opus 5.5

    Breaks a task's bill into turns, cache reads and output tokens, and shows how effort, model choice and context change it, and why a cheap run that needs a retry isn't cheap.

Sources

  1. Model configuration . Claude Code docs: aliases, /model, opusplan, effort levels, ultrathink
  2. Speed up responses with fast mode . Claude Code docs: /fast, a faster and pricier Opus configuration

Verified against the official Claude Code docs on October 1, 2026 · next review by January 1, 2027. Claude Code changes quickly; the docs are the source of truth.