{"version":"2.1.273","anchor":"relayawaitshandoff-flag-threaded-through-resumefork-startup","canonical_anchor":"relayawaitshandoff-flag-threaded-through-resumefork-startup","heading":"relayAwaitsHandoff flag threaded through resume\/fork startup and teleport-boot telemetry","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/relayawaitshandoff-flag-threaded-through-resumefork-startup","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### relayAwaitsHandoff flag threaded through resume\/fork startup and teleport-boot telemetry\n\nA new relayAwaitsHandoff signal is now tracked through session resume\/fork startup\n\n**Unclear.** What relayAwaitsHandoff represents and what behavior change it produces beyond the telemetry annotation is not stated.\n\n**What**\n\nA new value called `relayAwaitsHandoff` is now passed into the configuration used when a session starts up during resume or fork, and it's used to annotate a teleport-boot telemetry event (recording when a \"teleport boot\" doesn't get reached) as well as a check for empty hydration (loading of prior session state).\n\n**Why**\n\nThis gives Claude Code's telemetry and startup logic more precise information about when a session is waiting on a handoff during resume or fork, though the finding doesn't specify the exact effect for users.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}