{"version":"2.1.269","anchor":"new-edit-hook-tooldialog-for-adding-replacing-and-removing","canonical_anchor":"new-edit-hook-tooldialog-for-adding-replacing-and-removing","heading":"New edit_hook tool\/dialog for adding, replacing and removing hooks","tier":"internal","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/new-edit-hook-tooldialog-for-adding-replacing-and-removing","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### New edit_hook tool\/dialog for adding, replacing and removing hooks\n\nNew internal edit_hook system lets settings be edited to add, replace, or remove hooks\n\n**Unclear.** Whether a user-facing UI or command already exposes this editor, or it is purely internal plumbing so far, isn't shown by the evidence.\n\n**What**\n\nClaude Code has gained a full internal editor for hook configuration (hooks are commands Claude Code can run automatically at certain points, such as before or after a tool call). It can add, replace, or remove a hook entry; validates the operation against the event, matcher, and source (user, project, or local settings file) it targets; checks whether managed settings policy blocks the edit; and writes the change back to the right settings file. It also assembles a summary of configured hooks, including which are disabled and which are editable, and accounts for \"safe mode\" and \"bare mode\" states.\n\n**Why**\n\nThis lays the groundwork for a hooks management interface, so hooks could eventually be added, changed, or removed without hand-editing settings files directly.\n\n- Area: Hooks\n- Names: `edit_hook`\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 3\/5"}