Claude Code Too Chatty? This Switch Can Cut Answers in Half

Claude Code's default output style is verbose. For a simple question, it first restates your request, then explains its thinking step by step, and finally adds a summary. You drag the scrollbar for ages and the code change is only a few lines.

Addy Osmani posted on X that you can switch the output style to Concise. The method is simple: run /config and choose Output style, or add one line directly in settings.json:

{
  "outputStyle": "Concise"
}

The behavior of Concise mode is clearly described in the official docs: the first sentence directly states the result or answer, removing opening remarks, step-by-step narration, and closing summaries. Simple questions are answered in one or two sentences. The quality of engineering implementation is the same as in default mode. When you need details, ask and it will still expand. Error reports, test failure output, and security warnings are not compressed; they are kept in full.

Some users asked whether Concise will also cut out the apologies and small preambles before each answer. From the docs description, opening remarks are exactly what it removes. Another user asked more specifically: will the plan explanation before changing files become shorter, or will only the final summary become shorter? No one answered this directly, but based on the definition of Concise, narration during the planning phase counts as preamble and should be cut. You'll have to try it yourself to see the actual effect.

Some people find it not short enough. Daniel Stefan added a line to the global CLAUDE.md: "When reporting information to me, be extremely concise and sacrifice grammar for sake of concision." He said this works even better than the built-in Concise. Another user, cj, wrote a style called Procedural, requiring Claude to speak using ASD-STE100 Simplified Technical English and to draw a state diagram whenever it encounters a state machine. He also tried ICAO radio phraseology, but Claude became too robotic, so he gave up.

One detail worth noting: values in settings.json are case-sensitive. Writing "outputStyle": "Concise" is correct; writing "concise" will fall back to Default. The /output-style command itself is case-insensitive, but the config file must be exact. Also, /config saves settings for the current project; to apply globally, change ~/.claude/settings.json. Project-level settings take higher priority, which explains why switching in some repository doesn't work.

Mister SnowCrash clarified this in a reply: /config writes to .claude/settings.local.json, which is valid only for the current project. To make it the default across repositories, set outputStyle in the user-level settings.json. A project's own settings will override the global value.

Regarding versions, Concise requires Claude Code v2.1.237 or higher. In early versions, after switching styles you had to /clear or start a new session for it to take effect; after v2.1.251, the next message will use the new style.

Someone asked whether token usage would decrease. The official docs say: the style instruction itself adds input tokens, but prompt caching can spread that cost out. Concise reduces output tokens. As for whether it saves money, a user in the replies said that's just a side effect; the core benefit is making output easier to read.

Others care about diff readability. Chalitha Widusahan asked whether Concise will also compress diffs. The docs don't say diffs will change; Concise changes the narration in the conversation, not the code itself. Jess's usage is more direct: when bugs get weird, switch the style back.

Mikhail Rogov's comment hits the key point: Concise should be the default. Long output makes the actual code changes harder to review. That makes sense. The default style writes like a tutorial, while most of the time you just want to know what changed and why. Ask for a tutorial when you need one.

If you haven't tried it yet, take ten seconds to change settings.json. The cost is a few more input tokens; the benefit is a shorter scrollbar.

References:

• Addy Osmani tweet: https://x.com/addyosmani/status/2118958843501920268
• Claude Code output styles official docs: https://code.claude.com/docs/en/output-styles
• Attention Span custom style project: https://github.com/alexgreensh/attention-span