{"version":"2.1.288","anchor":"cloud-hook-forwarding-notices-rewritten-and-held-hooks-gain","canonical_anchor":"cloud-hook-forwarding-notices-rewritten-and-held-hooks-gain","heading":"Shorter reasons when a hook is not sent to a cloud session","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/cloud-hook-forwarding-notices-rewritten-and-held-hooks-gain","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Shorter reasons when a hook is not sent to a cloud session\n\nWith `claude --cloud`, notices about hooks held back are shorter and give a cause, with a warning when a changed guard hook blocks tool calls\n\n**Unclear.** It is not known whether this applies to every user of `claude --cloud`.\n\n**What**\n\nWhen you run `claude --cloud`, Claude Code tries to carry your hooks (your own commands that run at set moments) over to the cloud session. When it holds one back, the notice is now shorter and states the cause. For example, a hook script is now reported because its script may load files the cloud session can change, replacing a longer explanation. Held hooks now record:\n\n- Why they were held, such as running through your `CLAUDE_CODE_SHELL_PREFIX`, which this machine cannot verify, or living in a folder whose name starts with a dot.\n\n- Whether there is no fix you can apply.\n\nWhen a hook's script has changed and it guards a `PreToolUse` hook (one that runs before a tool call and can block it), the warning now adds \"Matching tool calls are blocked.\" It also tells you to check the file and then restart `claude --cloud`.\n\n**Why**\n\nYou get a clear, short reason why a hook did not move to the cloud session, and a warning when a hook that guards tool calls is stopping them.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}