Follow Discord
Sweep 23 Oct 2026 · 21:48Z Build v2.1.310 529 read Stable v2.1.308 Latest v2.1.310 Next v2.1.310 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.310 ·

Tool and permission telemetry now carries the API request_id

Telemetry records of tool use and permission decisions now include the API request_id, and a few other usage records gain extra fields

Group of 4 Under the hood Internal Changes
JSON All of v2.1.310
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
Internal ChangesKind: in v2.1.310,
Internal ChangesSection of the release

What

Claude Code keeps internal usage records, called telemetry, about what happens in a session. Several of these records gain new details:

  • Records of tool use and of permission decisions now include a request_id when one is available. A tool is an action Claude can take, a permission decision is whether a tool call was allowed, and request_id is the ID of the request to Anthropic's API that led to the action.
  • The record written when a conversation is compacted (shortened to save space) takes extra context.
  • Logging of API response bodies now receives the agent context (agentContext).
  • A cached tool-use object now carries a withListings flag.
  • The telemetry.log helper that hooks use can now add engineRaised: true when that option is set. A hook is a script that runs automatically at set points.

Why

With a request_id attached, a tool call or a permission decision can be traced back to the specific API request that produced it. Nothing changes in how you use Claude Code.

See this entry in the whole of v2.1.310 →

Feedback