Follow Discord
Sweep 02 Oct 2026 · 18:55Z Build v2.1.288 509 read Stable v2.1.285 Latest v2.1.287 Next v2.1.288 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.287 ·

Clearer reasons, with fixes, when a hook cannot run in a cloud session

When a hook cannot run for a cloud session, Claude Code now says why in plainer words and how to fix it

You'll notice Improvements
JSON All of v2.1.287
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
HooksArea: what it touches
ImprovementsKind: in v2.1.287,
ImprovementsSection of the release
What

Hooks 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:

  • 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.
  • Hooks for events that happen on your own machine: the reason is now shorter.
  • Hooks whose script the cloud session could change: the message tells you to move the script to ~/.claude/hooks.
Why

If 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.

See this entry in the whole of v2.1.287 →

Feedback