{"version":"2.1.282","anchor":"update-config-skill-no-longer-points-users-to-hooks-when-th","canonical_anchor":"update-config-skill-no-longer-points-users-to-hooks-when-th","heading":"Settings skill stops sending you to \/hooks where that menu is missing","tier":"notice","area":"Hooks","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/update-config-skill-no-longer-points-users-to-hooks-when-th","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Settings skill stops sending you to `\/hooks` where that menu is missing\n\nWhen the `\/hooks` menu is not available, the settings skill now tells you to start a new session or check the settings file instead\n\n**Unclear.** It is not clear exactly which environments count as having no `\/hooks` menu.\n\n**What**\n\nThe Update Config skill helps Claude change your Claude Code settings, including hooks (commands that run automatically on certain events). After adding a hook, it used to always tell you to open `\/hooks` once to reload the settings, or restart.\n\nWhere the `\/hooks` menu is not available, it now tells you to start a new session so the new settings load, or to review the hook in the settings file that was written. Everywhere else it still points to `\/hooks`.\n\n**Why**\n\nThis stops Claude from telling people, for example those using Claude Code through the SDK or remotely, to open a menu they do not have.\n\n- Area: Hooks\n- Names: `\/hooks`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}