{"version":"2.1.307","anchor":"telemetry-event-names-added","canonical_anchor":"telemetry-event-names-added","heading":"New usage-event names for MCP connections and queued messages","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/telemetry-event-names-added","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### New usage-event names for MCP connections and queued messages\n\nClaude Code's list of usage events now includes names tied to MCP connections and to handling queued messages\n\n**What**\n\nClaude Code keeps a list of usage events it can report about how it is used. That list now includes new names, two of them about MCP connections. MCP (Model Context Protocol) is the way Claude Code connects to outside tools and servers. The new names cover:\n\n- a handoff involving claude.ai\n\n- dialling an MCP connection again after it was suspended\n\n- messages you queue while Claude is working, including putting a queued message back\n\n**Why**\n\nNew event names change nothing you see on their own. They may point to MCP behaviour that other changes in this release introduce.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}