Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.221 Home All releases ←olderv2.1.220 v2.1.222newer→
Claude Code v2.1.221

Dead-probe telemetry pruned to two events

Under the hood
Useful2 Signal0
Telemetry

Most of the one-shot probes checking whether old code paths still run were removed.

What

The one-shot tengu_dead_probe_* instrumentation that checked whether legacy code paths were still reached has been almost entirely removed, along with the call sites and the dedupe flags that guarded them.

Details
  • 2.1.220 emitted 32 such events; 2.1.221 has two, tengu_dead_probe_tool_alias_exec and tengu_dead_probe_hook_updated_mcp_tool_output.
  • Removed probes include the plugins v2 dual-file rename and plugins v1 file probe, top-level experimental.themes and experimental.monitors, global-config env, attachment rename, daemon origin: auto, the Chrome legacy-socket scan, the remote-flag alias probe, tengu_dead_probe_plugin_toplevel_experimental, tengu_dead_probe_pinned_sidecar and both tengu_dead_probe_mcp_subsec_timeout call sites in MCP tool timeout and idle timeout resolution.
  • The associated dedupe sets and flush helpers were deleted with them.
Evidence

tengu_dead_probe_, tengu_dead_probe_tool_alias_exec, tengu_dead_probe_mcp_subsec_timeout

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.221 →