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.265,
Internal ChangesSection of the release
What
When Claude Code detects an inconsistency in a tool's recorded input (via the tether_wire_tool_input telemetry event), the event now also includes the tool's name (toolName) and whether it came from an MCP server (isMcp), an external tool provider connected via the Model Context Protocol.
Why
This gives more context for diagnosing which specific tool, and whether an MCP-provided one, triggered an inconsistent recorded input, making it easier to track down the source of such issues.
