{"version":"2.1.287","anchor":"user-prompt-telemetry-now-built-by-a-helper-that-spreads-fie","canonical_anchor":"user-prompt-telemetry-now-built-by-a-helper-that-spreads-fie","heading":"The prompt usage-data event is built differently","tier":"notice","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/user-prompt-telemetry-now-built-by-a-helper-that-spreads-fie","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### The prompt usage-data event is built differently\n\nThe usage-data event recorded when you send a prompt now gets its prompt fields from a different step, so its contents may change\n\n**Unclear.** It is not clear which fields the event now contains.\n\n**What**\n\nWhen you send a prompt, Claude Code records a usage-data event called `user_prompt`, which can be exported through OpenTelemetry (a standard for sending usage data to monitoring tools). The event used to carry a single `prompt` field. It now takes its fields from a different step that works on the raw prompt text, so the event can hold several fields.\n\n**Why**\n\nIf you collect these events, the fields they contain, and how prompt text in them is hidden or logged, may differ.\n\n- Area: Telemetry\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}