{"version":"2.1.246","anchor":"cloud-sessions-explain-which-of-your-hooks-cannot-be-pinned","canonical_anchor":"cloud-sessions-explain-which-of-your-hooks-cannot-be-pinned","heading":"Cloud sessions explain which of your hooks cannot be pinned","tier":"use","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/cloud-sessions-explain-which-of-your-hooks-cannot-be-pinned","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Cloud sessions explain which of your hooks cannot be pinned\n\nCloud sessions now tell you which of your hooks couldn't be pinned and were skipped.\n\n**What**\n\nWhen forwarding your machine's hooks to a cloud session (`claude --cloud`), each hook is now checked for whether its script or its config file sits somewhere the cloud session could itself write to. Hooks that cannot be pinned, because they are not a single script, are unreadable, hard-linked or oversized, or live inside the checkout, get a notice saying so and are not run. Successful registrations went quiet.\n\n**Details**\n\n- The routine registration summary and the \"this window now runs your hooks\" line dropped from info to debug level.\n- No separate flag; this applies on the cloud hook forwarding path.\n\n**Evidence**\n\n`is not a single script this machine can pin, so it is not run for the cloud session from this machine`\n\n- Area: Cloud Sessions\n- Names: `--cloud`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5"}