Attach failures now distinguish a dead terminal host from a silent session, and offer the right recovery.
What's wrong with this entry?
Attach failures used to collapse into a generic "couldn't attach". Two causes are now separated. A session whose terminal host died is restarted on a fresh host, automatically on the command line and on the next Enter in the picker. A session that simply did not answer is offered a stop-and-attach cycle, with a note that the conversation is saved. Sessions you adopted from a shell command get different wording, because their command is not re-run for you.
- The two cases are recognised from the prefix on the error the background daemon returns, and are reported separately in telemetry.
- The daemon's liveness check now also spots a worker that has become a zombie and SIGKILLs its whole process group before declaring the session gone.
- Unconditional; no flag involved.
job_attach_host_dead
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.221
claude attachnow measures time-to-interactiveBoth mention attach
-
v2.1.248
claude attachexplains cleaned-up background sessions instead of failing genericallyBoth mention attach