{"version":"2.1.280","anchor":"remote-tool-serving-adds-detailed-reply-timing-telemetry","canonical_anchor":"remote-tool-serving-adds-detailed-reply-timing-telemetry","heading":"Remote tool serving adds detailed reply-timing telemetry","tier":"internal","area":"Remote Tools","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/remote-tool-serving-adds-detailed-reply-timing-telemetry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Remote tool serving adds detailed reply-timing telemetry\n\nServing a remote tool call now records detailed timing for each stage of the reply\n\n**What**\n\nWhen Claude Code serves a tool call that came in remotely, it now measures and reports how long each step took: serving the call, preparing the reply, and signing or posting the signed reply. This is sent as a `tengu_remote_tool_serve` telemetry event, alongside a matching low-level trace for each step.\n\n**Why**\n\nThis gives finer-grained visibility into where time goes when a remote tool call is answered, which helps diagnose slowness in remote tool execution.\n\n- Area: Remote Tools\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}