Are Claude Code Output Styles Deprecated? What Changed and What to Use Instead
By Neo Zino - builder of ClockedCode7 min readNo - Claude Code output styles aren't deprecated. What got removed was the /output-style command in v2.1.91. Here's what changed and how to switch styles now.
Made with DispatchSEO
On this page
No, Claude Code output styles are not deprecated. The feature is currently five built-in styles deep, got a brand-new one (Concise, in v2.1.237) three weeks before this rumor picked up, and had a persistence bug fixed the very next day. I went and checked what really happened: the standalone /output-style slash command was deprecated in v2.1.73 and removed in v2.1.91. The command moved. The feature underneath it kept working.
TL;DR: Output styles are alive and getting updates. The
/output-stylecommand is gone (removed in v2.1.91); switch styles through/config, the VS Code command menu, or theoutputStylesetting instead. The "replaced by plugins" fear traces to one open GitHub feature request with no Anthropic response, not a roadmap item.
No, output styles aren't going away
Check the feature's own docs page and the picture is the opposite of dying: five built-in styles (Default, Proactive, Concise, Explanatory, Learning), a documented way to write your own, and a comparisons table against CLAUDE.md, --append-system-prompt, agents, and skills so you know when to reach for which. None of that reads as sunset language, and Anthropic doesn't typically leave a full reference page up for a feature it's about to pull.
The stronger evidence is what shipped around it recently. Two consecutive releases in August 2026 both touched output styles directly - one adding a style, one fixing a bug in the existing ones:
Every release that actually touched output styles
current as of v2.1.257
- v2.1.73
The standalone /output-style command is deprecated
Anthropic starts steering people toward /config instead - the command still runs, but it's on its way out.
- v2.1.91
/output-style is removed
The command is gone for good. This is the change people are actually reacting to when they call output styles "deprecated."
- v2.1.237
A new built-in style ships: Concise
Claude leads with the result and skips preamble, doing the same work with less chatter - a brand-new addition to the feature, not a wind-down.
- v2.1.238
A style-persistence bug is fixed
Custom, project, and plugin styles used to drift back to the default voice mid-session. Anthropic shipped the fix the very next day.
- v2.1.251
Switching styles stops requiring a fresh session
Before this release, a new style only applied after /clear or a new session. Now it applies starting with your next message.
- v2.1.257
The VS Code extension gets its own style picker
Open the command menu with / and pick Output styles, including custom ones - no more terminal-only switching.
Two removal-shaped entries, four addition-or-fix entries - the ledger the "deprecated" rumor leaves out.
Six dated releases, four of them additions or fixes and only two of them the single command removal everyone's reacting to. That's what active maintenance looks like.
The one thing that actually got removed: the /output-style command
Here's the part of the rumor that's true, precisely stated: /output-style - the standalone slash command you used to type to switch styles - was deprecated in Claude Code v2.1.73 and removed in v2.1.91. If you've been away from Claude Code for a while and it stopped responding to that command, this is why, and it's the entire factual basis for "output styles are deprecated."
The feature the command controlled didn't go anywhere. /config took over the job: run it, select Output style, and pick from the same list /output-style used to show you. The switch still gets written to .claude/settings.local.json at the project level, same as before - only the entry point moved.
| Surface | How to switch | Version needed |
|---|---|---|
| Terminal | /config → Output style | Any current version (/output-style itself is gone as of v2.1.91) |
| VS Code extension | / command menu → Output styles | v2.1.257 or later |
| Desktop app | Edit outputStyle directly in a settings file, e.g. .claude/settings.local.json (/config there opens Settings → Claude Code instead of a menu) | Any current version |
One more thing worth knowing if you switch mid-session: before v2.1.251, a new style only took effect after you ran /clear or started a new session. That's no longer true - since v2.1.251, Claude picks up the new style starting with your very next message.
Where the deprecation rumor started
Search results for this query are a mix of a Reddit thread flatly stating styles are "already deprecated," a LinkedIn post making the same claim, and an open GitHub issue titled "Please don't remove Output-Styles!" None of them are wrong that something got deprecated - they're wrong about what.
What's circulating
Reddit, LinkedIn, an open feature request
"Output styles are already deprecated"
The claim driving this search, repeated across posts that don't cite a version number or a docs page.
They'll be replaced by a plugin system
The fear behind GitHub issue #10671, opened October 31, 2025 - a feature request, not an announcement.
No maintainer response, ever
The issue has sat open without an Anthropic comment since it was filed - silence, not confirmation.
What's documented
code.claude.com/docs, this site's changelog mirror
Output styles are a current, built-in feature
Five styles ship today and the feature has its own docs page - nothing there reads as sunset.
A new style shipped three weeks before this rumor peaked
Concise landed in v2.1.237 on August 19, 2026 - a real addition, not a wind-down.
A bug in the feature got fixed the next day
v2.1.238 fixed styles drifting back to the default voice mid-session - active maintenance, not neglect.
That GitHub issue, #10671, is the real seed of the "replaced by plugins" version of the rumor. It was opened October 31, 2025 by a user worried that Anthropic would fold output styles into the plugin system, and it lists real, specific complaints - plugins need more setup steps for a simple persona swap, they're harder to disable than just picking Default, and the writer points to a separate bug report about plugin failures. As of this guide's publish date, the issue has no reply from an Anthropic maintainer confirming or denying that plan. An unanswered feature request is not a deprecation notice. Nothing in the current docs or changelog treats output styles as a plugin-only thing going forward, either - plugins can ship output styles alongside skills and hooks, and that reads as an addition to the system, not a plan to gut it.
The five styles you have today, and how to switch
If you landed here mid-migration and just want the current lineup:
The five built-in styles under Output style in /config
Default
always availableThe existing system prompt - built for finishing software engineering tasks efficiently.
Proactive
always availableExecutes immediately and makes reasonable assumptions instead of pausing for routine decisions - stronger than auto mode, and independent of your permission mode.
Concise
requires v2.1.237+Leads with the result, skips preamble and narration, does the same engineering work with less chatter around it.
Explanatory
always availableAdds educational "Insights" alongside the coding work, explaining implementation choices and codebase patterns.
Learning
always availableShares Insights and asks you to write small, strategic pieces of code yourself - Claude leaves TODO(human) markers for that.
Custom styles still work exactly as documented: a markdown file with frontmatter at ~/.claude/output-styles/ (personal) or .claude/output-styles/ (project, meant to be committed), with a keep-coding-instructions flag that decides whether Claude keeps its software-engineering habits on top of the new voice. ClockedCode's output style generator writes that file for you if you'd rather not hand-write the frontmatter.
Honest limits
I pulled the removal dates (v2.1.73 deprecated, v2.1.91 removed) and the newer version gates (v2.1.237, v2.1.238, v2.1.251, v2.1.257) straight from Anthropic's own output-styles doc and changelog rather than from testing every version myself, so this guide is only as current as those sources were on 2026-09-08. GitHub issue #10671 could get an official response after this publishes. If Anthropic ever does confirm a plugin-replacement plan, that would make the "no documented plan" answer here outdated - check the issue directly if you're making a decision that depends on it.
FAQ
Are Claude Code output styles deprecated?
No. Output styles are a current, actively maintained feature with five built-in styles and their own docs page. A new style (Concise) shipped in v2.1.237 and a bug in the feature was fixed the next day in v2.1.238 - that is not what a deprecated feature looks like.
What actually got removed from output styles?
Only the standalone /output-style slash command - deprecated in v2.1.73 and removed in v2.1.91. The feature it controlled, output styles themselves, was never removed; you switch through /config instead.
Why do people think output styles are being deprecated?
Two things got conflated: the real removal of the /output-style command, and an open GitHub feature request (issue #10671) asking Anthropic not to deprecate output styles in favor of a plugin system. The issue is a request. It has no maintainer response confirming any such plan.
How do I switch output styles now that /output-style is gone?
Run /config in the terminal and select Output style, use the / command menu in the VS Code extension (v2.1.257+), or edit the outputStyle field directly in a settings file like .claude/settings.local.json. All three write to the same setting.
Will output styles be replaced by plugins?
There's no documented plan to do that. The fear comes from a single open feature request from October 2025 that Anthropic hasn't commented on either way. Plugins can ship output styles of their own, which adds to the system rather than replacing it.
The command changed, not the feature
If a stale bookmark or an old habit has you typing /output-style into a current Claude Code session, that's the whole story - swap it for /config, and everything else about the feature keeps working the way it always did. Output styles change how Claude talks; a tuned CLAUDE.md changes what it knows about your project, and hooks are the layer for anything that needs to be enforced rather than just requested - ClockedCode ships tuned versions of all three.