{"version":"2.1.224","anchor":"reattaching-to-a-vanished-bridge-session-skips-history-backf","canonical_anchor":"reattaching-to-a-vanished-bridge-session-skips-history-backf","heading":"Reattaching to a vanished bridge session skips history backfill","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/reattaching-to-a-vanished-bridge-session-skips-history-backf","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Reattaching to a vanished bridge session skips history backfill\n\nReattaching to a vanished remote session mints a fresh one without backfilling missing history.\n\n**What**\n\nWhen you reattach to a remote bridge session that no longer exists, Claude Code mints a fresh session instead, and that session is now flagged to skip backfilling history it does not have. The replacement also gets a neutral fallback title rather than inheriting the old one.\n\n**Details**\n\n- The flag is threaded through the transport options, the `bridge-session` transcript entries, the session-state maps and the clear\/save helpers, so it survives save and restore.\n- Triggered by a reattach-target-gone callback; nothing else in the build sets the flag.\n\n**Evidence**\n\n`noHistoryBackfill`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}