{"version":"2.1.288","anchor":"served-project-hook-handling-reworked-set-aside-and-recorde","canonical_anchor":"served-project-hook-handling-reworked-set-aside-and-recorde","heading":"Project hooks that changed after a session attached can be set aside or run as recorded","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/served-project-hook-handling-reworked-set-aside-and-recorde","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Project hooks that changed after a session attached can be set aside or run as recorded\n\nServed sessions gain a mode where a project hook that changed since attaching is set aside or run as recorded, not always held\n\n**Unclear.** What switches this mode on is not known.\n\n**What**\n\nA hook is a command that Claude Code runs automatically at certain points, and a project can supply its own hooks. In sessions where hooks are served to Claude Code, a project hook that changed after the session attached was always held for your approval. There is now a mode in which such a hook is instead either set aside or run in the form that was recorded earlier. In that mode, Claude Code also asks a separate question about each hook that was updated.\n\n**Why**\n\nThis changes what happens to project hooks that are edited partway through a remote or served session.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}