{"version":"2.1.300","anchor":"hook-runs-on-another-machine-timeouts-distinguished-org-ho","canonical_anchor":"hook-runs-on-another-machine-timeouts-distinguished-org-ho","heading":"Remote hook timeouts are reported separately, and organization hooks set up differently","tier":"notice","area":"Hooks","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/hook-runs-on-another-machine-timeouts-distinguished-org-ho","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Remote hook timeouts are reported separately, and organization hooks set up differently\n\nHooks that run on another machine now report timing out separately from failing, and organization hooks no longer start with a plugin's environment\n\n**What**\n\nHooks are your own commands that Claude Code runs at set points, such as before a tool runs. Several things about them have changed:\n\n- A hook that runs on another machine now reports when it timed out, separately from when it failed for another reason. Before, every failure was reported the same way.\n\n- Hooks set by your organization now start without the environment variables a plugin sets, and a message is logged when this happens.\n\n- Environment variables from managed settings, the settings an organization controls, are applied.\n\nThe way hooks are registered has also been reworked.\n\n**Why**\n\nThis affects how organization hook policy is enforced. A timeout is now easier to tell apart from other failures.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: both\n- Heads-up: no"}