{"version":"2.1.271","anchor":"claude-edit-hook-now-emits-telemetry-for-its-outcomes","canonical_anchor":"claude-edit-hook-now-emits-telemetry-for-its-outcomes","heading":"claude edit-hook now emits telemetry for its outcomes","tier":"internal","area":"IDE Integration","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/claude-edit-hook-now-emits-telemetry-for-its-outcomes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### `claude edit-hook` now emits telemetry for its outcomes\n\nThe hidden `claude edit-hook` command now sends telemetry for each outcome\n\n**What**\n\n`claude edit-hook` is a hidden command that the VS Code extension uses internally to apply changes to hooks (scripts that run automatically at certain points). It now sends telemetry events recording what happened each time it runs: whether it was invoked from a terminal (TTY), whether the input it received was invalid JSON, which error code caused a failure, or whether it succeeded.\n\n**Why**\n\nThis gives visibility into how reliably the VS Code extension's hook-editing feature is working, without changing what the command does for anyone using it.\n\n- Area: IDE Integration\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}