{"version":"2.1.228","anchor":"reaped-bridge-sessions-are-unarchived-before-reattaching","canonical_anchor":"reaped-bridge-sessions-are-unarchived-before-reattaching","heading":"Reaped bridge sessions are unarchived before reattaching","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/reaped-bridge-sessions-are-unarchived-before-reattaching","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Reaped bridge sessions are unarchived before reattaching\n\nResuming an older reaped session now unarchives it first instead of failing.\n\n**What**\n\nOn resume, a bridge session that was reaped is unarchived first and then reattached, so resuming an older session works instead of failing. Controlled by `tengu_bridge_unarchive_on_resume`, which defaults to on in this build.\n\n**Details**\n\n- The unarchive call is retried once through the trusted-device path.\n- A 409 is read as another client having already unarchived the session, and resume continues without undoing anything.\n\n**Evidence**\n\n`tengu_bridge_unarchive_on_resume`\n\n- Flag `tengu_bridge_unarchive_on_resume`: Gate removed from the code (read for one account on one subscription tier against v2.1.228; this account: on, anonymous baseline: on, 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: Sessions\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5"}