{"version":"2.1.247","anchor":"attaching-to-an-unresponsive-background-session-says-so","canonical_anchor":"attaching-to-an-unresponsive-background-session-says-so","heading":"Attaching to an unresponsive background session says so","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/attaching-to-an-unresponsive-background-session-says-so","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Attaching to an unresponsive background session says so\n\nAttaching to a live but silent background session now says \"Session isn't responding\" instead of a vague error.\n\n**What**\n\nAttaching to a background session that is alive but silent now reports that specific condition instead of failing with an unexplained error. A new ENORESPONSE case, a distinct attach failure meaning the session did not answer, surfaces as \"Session isn't responding\", and the fleet view of running jobs branches on it: a finished job that is not responding shows that fixed message, while a live one goes through the restart prompt.\n\n**Details**\n\n- Both the ENORESPONSE condition and the \"Session isn't responding\" text are new in this build.\n- Attach failures for reasons other than no response are unchanged and still report their own error.\n- The restart prompt text is unchanged: press Enter again to restart it (the conversation is saved).\n- The same area gained a hand-written parser for kitty-protocol keyboard escape sequences, an extended terminal key encoding, matching specific key codes.\n\n**Evidence**\n\n`press Enter again to restart it (the conversation is saved)`, `Session isn't responding`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}