{"version":"2.1.296","anchor":"telemetry-error-attribute-is-dropped-if-it-is-not-a-snake-ca","canonical_anchor":"telemetry-error-attribute-is-dropped-if-it-is-not-a-snake-ca","heading":"Usage data now drops error text that is not a short code","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/telemetry-error-attribute-is-dropped-if-it-is-not-a-snake-ca","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Usage data now drops error text that is not a short code\n\nAn `error` value in usage data is dropped unless it is a short code of lowercase letters, digits and underscores\n\n**What**\n\nWhen Claude Code logs usage events, it now drops an `error` value unless it is made only of lowercase letters, digits and underscores, such as `timeout` or `not_found`. Before, every value was copied into the event unchanged. In some sessions the event details are also passed through an extra cleaning step.\n\n**Why**\n\nFree-text error messages can contain things like file paths or message content. Keeping only short codes keeps that text out of usage data.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}