Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
TelemetryArea: what it touches
Internal ChangesKind: in v2.1.287,
Internal ChangesSection of the release
What
The 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.
Why
The report now shows why a device hook was held back, where it previously grouped most cases under one catch-all count.
