Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.224entry #348

Claude Code v2.1.224 ·

Telemetry forwarding now strips identifying fields and caps MCP event volume

Internal metrics forwarding strips identifying fields, buckets tool names and caps per-server MCP volume.

Under the hood Internal Changes
JSON All of v2.1.224
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
TelemetryArea: what it touches
Internal ChangesKind: in v2.1.224,
Internal ChangesSection of the release
What

The internal metrics forwarder, reached only on first-party accounts, now removes a list of potentially identifying fields before sending, collapses tool and feature names into generic buckets, and limits how often per-server MCP events can be sent.

Details
  • Deleted fields include the MCP server base URL and name, the MCP tool name, a hashed error message, and two hashed skill names.
  • Any tool name collapses to mcp when the event is flagged as MCP, where previously only names beginning with mcp__ were collapsed. Names beginning with skill__ become skill, and feature names beginning with tool_skill_ become tool_skill, except tool_skill_tool.
  • Five MCP events are capped at 10 forwards per 60 second window per server, tracked across at most 200 server keys, and the count suppressed since the last send rides along as droppedSinceLastForward.
Evidence

stripPiiFieldsForDatadog

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.224 →

Feedback