{"version":"2.1.288","anchor":"cloud-session-hook-sync-messages-reworded-remote-hook-failu","canonical_anchor":"cloud-session-hook-sync-messages-reworded-remote-hook-failu","heading":"Clearer messages about hooks in cloud sessions","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/cloud-session-hook-sync-messages-reworded-remote-hook-failu","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Clearer messages about hooks in cloud sessions\n\nMessages about hooks that can't run in a cloud session were reworded, and a failed plugin hook on another machine is now logged as an error\n\n**Unclear.** It is not clear how widely hooks in cloud sessions are available.\n\n**What**\n\nA hook is a script Claude Code runs automatically at set moments. A cloud session runs on another machine. Messages about hooks there have changed:\n\n- An unreadable hook is now described as one that \"this machine could not verify what it runs\".\n\n- Hooks that cannot be used now come with advice: check the script, then move it to `~\/.claude\/hooks`. An inline command should become one script in `~\/.claude\/hooks`.\n\n- The warning now says hooks start in an empty folder. A hook in your user settings marked `\"cloud\": \"device\"` starts in the project instead, where the cloud session can change files.\n\n- A plugin hook that fails on another machine is now logged as an error.\n\n**Why**\n\nWhen a hook does not work in a cloud session, the message now says more clearly what is wrong and how to fix it.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}