{"version":"2.1.76","anchor":"hooks-ui-redesigned-as-read-only-viewer","canonical_anchor":"hooks-ui-redesigned-as-read-only-viewer","heading":"Hooks UI Redesigned as Read-Only Viewer","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.76\/e\/hooks-ui-redesigned-as-read-only-viewer","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.76","markdown":"### Hooks UI Redesigned as Read-Only Viewer\n\nThe `\/hooks` command has been redesigned from a full hook management interface (add, edit, delete) to a read-only viewer. Users can browse hook events, matchers, and see hook details, but can no longer modify hooks through the UI.\n\nWhat changed:\n\n- Removed: \"Add new hook\", \"Delete hook?\", \"Delete matcher?\", \"Save hook configuration\", \"Where should this hook be saved?\" dialogs\n- Added: \"Hook details\" detail view showing event, matcher, type, source, command\/prompt, and status message\n- Added: \"This menu is read-only. To add or modify hooks, edit settings.json directly or ask Claude.\"\n- Added: \"To re-enable hooks, remove `disableAllHooks` from settings.json or ask Claude.\"\n- Navigation: \"Esc to go back\" \/ \"Esc to close\" guides\n- Description changed from \"Manage hook configurations\" to \"View hook configurations\"\n\n**Evidence**\n\nRead-only hooks viewer (search for `\"View hook configurations\"`, `\"This menu is read-only\"`, `\"Hook details\"`)"}