{"version":"2.1.247","anchor":"claude-attach-tells-you-whether-the-terminal-host-died-or-ju","canonical_anchor":"claude-attach-tells-you-whether-the-terminal-host-died-or-ju","heading":"claude attach tells you whether the terminal host died or just never answered","tier":"use","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/claude-attach-tells-you-whether-the-terminal-host-died-or-ju","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### `claude attach` tells you whether the terminal host died or just never answered\n\nAttach failures now distinguish a dead terminal host from a silent session, and offer the right recovery.\n\n**What**\n\nAttach 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.\n\n**Details**\n\n- The two cases are recognised from the prefix on the error the background daemon returns, and are reported separately in telemetry.\n- 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.\n- Unconditional; no flag involved.\n\n**Evidence**\n\n`job_attach_host_dead`\n\n- Area: Sessions\n- Names: `claude attach`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5"}