{"version":"2.1.288","anchor":"held-project-hook-asks-re-prompt-after-hook-changes","canonical_anchor":"held-project-hook-asks-re-prompt-after-hook-changes","heading":"Project hooks that changed after approval now ask again in remote sessions","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/held-project-hook-asks-re-prompt-after-hook-changes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Project hooks that changed after approval now ask again in remote sessions\n\nIn remote sessions, a project hook that changed after you approved it is now held until you give permission again\n\n**Unclear.** The exact wording you see when asked again, and whether this is switched on for everyone, is not clear.\n\n**What**\n\nA hook is a command a project sets up to run automatically at certain moments. In a remote session that is running tools, a project hook that has changed since you approved it is now held, and Claude Code asks you for permission again before running it. Notes are recorded about the outcome, for example that you accepted the updated hook, and Claude Code keeps count when you decline more than once.\n\nPreviously the outcome was only that the hook ran in a sandbox (a restricted environment that limits what it can touch) or that you were asked.\n\n**Why**\n\nThis changes how approval works for project hooks in remote sessions. Approving a hook once no longer covers a later, changed version of it, so expect to be asked again after a project edits its hooks.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}