{"version":"2.1.287","anchor":"device-hooks-register-telemetry-broken-out-by-held-reason","canonical_anchor":"device-hooks-register-telemetry-broken-out-by-held-reason","heading":"Device-hook registration telemetry now counts each reason a hook is held","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/device-hooks-register-telemetry-broken-out-by-held-reason","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Device-hook registration telemetry now counts each reason a hook is held\n\nDevice-hook registration telemetry now reports a separate count for each reason a hook is held back\n\n**What**\n\nThe telemetry event sent when the device-hook client registers now reports a count for each reason a hook is held back. Telemetry is usage data Claude Code sends to Anthropic. Device hooks are hooks forwarded to run on your machine. Examples of the new reasons are `held_event_runs_locally` and `held_over_cap`. Before this change, the event only split held hooks into `held_after_edit` and `held_other`.\n\n**Why**\n\nThe report now shows why a device hook was held back, where it previously grouped most cases under one catch-all count.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}