{"version":"2.1.239","anchor":"remote-handoff-reports-bundling-progress-and-records-why-it-","canonical_anchor":"remote-handoff-reports-bundling-progress-and-records-why-it-","heading":"Remote handoff reports bundling progress and records why it bundled","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/remote-handoff-reports-bundling-progress-and-records-why-it-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Remote handoff reports bundling progress and records why it bundled\n\nHanding work to a remote session now shows bundling progress and names the fallback on failure.\n\n**What**\n\nThe flow that ships your working tree to a remote session now emits progress while it bundles, reports a bundle failure along with the fallback it will use instead, and checks for cancellation before bundling starts.\n\n**Details**\n\n- A new telemetry event, `tengu_teleport_bundle_started`, records the reason bundling was needed.\n- Progress callbacks cover the `bundling` stage and a `bundle_failed` stage carrying the fallback.\n- Adds a `title-await` phase log, and carries the destination repository through the flow so the git source is assembled later.\n\n**Evidence**\n\n`tengu_teleport_bundle_started`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}