You'll notice
Useful3 Signal2
Attaching to a live but silent background session now says "Session isn't responding" instead of a vague error.
What's wrong with this entry?
Anonymous. No account, no email.
What
Attaching 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.
Details
- Both the ENORESPONSE condition and the "Session isn't responding" text are new in this build.
- Attach failures for reasons other than no response are unchanged and still report their own error.
- The restart prompt text is unchanged: press Enter again to restart it (the conversation is saved).
- The same area gained a hand-written parser for kitty-protocol keyboard escape sequences, an extended terminal key encoding, matching specific key codes.
Evidence
press Enter again to restart it (the conversation is saved), Session isn't responding
Strings lifted out of the shipped bundle, so the claim above can be checked against them.