{"version":"2.1.309","anchor":"toolbox-telemetryevent-additions-closed-unrun-follow-ups","canonical_anchor":"toolbox-telemetryevent-additions-closed-unrun-follow-ups","heading":"New internal records for follow-ups, connectors and setup failures","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/toolbox-telemetryevent-additions-closed-unrun-follow-ups","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### New internal records for follow-ups, connectors and setup failures\n\nClaude Code records a few new details about follow-up messages, organisation connector servers and setup failures\n\n**What**\n\nThis release adds several small internal changes:\n\n- A new log entry is recorded when a follow-up message that was sent again is closed without being run.\n\n- MCP servers can carry a new source label for servers that come from an organisation's connectors. MCP (Model Context Protocol) servers give Claude extra tools.\n\n- Reports of a failed setup now include a field saying what kind of failure it was.\n\n- When you resume a session, the check that looks up your local identity is now told that this is a resume. A session is one run of Claude Code from start to finish.\n\n**Why**\n\nThese are groundwork for remote sessions and connectors. On their own they may change little that you can see.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}