The new Concise output style in Claude Code has a version gate most reviews skip. Below build 2.1.237, the option does not exist. The menu will show three entries, not four, and the menu will not explain why. Run claude --version before doing anything else. If the number is at or above 2.1.237, the rest of this applies to you. If not, update Claude Code, restart your terminal, and reopen with claude. The fourth entry shows up on the next session.
What the toggle actually does
Concise is a presentation layer. Same reasoning, same final answer, less preamble. The release notes describe it that way, and after a week of running with it on debugging sessions the description holds. Less scrolling through setup paragraphs. More reading of the actual change.
It is a quiet improvement, not a transformation. Once it is on, you stop noticing it. The cumulative time saved disappears into the workflow once you stop measuring it.
When not to use it is the part worth naming now. Concise drops the paragraphs that announce the plan, restate the question, and recap the obvious. For long debugging sessions where the answer is a diff, that is what you want. For learning an unfamiliar codebase, those paragraphs are the scaffolding you rely on. Explanatory mode exists for that reason. Concise is the wrong tool for jobs where the scaffolding helps.
The version gate, and why most “where is Concise” threads exist
Builds older than 2.1.237 simply do not have the option in the menu. Not hidden behind a flag, not waiting on a config, just absent. Most of the recent complaints online trace back to this. The fix is also boring. Update, restart, reopen. The new entry appears on the next session.
Two adjacent facts that catch people out:
- The
/output-styleslash command was deprecated in build 2.1.73 and removed in build 2.1.91. Any tutorial older than a few weeks that tells you to type/output-styleis pointing at a command that no longer exists. - A second sanity check is to open Claude Code and run
/config. If the only Output style entries you see are Default, Explanatory, and Formal, your build is older than 2.1.237.
The four-second switch on a current build
Once the entry is in the menu, switching to Concise is fast. Run /config, arrow down to Output style, pick Concise, press Enter. The whole interaction is roughly four seconds, and you feel the difference on the very next reply. The toggle is the easy part of the rollout, and the rest of this article is about the parts that are not.
Three details about the toggle that are easy to miss the first time:
- Per-conversation scope. The setting lives at the session level. Switching styles inside a long-running session holds the earlier behavior for that thread.
- New thread to see the change. The new style does not retroactively rewrite earlier replies in the same conversation. Start a new thread to see the difference from the first reply.
/configis the only menu surface. There is no separate settings page for output style inside Claude Code.
If your run takes longer than four seconds, the delay is almost always the build number, not the toggle.
Why your second project seems to forget the setting
Here is the part most coverage skips. Picking Concise through /config writes the choice into a file called .claude/settings.json, and that file lives inside whichever repository you happened to be editing when you flipped the switch. Open a fresh checkout of a different project the next morning and /config will treat it as a brand-new context. The fresh folder has no record of your preference, so the menu prompts you again. That is the explanation behind the “I set Concise yesterday and it is gone today” reports.
It is also the right behavior for teams that want each repository to carry its own configuration. The catch is that the global fallback lives in ~/.claude/settings.json, not in the per-project file, and there is no menu shortcut to edit the global one. Most solo developers will not find the global override without reading the docs, which is the practical cost of the design.
For team settings, committing .claude/settings.json to the repo is the cleanest path.
Where the standalone client currently sits
The standalone Claude client, the one with the chat box and the agents panel, is running an engine build older than 2.1.237. The picker does not exist in that build. Searching its settings for the word “concise” returns nothing, because nothing matching that word exists in its index. Correct behavior, not a bug.
For now, the picker is a terminal-only feature. There is also no in-client way to hand-edit the settings file the way you can from the terminal. If a future build brings Concise to the standalone client, expect the same per-project file the terminal uses to be the source of truth. Until that release lands, anyone who would rather click than type is paying for the gap.
What you can do about it:
- Pair the standalone client with a terminal tab for the parts of the workflow where Concise pays off.
- Watch the standalone client’s release notes for the next version bump and check whether the engine crosses 2.1.237 before you assume the picker is broken.
How the editor extensions and the web version behave
The Claude Code editor plugins for VS Code and JetBrains share the same engine as the terminal, so the per-project settings file carries over the moment you open the same repo in either editor. Different project, same rule: the editor plugin has no output style toggle of its own, and it will not invent one until the underlying engine catches up.
The web experience at claude.ai/code is the odd one out. Output style on the web is controlled by whatever lives in the cloud environment the browser is connected to, not by your local settings file. To get Concise there, you can commit the per-project file to the repo and rely on the cloud environment picking it up, or you can set an environment variable in your cloud workspace before the session starts.
Quick map of where the setting lives in each surface:
- VS Code and JetBrains: inherited per-project from the terminal’s settings file, no extra step.
- The web version at
claude.ai/code: ignores the local file; reads the cloud environment instead. - For teams that want Concise everywhere, commit the per-project file and set the environment variable in the cloud workspace.
When the switch seems to do nothing
Two things explain a reply after the toggle that looks identical to a reply from before. The first is that the conversation you are responding to was started before you changed styles, and Claude has already committed to the earlier behavior for that thread. The second is that you changed styles inside an already long-running session with its own context window, and the new style only applies to future turns in a fresh conversation. In either case, open a brand-new conversation, repeat the same prompt, and the difference should show up on the first reply. If it still does not, run claude --version one more time and confirm the build is at or above 2.1.237.
Trade-offs
Four costs worth naming before you flip the switch:
- Incomplete rollout. Anyone below build 2.1.237 has no path to the setting short of updating Claude Code itself. That is a real cost for teams that pin specific build versions for reproducibility, and the fix is to either upgrade past 2.1.237 or wait for the next stable release if your team is locked to an older line.
- Per-project scoping. Right behavior for teams who want different repos to use different styles, wrong behavior for a solo developer who expects one setting to follow them everywhere. Editing your global
~/.claude/settings.jsonis the workaround, but most people will not find it without reading the docs. - Standalone client gap. Anyone who prefers clicking to typing pays for it until the standalone client catches up. The terminal toggle works today. The standalone menu does not. That is the honest version, not a dealbreaker for most workflows.
- Mid-thread style changes. The new style does not retroactively change earlier messages in the same conversation. Start a new thread to see the difference. If you swap styles often during long debugging sessions, expect to start new threads more than you did before.
What I would tell past me
Concise is not a flashy feature, and that is exactly why it pays off. It does one thing, it does it well, and it takes four seconds to turn on once you know where to look. The version-number gating is the part most coverage skips, and it is the part that wastes the most time when you skip it. Update first, toggle second, edit your global settings only if you actually want the same style everywhere.
One pattern worth keeping: when a new Claude Code setting shows up and you cannot find it, run claude --version before you run anything else. The version gate is the single most common reason a setting that should be visible is invisible, and it is the cheapest check to do.