Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
TelemetryArea: what it touches
ImprovementsKind: in v2.1.274,
ImprovementsSection of the release
What
When Claude Code is configured to log raw request and response bodies for OpenTelemetry (OTEL, a standard for exporting logs and metrics), the internal code that writes those dump files now builds its file paths differently and writes the file using an atomic 'replace' operation, instead of writing the file directly and catching errors afterward.
Why
An atomic write means the file is either fully written or not written at all, which avoids leaving behind a half-written or corrupted dump file if the write is interrupted. This is an internal reliability fix for anyone relying on these OTEL debug logs.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed sinceAnthropic's documentation has since written up OTEL_LOG_RAW_API_BODIES, on Modifying system prompts.* **Raw request logging**: set [`OTEL_LOG_RAW_API_BODIES`](/docs/en/monitoring-usage#api-request-body-event) to `file:<dir>`. Claude Code writes each request body to that directory.agent-sdk/modifying-system-promptssee the edit
How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up OTEL_LOG_RAW_API_BODIES, on Modifying system prompts.
Anthropic's release notes agreeImproved OTEL_LOG_RAW_API_BODIES=file:<dir> output: a new index.jsonl and request_body_id / message.id event attributes link each response…
