{"version":"2.1.311","anchor":"new-telemetry-event-names-and-a-chat-relay-status-schema","canonical_anchor":"new-telemetry-event-names-and-a-chat-relay-status-schema","heading":"Two more internal event types and a status format appear","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/new-telemetry-event-names-and-a-chat-relay-status-schema","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Two more internal event types and a status format appear\n\nClaude Code can record two more kinds of usage event and has a data format for describing a status, with nothing visible using them yet\n\n**What**\n\nClaude Code can now record two more kinds of usage event, named chat_relay_standing_ask and chrome_late_mcp_server. A usage event is a short record of something that happened while you use Claude Code. MCP, in the second name, is the system Claude Code uses to connect extra tools.\n\nThere is also a data format for describing a status, with these fields:\n\n- status_category\n\n- status_detail\n\n- needs_action\n\n- standing, reply and description, which are optional\n\n**Why**\n\nNothing you can see uses these yet. The names point to a chat relay feature with a \"standing ask\" and to handling a Chrome MCP server that arrives late.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}