{"version":"2.1.311","anchor":"explanatory-output-style-tip-added","canonical_anchor":"explanatory-output-style-tip-added","heading":"A tip about the explanatory output style after you ask for explanations","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/explanatory-output-style-tip-added","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### A tip about the explanatory output style after you ask for explanations\n\nIf you keep asking Claude to explain things, a tip now suggests an explanatory output style through \/config, at most three times ever\n\n**What**\n\nWhile Claude is working, Claude Code shows short tips next to its progress indicator. There is now a tip that points you to `\/config`, where you can choose an output style. An output style is a setting that changes how Claude writes its replies, for example explaining more as it works.\n\nThe tip follows these rules:\n\n- It appears only after you have asked Claude for explanations several times.\n\n- It is shown at most 3 times in total.\n\n- After it appears, it waits at least 15 sessions before it can appear again. A session is one run of Claude Code.\n\n- It is not shown if an output style is already set in your local settings, through a command-line flag, or by an organisation policy.\n\n**Why**\n\nIf you often ask Claude to explain what it is doing, this tip tells you there is a setting that can do that by default.\n\n- Area: Elsewhere\n- Names: `\/config`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}