Skip to content
eWiki The practical AI reference

AI Tool Glossary

What Are Claude Code Output Styles and When Should You Change Them?

Blank white paper with a black pen on a pale desk beside gray, blue, black, and cream color swatches.

Claude Code output styles are persistent instructions that shape how the tool responds. Change the style when you want a recurring response pattern—not when you need to supply project knowledge or enforce an action after every edit or command.

What Claude Code Output Styles Are

An output style supplies instructions that Claude Code sends with every request. It is therefore a way to establish recurring response behavior rather than rewriting the same preference in each prompt.

Claude Code documents five built-in styles: Default, Proactive, Concise, Explanatory, and Learning. These named options provide starting points before you invest in a custom configuration. As an editorial starting point, list the styles available in your installation and select a built-in option that matches the response pattern you want.

Stack of cream, blue, gray, and black paper samples on a gray desk beside a white ruler and black pen.

When to Change an Output Style

Change the output style when you want persistent instructions applied across requests—for example, when a recurring presentation or response pattern matters throughout a session. Keep the style’s role separate from two other Claude Code mechanisms:

  • Put information Claude should know about a particular project in CLAUDE.md.
  • Use hooks for actions that must occur every time, such as formatting after edits or blocking a command.

This distinction prevents response preferences, project context, and mandatory automation from becoming mixed together.

Be especially careful when creating a custom style under the full system prompt. Without keep-coding-instructions: true, Claude Code’s built-in software-engineering instructions are omitted. Add that frontmatter field when you want to preserve those instructions. It has no effect when the shorter system prompt is used.

Person seated at a white table reviewing printed layouts with a blue pen, with binders on shelves behind them.

How to Select or Create an Output Style

The supported selection method depends on the interface and version:

  • Terminal: In Claude Code v2.1.269 or later, run /output-style <style>. Run /output-style without an argument to list available styles and identify the active one.
  • Configuration menu: Run /config, then select Output style from the terminal menu.
  • VS Code extension: In Claude Code v2.1.257 or later, open the command menu with / and select Output styles. This menu can include custom styles.
  • Desktop app: Set the outputStyle field in a settings file such as .claude/settings.local.json.
  • Agent SDK: Configure the style through the settings object, not as a top-level Options field.

A custom output style is a Markdown file containing frontmatter and instructions. Documented locations include the user-level ~/.claude/output-styles directory, the project-level .claude/output-styles directory, and an output-styles directory inside the managed settings directory.

Because command support is version-specific, check the installed Claude Code version and follow the path documented for the interface you actually use.

Conclusion

Claude Code output styles are appropriate for response instructions that should accompany every request. Use CLAUDE.md for project knowledge and hooks for actions that must always run. Check your Claude Code version and interface, list the available styles through the documented method, and try a built-in style before creating a custom one for a recurring response pattern.

Disclosures and limitations

  • This article was prepared with AI assistance using the cited Claude Code documentation and supporting source materials.
  • Trying a built-in style before writing a custom one is an editorial suggestion, rather than a measured comparison.

Sources

Improve this guide

Report a problem or suggest the next question

Submissions enter a private editorial queue. They are reviewed and deduplicated before any public update or new page is created.