{"version":"2.1.314","anchor":"asyncrewake-hooks-missing-script-detection-can-be-supplied","canonical_anchor":"asyncrewake-hooks-missing-script-detection-can-be-supplied","heading":"Background rewake hooks can report a missing script in a new way","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/asyncrewake-hooks-missing-script-detection-can-be-supplied","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Background rewake hooks can report a missing script in a new way\n\nWhen an `asyncRewake` hook exits with code 2, Claude Code can now use a separate missing-script check instead of reading the output\n\n**What**\n\nFor `asyncRewake` hooks, background commands that run at set moments, Claude Code now handles a missing script differently. Exit code 2 is the number a script returns to signal a problem. When such a hook exits with it, except for a Stop hook, Claude Code can now use a separate check for whether the hook's script could not be found, instead of only reading the hook's output.\n\nThis check also spots when the same missing script is reported again. The hook's summary is now trimmed by a shared step.\n\n**Why**\n\nReports that a hook could not open its script should be clearer.\n\n- Area: Hooks\n- Names: `asyncRewake`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}