Output Style or CLAUDE.md: Which Dial Changes Tone
A developer wants Claude Code to sound more casual and narrate more of its reasoning during today's session, without changing anything about what Claude knows about the project's conventions or architecture, and without affecting sessions after this one.
Which mechanism should they use?
The correct answer is "Switch to a different output style."
An output style changes how Claude communicates — tone, role,
response format — by modifying the system prompt for the current
session; it doesn't touch what Claude knows about the project, and it
reverts on /clear or a new session, which matches both of the
developer's constraints (tone-only, session-scoped).
Editing CLAUDE.md is the wrong tool here even though it also
"changes behavior": CLAUDE.md holds persistent project context —
conventions, architecture notes — that's read at the start of every
future session too, so a tone note added there would leak into every
later session, not just this one. A deny rule in settings.json
controls which actions are blocked outright; it has nothing to do with
tone. Plan mode changes whether Claude can make edits without
approval, not how it communicates.
Share this question