Claude has a "Concise" output style

CLAUDE.mdinstead.

Built-in output styles #

Claude Code’sDefault output style is the existing system prompt, designed to help you complete software engineering tasks efficiently. There are four additional built-in output styles:

Proactive: Claude executes immediately, makes reasonable assumptions instead of pausing for routine decisions, and prefers action over planning. This is stronger autonomous-execution guidance thanauto modeapplies, and it works without changing your permission mode, so your permission mode still decides what runs without asking you. - Concise: Claude leads with the result, skips preamble and narration, and keeps responses short by default, while doing the engineering work as thoroughly as in the Default style. When you ask for an explanation or more detail, Claude answers in full. Claude always keeps the complete content of error reports, security warnings, and confirmations for destructive actions. Requires Claude Code v2.1.237 or later. - Explanatory: Provides educational “Insights” in between helping you complete software engineering tasks. Helps you understand implementation choices and codebase patterns. - Learning: Collaborative, learn-by-doing mode where Claude will not only share “Insights” while coding, but also ask you to contribute small, strategic pieces of code yourself. Claude Code will addTODO(human)

markers in your code for you to implement.

Change your output style #

Pick a style in one of these ways:Terminal: run/config

and selectOutput style to pick a style from a menu. Claude Code saves your selection to.claude/settings.local.json

at thelocal project level.Desktop app: set theoutputStyle field in a settings file, for example.claude/settings.local.json

, the file the terminal menu writes. When you run/config

there, Claude Codeopensrather than a menu.Settings > Claude Code The standalone

/output-style

command was deprecated in v2.1.73 and removed in v2.1.91. Use /config

or edit the outputStyle

setting directly.outputStyle

field directly in a settings file: /clear

or a new session. See How Claude Code uses prompt cachingfor what an output style change does to the cache.

Create a custom output style #

A custom output style is a Markdown file: frontmatter for metadata, then the instructions to add to the system prompt.1

Create a Markdown file

Save it at one of three levels. The file name becomes the style name unless you set

name

in the frontmatter.- User: ~/.claude/output-styles

• Project: .claude/output-styles

• Managed policy: .claude/output-styles

inside themanaged settings directory .claude/output-styles/

between the working directory and the repository root. When more than one of these nested directories defines a style with the same name, Claude Code uses the one closest to the working directory.2

Add frontmatter and instructions

Decide whether to keep Claude Code’s software engineering instructions. Set

`keep-coding-instructions: true`

if you’re changing how Claude communicates but still want it coding the same way. Leave it out if Claude won’t be doing software engineering.This example leads every explanation with a diagram while keeping Claude’s coding behavior:3

Switch to your style

Run

/config

in the terminal and select your style under Output style, or setoutputStyle

in a settings file to the style’s name. It takes effect after /clear

or the next time you start a session.Pluginscan also ship output styles in an

output-styles/

directory.

Frontmatter

Output style files support these frontmatter fields:## How output styles work

Output styles directly modify Claude Code’s system prompt.- Claude Code adds each output style’s custom instructions to the end of the system prompt.

• All output styles trigger reminders for Claude to adhere to the output style instructions during the conversation.
• Custom output styles leave out Claude Code’s built-in software engineering instructions, such as how to scope changes, write comments, and verify work, unless

keep-coding-instructions is set totrue

.

subagent runs its own system prompt, so styles don’t change how subagents respond. A forkis the exception, because it inherits the parent’s full system prompt. Token usage depends on the style. Adding instructions to the system prompt increases input tokens, though prompt caching reduces this cost after the first request in a session. The built-in Explanatory and Learning styles produce longer responses than Default by design, which increases output tokens, and the Concise style does the opposite by instructing Claude to keep responses short by default. For custom styles, output token usage depends on what your instructions tell Claude to produce.

Comparisons to related features #

Several features customize how Claude Code behaves. Output styles modify the system prompt directly and apply to every response. The others add instructions without changing the default system prompt, or scope them to a specific task.## Related resources

Settings: where theoutputStyle field lives and how settings precedence worksPermission modes: how the Proactive style compares to auto modePlugins: package and distribute output styles alongside skills, hooks, and agentsDebug your configuration: diagnose why an output style isn’t taking effect