Use it now
Useful3 Signal3
Cloud sessions now tell you which of your hooks couldn't be pinned and were skipped.
What's wrong with this entry?
Anonymous. No account, no email.
--cloud
What
When 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.
Details
- The routine registration summary and the "this window now runs your hooks" line dropped from info to debug level.
- No separate flag; this applies on the cloud hook forwarding path.
Evidence
is not a single script this machine can pin, so it is not run for the cloud session from this machine
Strings lifted out of the shipped bundle, so the claim above can be checked against them.