{"version":"2.1.246","anchor":"clearer-warning-when-a-saved-hooks-answer-cannot-be-reused-i","canonical_anchor":"clearer-warning-when-a-saved-hooks-answer-cannot-be-reused-i","heading":"Clearer warning when a saved hooks answer cannot be reused in a cloud session","tier":"notice","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/clearer-warning-when-a-saved-hooks-answer-cannot-be-reused-i","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Clearer warning when a saved hooks answer cannot be reused in a cloud session\n\nThe warning about a set-aside hooks decision in a cloud session is now one short line pointing at \/hooks.\n\n**What**\n\nThe warning shown when your stored decision about this machine's hooks is set aside, because the cloud session can write to the files involved, is now a shorter sentence pointing you at \/hooks.\n\n**Details**\n\n- Classifying a hook script now goes through one helper returning unverifiable, reachable by the session, or outside its reach, replacing inline path and digest checks.\n- The consent telemetry event name is unchanged.\n\n**Evidence**\n\n`The saved answer about this machine's hooks is ignored here: this cloud session can itself write `\n\n- Area: Hooks\n- Names: `\/hooks`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}