{"version":"2.1.317","anchor":"plugin-hooks-statusline-and-other-hook-commands-get-a-redac","canonical_anchor":"plugin-hooks-statusline-and-other-hook-commands-get-a-redac","heading":"Status line and hook logs can hide the command text in some plugin sessions","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/plugin-hooks-statusline-and-other-hook-commands-get-a-redac","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Status line and hook logs can hide the command text in some plugin sessions\n\nIn some plugin sessions, logs and errors for hooks and the status line show a display name or \"command left out\" instead of the command\n\n**Unclear.** It is not stated which plugin sessions use the hidden display name.\n\n**What**\n\nA hook is a command Claude Code runs at set moments, and `statusLine` runs your own command to draw a status line below the prompt. In some plugin sessions, logs and error output for these now show a display name, or the words \"command left out\", instead of the full command text.\n\nErrors from hooks that block Claude now also say whether the hook finished.\n\n**Why**\n\nThe text of hook commands is kept out of logs in these sessions.\n\n- Area: Hooks\n- Names: `statusLine`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}