{"version":"2.1.287","anchor":"device-hook-absence-notices-pauseresume-messages","canonical_anchor":"device-hook-absence-notices-pauseresume-messages","heading":"Claude is told when hooks on your machine are paused, and you hear when they resume","tier":"notice","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/device-hook-absence-notices-pauseresume-messages","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Claude is told when hooks on your machine are paused, and you hear when they resume\n\nWhen hooks on your own machine stop answering, Claude is now told they are paused and you get notices when they pause and resume\n\n**What**\n\nHooks 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:\n\n- 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.\n\n- You get a message about it.\n\n- When the machine answers again, you get a message that hooks have resumed.\n\nThese 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.\n\n**Why**\n\nIf you ask Claude whether your hooks ran during a gap, it can now tell you they were paused instead of guessing.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}