{"version":"2.1.317","anchor":"baresafe-mode-hook-notices","canonical_anchor":"baresafe-mode-hook-notices","heading":"Claude Code tells you when your own hooks aren't running","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/baresafe-mode-hook-notices","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Claude Code tells you when your own hooks aren't running\n\nA new notice says your own hooks aren't running because a host kept them out, setup did not finish, or of launch mode, and Claude relays it\n\n**What**\n\nHooks are commands you configure Claude Code to run at set moments. Claude Code now shows a notice when your own hooks are not running in a session: \"Your own Claude Code hooks aren't running in this session\".\n\n- It gives the cause: a host app kept them out (`host_off`), setting them up did not finish, or the mode Claude Code was launched in.\n\n- When setup did not finish, it suggests starting a new session to try again.\n\n- A separate message tells Claude to pass the notice on to you.\n\n- The existing safe-mode and bare-mode reasons now carry `mode: true`.\n\n**Why**\n\nBefore, hooks could be off with no sign of it. Now you are told they are not running and why, so you are not left wondering why a hook did nothing.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}