{"version":"2.1.287","anchor":"cloud-session-hook-skip-messages-reworded","canonical_anchor":"cloud-session-hook-skip-messages-reworded","heading":"Clearer reasons, with fixes, when a hook cannot run in a cloud session","tier":"notice","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/cloud-session-hook-skip-messages-reworded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Clearer reasons, with fixes, when a hook cannot run in a cloud session\n\nWhen a hook cannot run for a cloud session, Claude Code now says why in plainer words and how to fix it\n\n**What**\n\nHooks are scripts you set up to run automatically at certain points, for example after Claude edits a file. When a hook cannot run for a cloud session (a session that runs on a remote machine rather than yours), Claude Code shows a reason. Those reasons have been reworded:\n\n- After-edit hooks: instead of saying they stay local for now, the message explains that cloud edits change files in the cloud and tells you to put the hook in the repository's `.claude\/settings.json`.\n\n- Hooks for events that happen on your own machine: the reason is now shorter.\n\n- Hooks whose script the cloud session could change: the message tells you to move the script to `~\/.claude\/hooks`.\n\n**Why**\n\nIf an after-edit hook does not fire in a cloud session, the message now tells you what to do about it rather than only that it was skipped.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5"}