{"version":"2.1.317","anchor":"headless-telemetry-events-added","canonical_anchor":"headless-telemetry-events-added","heading":"Headless sessions record more detail about re-delivered messages","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/headless-telemetry-events-added","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Headless sessions record more detail about re-delivered messages\n\nHeadless Claude Code now records what happens to repeated user messages, plus new records about MCP requests and per-turn effort caps\n\n**What**\n\nIn headless mode, Claude Code runs without its interactive screen and is driven by another program or a remote session. In this mode it now keeps more diagnostic records:\n\n- Re-delivered messages: sometimes the same user message, recognised by its unique ID (UUID), arrives a second time. Claude Code now records what happened to it. It may have run again, been left unanswered, been handed to a turn that was parked and waiting, or have been done even though it was cut off.\n\n- Duplicate check log: the log used to spot duplicate messages now also carries `tail_kind` and `tail_shutdown_stamped`.\n\n- Two other new records: one appears to concern MCP requests handled outside the main loop, and one a cap on effort for each turn. MCP (Model Context Protocol) is the way Claude Code connects to outside tools and servers. Effort is how much thinking Claude puts into a reply.\n\n**Why**\n\nNothing you see changes. In practice these records give more detail about how headless and remote sessions handle a message that arrives twice. The new effort-cap record is also a sign that turns in headless mode can carry an effort limit.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}