2 min read AI-generated

Claude Code 2.1.237: The 'Concise' Style Becomes Built-In

Copy article as Markdown

A small release with two points: Claude Code can now answer briefly out of the box if you want it to. And a caching bug that served stale prompts on custom gateways is gone.

Featured image for "Claude Code 2.1.237: The 'Concise' Style Becomes Built-In"

One day after 2.1.235 and 2.1.236, here’s the next release already. 2.1.237 is small, but one item in it will land well with a lot of people.

Less preamble, more result

Claude Code gets a built-in output style called Concise. Turn it on, and Claude leads with the result and drops the wrapping – no “let me take a look,” no narrating every step. The work itself stays just as thorough; only the chatter before and between falls away.

You’ll find the style under /config, at the Output style setting. Until now you had to cobble something like this together with your own instruction whenever the long status updates got on your nerves. Now it’s a switch.

If you’ve been around a while, you’ll remember: the complaint about novel-length progress messages is almost as old as Claude Code itself. So this is an answer to a real ask, not a feature pulled from the idea box.

Caching bug on custom gateways

The second item affects a smaller group, but it was annoying for them. If you run Claude Code through an LLM gateway or a custom base URL, you could end up served stale prompts – prompt caching wasn’t gripping cleanly in that case. That’s now fixed. Your sessions pull the current state again, not one from earlier.

My take

Concise is the kind of feature where I wonder why it wasn’t here sooner. Not everyone wants to read along at every step as Claude thinks. Sometimes you just want the result and that’s it. Anthropic offering this as a proper style instead of a DIY workaround makes it reachable for anyone who opens /config once.

The gateway fix quietly shows Anthropic also has an eye on people who use Claude Code not directly, but through their own infrastructure. For teams with their own proxy, a caching bug like this isn’t a detail – it’s a daily stumbling block.


Sources: