Claude Code has at least four separate controls for thinking effort, and I see a lot of people using only one of them. Here is how I split them, curious how others do it.
- Plan mode (Shift+Tab or /plan): Claude reads the code and proposes a plan before it edits anything. I use this for anything touching more than 3 files, or anything I would be nervous to undo. Cheapest way to catch a wrong direction early.
- /effort: sets the effort level for the session. I run low for renames, test scaffolding and boilerplate, and high when debugging something that has already failed once. Note that /effort warns you about a prompt cache miss if you change it mid-session.
- ultrathink: as of 2.1.311 (Oct 26) typing it runs that turn at xhigh effort on Opus 5.5, Sonnet 5.5, Haiku 5.5 and Fable 5.1 through Anthropic’s API. If you type it while Claude is already working, it raises the rest of that turn. So it is a one-turn boost, not a session setting. The rainbow highlight now only shows when it will actually do something.
- Model choice (/model): Haiku 5.5 for grunt work and quick questions, Sonnet 5.5 as the default, Opus 5.5 when I am stuck. Switching models is the biggest cost lever of the four. My rule in one line: plan mode decides direction, model decides capability, effort decides depth, ultrathink is the emergency button. Where this breaks for me: long sessions where I forget I set effort high an hour ago and keep paying for it on trivial edits. Which of these do you actually use day to day, and which one did you forget existed? Source: https://code.claude.com/docs/en/changelog submitted by /u/emarkosov
Originally posted by u/emarkosov on r/ClaudeCode
You must log in or # to comment.