{"version":"2.1.287","anchor":"cloud-hooks-panel-explains-why-stored-consent-is-not-used","canonical_anchor":"cloud-hooks-panel-explains-why-stored-consent-is-not-used","heading":"Cloud sessions now explain why a saved hooks answer is not used","tier":"notice","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/cloud-hooks-panel-explains-why-stored-consent-is-not-used","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Cloud sessions now explain why a saved hooks answer is not used\n\nIn a cloud session, the hooks panel now says why your saved hooks answer is not being used instead of quietly ignoring it\n\n**What**\n\nHooks are commands that run automatically at set points in a session, and Claude Code asks for your consent before running them. In a cloud session, meaning Claude Code running on Anthropic's servers, the hooks panel now explains when your saved answer is not being used. One example is when the cloud session itself can write to the file that holds that answer. The panel also shows when an answer is not in force.\n\nPreviously the saved answer was quietly reset to unset in these cases.\n\n**Why**\n\nIn a cloud session you now see a reason when you are asked about hooks again, instead of a prompt that seems to ignore your earlier choice.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}