{"version":"2.1.292","anchor":"teleport-handoff-relay-gets-staged-diagnostics-and-a-handoff","canonical_anchor":"teleport-handoff-relay-gets-staged-diagnostics-and-a-handoff","heading":"Teleport handoff records more detail about why a handoff did not go through","tier":"internal","area":"Teleport","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/teleport-handoff-relay-gets-staged-diagnostics-and-a-handoff","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Teleport handoff records more detail about why a handoff did not go through\n\nTeleport handoffs now record specific reasons when the handoff marker is not used, and report a crash during startup as a boot failure\n\n**What**\n\nWhen Claude Code hands a session over through teleport, it checks for a marker that tells it to pass the turn along. That check now records a specific reason when it does not go ahead, such as the relay not being set up or the turn already having been answered. Before, the reasons were free text.\n\nIt also records which stage it reached, records a warning if the marker is never used, and reports a failure during startup as `boot_failed`.\n\n**Why**\n\nThis only changes the usage data Claude Code records. Handoffs work the same way, but problems with them are easier to track down.\n\n- Area: Teleport\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}