The turn is parked, not killed
When the link goes, the running child is parked on the machine and its output is buffered instead of discarded. The turn is suspended, and that is recorded as a suspension rather than as a failure.
Any engine fix: A turn ends because the machine disconnected
The engine runs on your machine rather than in the browser, so a dropped link is a lost view before it is a lost turn. Whether the turn survives comes down to how long the gap lasts.
Machine disconnected
Printed by Termdeck.
Diagnosis
When the link goes, the running child is parked on the machine and its output is buffered instead of discarded. The turn is suspended, and that is recorded as a suspension rather than as a failure.
A shorter gap rebinds: the suspended run finds its parked child and the stream resumes where it stopped. A longer one finishes the turn as disconnected, because past that point nothing can promise the child is still the one you meant.
A service restart parks turns on purpose and re-attaches them afterwards, which is why an update reads as a pause of a few seconds rather than as a lost afternoon.
Check
| Run this | What a good answer looks like |
|---|---|
tail -n 20 ~/.termdeck/logs/agent.log | Whether the machine lost the link or went away entirely. A reconnect within seconds explains a turn that came back on its own. |
ps -eo pid,etime,cmd | grep "[c]laude" | A child still running whose age matches your turn is a parked turn rather than a lost one. |
Every command here has been run on a real machine. Termdeck answers the same questions for every machine you have connected, without opening a terminal on any of them.
Fix
A turn that rebinds continues from where it was. Sending again during the gap starts a second turn that then has to be reconciled with the first.
The engine writes to disk as it goes, so whatever finished is on the machine whether or not a browser watched it arrive.
Past the window the turn is closed for good, and sending again is the right move rather than a duplicate.
Not this
The transcript is written on the machine while the turn runs. A disconnected view is not a discarded turn.
FAQ
No. The turn runs on the machine and continues with nobody watching.
Around four minutes. Under that it rebinds; over it, the turn closes as disconnected.
They are parked and re-attached deliberately, so the visible effect is a pause of a few seconds.
Claude Code, Codex and Grok in one browser console