{"version":"2.1.312","anchor":"status-line-tip-now-routed-through-a-content-helper","canonical_anchor":"status-line-tip-now-routed-through-a-content-helper","heading":"Several Claude Code tips can now vary in wording","tier":"internal","area":"Tips","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/status-line-tip-now-routed-through-a-content-helper","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Several Claude Code tips can now vary in wording\n\nThe tips for `\/statusline`, `\/permissions` and plan mode are now built in a way that lets their wording vary, though the current text is unchanged\n\n**What**\n\nClaude Code shows short tips about its features. Three of them now get their text from a helper instead of a fixed string:\n\n- The `\/statusline` tip, which still reads \"Use \/statusline to set up a custom status line that will display beneath the input box\"\n\n- The `\/permissions` tip, which still suggests using `\/permissions` to pre-approve and pre-deny bash, edit, and MCP tools\n\n- The tip suggesting plan mode for complex tasks\n\nThe wording of each is unchanged for now. The check that decides whether the `\/statusline` tip is relevant to you also changed, and now includes a check related to managed hooks (hooks, meaning commands that run automatically at certain points, set up centrally rather than by you).\n\n**Why**\n\nBecause the text now comes from a helper, these tips can be worded differently for different users, so what you see may not match what someone else sees.\n\n- Area: Tips\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}