Change Claude's Output Style for Different Tasks

Claude Code supports different output styles you can switch between depending on your task.

Built-in Styles

Access via /config or switch directly:

/output-style explanatory

• Concise - minimal output, just the changes (default)
• Explanatory - explains reasoning behind each decision. Great when exploring an unfamiliar codebase
• Learning - coaches you through changes, explains concepts, identifies knowledge gaps

Create Custom Styles

/output-style:new

Claude scaffolds a Markdown file you can customize. Define exactly how you want Claude to communicate: format, verbosity, what to include or skip.

Custom styles are stored in:

• Project-level: .claude/settings.local.json
• User-level: ~/.claude/output-styles/

When to Switch

Task	Style
Routine feature work	Concise
Onboarding to new codebase	Explanatory
Mentoring / pair programming	Learning
Rapid prototyping	Concise
Debugging unfamiliar code	Explanatory

Tip

You can combine output styles with the “thought partner” approach. Use Explanatory mode and ask Claude questions you’d ask another engineer. It’s like pair programming with someone who knows the entire codebase.

Show me how to change Claude Code's output style to be more explanatory when I'm learning a new codebase.