{"version":"2.1.238","anchor":"new-telemetry-when-the-claude-in-chrome-server-lists-its-too","canonical_anchor":"new-telemetry-when-the-claude-in-chrome-server-lists-its-too","heading":"New telemetry when the Claude-in-Chrome server lists its tools","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/new-telemetry-when-the-claude-in-chrome-server-lists-its-too","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### New telemetry when the Claude-in-Chrome server lists its tools\n\nRunning the Chrome extension's MCP server now logs how many browser tools were added, once per session.\n\n**What**\n\nListing tools from an MCP server that runs over a local process and identifies itself as `claude-in-chrome` now records a `tengu_chrome_tools_added` event with the tool count and the discovery source, at most once per session. No flag guards it; it fires for anyone running the Chrome extension's MCP server.\n\n**Evidence**\n\n`tengu_chrome_tools_added`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}