Under the hood
OTEL debug logging of raw request/response bodies now writes files atomically instead of writing then handling errors after the fact
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.
Names in the bundleOTEL_LOG_RAW_API_BODIES
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agree
Improved OTEL_LOG_RAW_API_BODIES=file:<dir> output: a new index.jsonl and request_body_id / message.id event attributes link each response…