{"version":"2.1.296","anchor":"hooksettings-startup-check-explains-restricted-mode-and-dis","canonical_anchor":"hooksettings-startup-check-explains-restricted-mode-and-dis","heading":"Claude Code now explains why your user settings and hooks are not in effect","tier":"notice","area":"Settings","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/hooksettings-startup-check-explains-restricted-mode-and-dis","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Claude Code now explains why your user settings and hooks are not in effect\n\nWhen user settings are skipped or hooks are turned off elsewhere, Claude Code now gives the reason instead of saying nothing\n\n**What**\n\nYour user settings file holds your personal Claude Code settings, including hooks, which are commands that run when certain events happen. When a session starts, Claude Code checks this file. Before, if user settings were not being read, the check simply came back empty. It now gives the reason, which can be:\n\n- the session runs in restricted mode, which reads no user settings\n\n- the session's settings sources leave out user settings\n\n- another settings file turns all hooks off\n\n**Why**\n\nIf you are in a restricted session, or another settings file overrides yours, you can now see why your hooks and rules are not taking effect instead of wondering why nothing happens.\n\n- Area: Settings\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}