{"version":"2.1.281","anchor":"new-resume-telemetry-for-first-turn-announcements","canonical_anchor":"new-resume-telemetry-for-first-turn-announcements","heading":"New resume telemetry for first-turn announcements","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/new-resume-telemetry-for-first-turn-announcements","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### New resume telemetry for first-turn announcements\n\nTwo new telemetry events count context entries that land off the message chain around the first turn of a resumed session\n\n**What**\n\nTelemetry is usage data Claude Code reports back. Two new events were added around resuming, which means reopening an earlier conversation:\n\n- `tengu_resume_first_turn_announcement_census` is sent every time a session is loaded for resume.\n\n- `tengu_chain_first_turn_announcements_off_chain` is sent once per session file while the conversation's message chain is rebuilt.\n\nBoth measure context entries, such as instructions, the date and session context, that end up outside the message chain around the first turn.\n\n**Why**\n\nThese events only measure. They do not change how resuming behaves."}