{"version":"2.1.239","anchor":"hooks-owned-by-a-connected-device-now-obey-hook-policy","canonical_anchor":"hooks-owned-by-a-connected-device-now-obey-hook-policy","heading":"Hooks owned by a connected device now obey hook policy","tier":"notice","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/hooks-owned-by-a-connected-device-now-obey-hook-policy","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Hooks owned by a connected device now obey hook policy\n\nHooks owned by a paired device are skipped when managed-hooks-only policy applies.\n\n**What**\n\nHook definitions that carry a device-owner marker are skipped whenever the managed-hooks-only policy is in force, or when hooks are disabled for the settings file they came from. The skip applies both when hooks run and when Claude Code checks whether any hooks exist at all.\n\n**Details**\n\n- Same treatment on both paths, so a suppressed device hook does not make the session look hook-enabled.\n- Device hooks travel over the connection to the device as tagged callback requests, each with an id, a deadline and a cancel handle.\n- Malformed and failed replies are counted, and a warning is logged once more than 512 such requests are outstanding at once.\n\n**Evidence**\n\n`deviceOwner`\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}