{"version":"2.1.296","anchor":"settings-blocking-denial-reason-reworded-to-include-hooks","canonical_anchor":"settings-blocking-denial-reason-reworded-to-include-hooks","heading":"Settings error that blocks tool calls now mentions hooks too","tier":"notice","area":"Settings","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/settings-blocking-denial-reason-reworded-to-include-hooks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Settings error that blocks tool calls now mentions hooks too\n\nThe message shown when a settings problem blocks tool calls now names your hooks as well as your settings\n\n**What**\n\nSometimes a problem in your own configuration stops Claude Code from running tools. A tool call is one action Claude takes, such as reading a file or running a command. The reason Claude Code gives now reads \"A problem with your own settings or hooks is blocking tool calls\". Before, it named only your user settings file.\n\nHooks are commands you set up to run automatically at certain points, for example before a tool runs.\n\n**Why**\n\nIf you see this message, check your hooks as well as your settings file. The cause may be in either one.\n\n- Area: Settings\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}