{"version":"2.1.280","anchor":"hooks-errors-carry-a-sanitized-telemetry-message","canonical_anchor":"hooks-errors-carry-a-sanitized-telemetry-message","heading":"Hooks errors carry a sanitized telemetry message","tier":"internal","area":"Hooks","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/hooks-errors-carry-a-sanitized-telemetry-message","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Hooks errors carry a sanitized telemetry message\n\nHook errors now report a generic message to telemetry instead of the actual error text\n\n**What**\n\nWhen a function hook (a custom script that runs at certain events) throws an error, Claude Code now attaches a fixed, generic `telemetryMessage` to the resulting `HooksError`. That generic placeholder is what gets sent to telemetry, not the hook's actual error text.\n\n**Why**\n\nHooks can be authored by plugins or other third parties, so their error messages might contain private or sensitive details. Sending a generic message instead protects that information from ending up in telemetry.\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}