Claude Code v2.1.239 · 21 Aug 2026
Deferred tool calls carry trace context to hooks
Deferred tool-call notifications now carry a traceparent so hook consumers can correlate them.
Under the hood
No documentation found Improvements
Copy link
Copy markdown
JSON
All of v2.1.239
Under the hood Tier: how much it should matter to you
2 Useful: my rating, 1 to 5
2 Signal: worth watching, 1 to 5
Hooks Area: what it touches
Improvements Kind: in v2.1.239, 21 Aug 26
Improvements Section of the release
What
When a PreToolUse hook defers a tool call, the notification sent out now includes a W3C traceparent value, so hook consumers can line the deferred call up with the surrounding trace.
Details
Sits alongside the existing hookName, hookEvent: "PreToolUse " and permissionMode fields. The value comes from the existing trace-context helper and the field is omitted entirely when there is no active trace. Evidence
hookEvent: "PreToolUse"
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
How sure we are
One source agrees One thing we can check says the same as this entry.
Anthropic's release notes agree Fixed OpenTelemetry trace fragmentation: tool executions deferred by a PreToolUse hook now resume in the original turn's trace instead of…
See this entry in the whole of v2.1.239 →
21 Aug 2026 · 300 entries, this one is #183.
Use it now41 You'll notice160 Nothing to try yet37 Under the hood62
Open the release →
Names in this entry
hook PreToolUse Before a tool call executes. Can block it
setting traceparent Telemetry spans can now join a trace that was started by whatever called in.
setting permissionMode SDK callers can let the CLI pick the permission mode from settings instead of forcing "default".
Anthropic's note
Upstream's own release notes for v2.1.239 name something this entry names, so the two are probably about the same change. Probably: the pairing is made on a shared name rather than on the words around it.
Fixed OpenTelemetry trace fragmentation: tool executions deferred by a PreToolUse hook now resume in the original turn's trace instead of starting a new trace
Is this right?
0
0
Feedback
What's wrong with this entry?
Hard to understand Too vague Looks wrong Not relevant to me Too long Missing the detail I wanted Duplicate of another card
Clear Learned something new I can act on this Good catch
← Previous · 182 of 300
Clearer refusal when a session tries to message itself
You'll notice Session Messaging
In v2.1.239 Improvements release-page order
Next → · 184 of 300
Agent listing tells apart a failed local lookup and messaging being off
You'll notice Session Messaging