{"version":"2.1.268","anchor":"chrome-bridge-tool-result-telemetry-now-includes-response-si","canonical_anchor":"chrome-bridge-tool-result-telemetry-now-includes-response-si","heading":"Chrome bridge tool-result telemetry now includes response size and transport tag","tier":"internal","area":"Chrome & Browser","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/chrome-bridge-tool-result-telemetry-now-includes-response-si","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Chrome bridge tool-result telemetry now includes response size and transport tag\n\nChrome bridge tool-call telemetry now records response size in bytes and tags the transport as \"bridge\"\n\n**What**\n\nThe `chrome_bridge_tool_call_completed` and `chrome_bridge_tool_call_error` telemetry events now include a `transport: \"bridge\"` tag. Completed calls additionally record `response_bytes`, the size of the raw websocket response message.\n\n**Why**\n\nThis gives more detail in telemetry about Claude in Chrome tool calls, letting response payload size and transport type be tracked alongside success and error outcomes.\n\n- Area: Chrome & Browser\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}