{"version":"2.1.247","anchor":"a-saved-yes-for-device-hooks-and-cloud-plugins-is-ignored-if","canonical_anchor":"a-saved-yes-for-device-hooks-and-cloud-plugins-is-ignored-if","heading":"A saved \"yes\" for device hooks and cloud plugins is ignored if the session could have edited it","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/a-saved-yes-for-device-hooks-and-cloud-plugins-is-ignored-if","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### A saved \"yes\" for device hooks and cloud plugins is ignored if the session could have edited it\n\nA saved yes to forwarding hooks and plugins is ignored if the cloud session could have edited that file.\n\n**What**\n\nBefore honouring a previously accepted answer about forwarding your hooks and plugins to a cloud session, Claude Code now checks whether the file holding that answer sits somewhere the session can write: the checkout, a synced directory, or a sandbox write inlet. If it does, or if that cannot be determined, the stored acceptance is refused as `untrusted_store` and you are asked to decide again interactively.\n\n**Details**\n\n- The refusal text is surfaced as the reason the feature is off: run `\/cloud-plugins` to decide for the session.\n- Only reachable when device-hook or cloud-plugin forwarding is in play (`claude --cloud`); the distrust check itself always runs there.\n\n**Evidence**\n\n`the saved answer here could be changed by this session; run \/cloud-plugins to decide for it`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5"}