Claude Code picked up a new Concise output style this week, and the pitch is simple: Claude leads with the result instead of narrating its way there. I flipped it on the same morning it landed, and the switch itself took about four seconds. Working out why it refused to appear on my desktop app took considerably longer — so here is the short version, plus the one surface where you currently cannot have it at all.
- At a glance
- Check your version before you go hunting for the setting
- The terminal takes four seconds
- The part that caught me out: the menu writes a per-project file
- Why the desktop app shows you nothing when you search for it
- VS Code and JetBrains ride along
- On the web, settings travel with the repository
- Your phone has nothing to set
- If it looks like nothing changed
- Worth the four seconds
At a glance
| Where you run Claude Code | Can you use Concise? | How you switch it on |
|---|---|---|
| Terminal (CLI) | Yes, on v2.1.237 or newer | /config → Output style |
| Desktop app | Not yet — current build ships an older engine | No picker exists; you edit a settings file by hand |
| VS Code / JetBrains | Follows whichever CLI version it runs | Shares ~/.claude/settings.json with the terminal |
| Web (claude.ai/code) | Depends on the version in your cloud environment | Commit a settings file to the repo, or use environment variables |
| Phone (Claude app → Code tab) | Inherited, never set here | Nothing to configure — no code runs on the phone |
Check your version before you go hunting for the setting
Concise arrived in Claude Code v2.1.237. The release note describes it as a style where Claude “leads with results and skips preamble and narration, while doing the work just as thoroughly.” My own machine was sitting on 2.1.233, and on that build the style genuinely does not exist — not hidden, not behind a flag, simply absent. If the option is missing for you, this is almost always the reason.
How to check: run claude --version in a terminal. Anything below 2.1.237 needs an update first.
Note: the standalone /output-style command is long gone — deprecated in v2.1.73 and removed in v2.1.91. Older tutorials still reference it. Use /config instead.
The terminal takes four seconds
Run /config, arrow down to Output style, and pick Concise from the list. That is the whole procedure, and it is the only surface with a menu for it.
How to use it: /config → Output style → Concise.
This is the detail I wish I had known first. When you pick a style through /config, Claude Code saves it to .claude/settings.local.json — a file inside the project folder you happened to be sitting in. Open a different repository tomorrow and you are back to the default, wondering whether the setting stuck.
To make it follow you everywhere, put it in your user-level settings file yourself:
{
"outputStyle": "Concise"
}That file lives at ~/.claude/settings.json on macOS and Linux, and at %USERPROFILE%\.claude\settings.json on Windows.
Works on: every surface that reads settings files. Note: when the same key appears twice, the narrower scope wins — local beats project, project beats user, and anything your organisation manages centrally beats all three. A per-project file you forgot about will quietly override your global preference.
Why the desktop app shows you nothing when you search for it
Here is where I lost my afternoon. Searching the desktop app’s settings for “concise” returns No matching settings, and that result is correct twice over.
First, the desktop app has never had an output-style picker. Anthropic’s own documentation tells desktop users to set the outputStyle field in a settings file directly, because typing /config there opens Settings → Claude Code rather than the terminal’s menu. Searching settings for it will never produce a hit, on any version.
Second — and this is the bit no amount of clicking will fix — the desktop app carries its own copy of the Claude Code engine, pinned when the app is built. I unpacked the current desktop package to check, and it reports an embedded engine version of 2.1.234, built on 17 August. Concise needs 2.1.237. The style is simply not in there yet, so writing "outputStyle": "Concise" into your settings today gives the desktop app a value it does not recognise.
What to do: keep using the terminal for Concise for now, and let the desktop app catch up on its next release. On macOS and Windows it updates itself on launch; on Linux it does not, and arrives through sudo apt update && sudo apt upgrade like any other package.
How to check your desktop version: on macOS, Claude in the menu bar → About Claude. On Windows, Help → About. Click the version number to copy it.
VS Code and JetBrains ride along
The IDE extensions share ~/.claude/settings.json with the CLI, so a global outputStyle covers both without any extra work. Whether Concise is available comes down to the Claude Code version the extension is running, exactly as it does in the terminal.
Tip: add "$schema": "https://json.schemastore.org/claude-code-settings.json" to the top of your settings file and VS Code will autocomplete and validate every key, including this one.
On the web, settings travel with the repository
Cloud sessions at claude.ai/code have no picker either. Typing /config opens the Claude Code section of your settings, and anything you type after the command — including key=value — is ignored outright.
How to use it: commit a settings file into the repository, or set the value through your cloud environment’s variables. The session reads what the repo carries.
Note: /clear does not exist in cloud sessions, so a change lands by starting a fresh session from the sidebar.
Your phone has nothing to set
The Code tab in the Claude mobile app is a client, not a place where code runs. It attaches to a cloud session, to a session on your own machine over Remote Control, or to a Dispatch task on your desktop. The style comes from whichever of those you are driving, so there is no mobile setting to find and nothing to configure.
If it looks like nothing changed
Two behaviours account for nearly every “I set it and Claude ignored me” report.
It does not apply mid-conversation. The output style is part of the system prompt, which is assembled once when a session starts. Run /clear or open a new session and it takes hold.
It does not reach subagents. Anything Claude delegates to a subagent runs on its own system prompt, so those replies keep their usual shape no matter what you chose. Forking the current conversation is the one exception, since a fork inherits the parent’s full prompt.
Worth the four seconds
Concise is the closest thing to a preference I have wanted since I started using Claude Code daily: the answer first, the reasoning available if I ask. The tax is knowing that the menu writes a project-local file, that the desktop app is running a slightly older engine than your terminal, and that neither takes effect until the next session. Set it globally once and you can forget all three.
Leave a Reply