Follow Discord
Sweep 02 Oct 2026 · 18:55Z Build v2.1.288 509 read Stable v2.1.285 Latest v2.1.287 Next v2.1.288 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.287 ·

The prompt usage-data event is built differently

The usage-data event recorded when you send a prompt now gets its prompt fields from a different step, so its contents may change

You'll notice Improvements
JSON All of v2.1.287
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
TelemetryArea: what it touches
ImprovementsKind: in v2.1.287,
ImprovementsSection of the release
What

When 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.

Why

If you collect these events, the fields they contain, and how prompt text in them is hidden or logged, may differ.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear which fields the event now contains.
Anthropic's release notes agreeAdded prompt_text to the OpenTelemetry user_prompt event, a copy of prompt for backends that nest dotted keys; drop or mask it wherever you…

See this entry in the whole of v2.1.287 →

Feedback