You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
HooksArea: what it touches
ImprovementsKind: in v2.1.287,
ImprovementsSection of the release
What
Hooks are commands you set up to run at certain points in a session, such as before a tool runs. Some hooks run on your own machine while the session runs elsewhere. When that machine stops answering in time:
Claude is told the hooks are paused, that tool calls (Claude's actions such as reading a file or running a command) go ahead without them, and that if you ask whether your hooks ran, it should say they were paused.
You get a message about it.
When the machine answers again, you get a message that hooks have resumed.
These notices are limited so they are not repeated too often. Before, you got a single message that the machine stopped answering, and Claude was not told.
Why
If you ask Claude whether your hooks ran during a gap, it can now tell you they were paused instead of guessing.
