{"version":"2.1.268","anchor":"chrome-bridge-tool-calls-now-emit-a-start-telemetry-event-wi","canonical_anchor":"chrome-bridge-tool-calls-now-emit-a-start-telemetry-event-wi","heading":"Chrome bridge tool calls now emit a start telemetry event with request size","tier":"internal","area":"Chrome & Browser","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/chrome-bridge-tool-calls-now-emit-a-start-telemetry-event-wi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Chrome bridge tool calls now emit a start telemetry event with request size\n\nChrome bridge tool calls now log a start event that includes the size of the outgoing request\n\n**What**\n\nBefore Claude Code dispatches a tool call through the Chrome bridge (the connection to the Claude in Chrome browser extension), it now emits a `chrome_bridge_tool_call_started` telemetry event. It records the tool name, session ID, message ID, timeout, transport method, and the byte size of the request, calculated from the combined permission and allowed-domains data being sent.\n\n**Why**\n\nThis gives visibility into how large and how often Chrome bridge requests are, which can help diagnose performance or timeout issues with browser-based tool calls.\n\n- Area: Chrome & Browser\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}