{"version":"2.1.281","anchor":"new-telemetry-for-the-transcript-deferral-lifecycle","canonical_anchor":"new-telemetry-for-the-transcript-deferral-lifecycle","heading":"New telemetry for the transcript-deferral lifecycle","tier":"soon","area":"Telemetry","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/new-telemetry-for-the-transcript-deferral-lifecycle","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### New telemetry for the transcript-deferral lifecycle\n\nA new telemetry event, tengu_bridge_transcript_deferral, reports each stage of Remote Control's deferred transcript upload\n\n**What**\n\nTelemetry is the usage data Claude Code sends back to Anthropic. A new event, `tengu_bridge_transcript_deferral`, records what happens to a Remote Control transcript whose upload is being held back. It is sent with one of these phases:\n\n- `deferred`\n\n- `released`\n\n- `backfill_dropped`\n\n- `exited_unopened`\n\nIt also carries timing values (`hold_ms`, `deferred_ms`) and counts of messages back-filled and eligible for back-fill.\n\n**Why**\n\nThe event records how long transcripts were held and how many historical messages were sent or dropped when a client connected. Sessions that ended without anyone opening them are recorded too.\n\n- Flag `tengu_noble_snowflake`: Not enough to say (read for one account on one subscription tier against v2.1.281; this account: no value returned, anonymous baseline: no value returned, compiled default: not a boolean we can read) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Telemetry\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}