What
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.
Details
- 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.
Evidence
job_attach_host_dead
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundleclaude attach
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up claude attach, on Manage multiple agents with agent view.
| `claude attach <id>` | Attach to a session in this terminal |agent-view see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up claude attach, on Manage multiple agents with agent view.