Development record
The lost-connection fix of iss-2610080620372731 is proven by unit tests with an injected clock and prober, not yet by a live run: the record asks for a lab that cuts the network during a real autonomous run and shows each kind of loss (the host's own turn, a sub-agent, a tool's network call, and the model service) waited out on the one shared probe, the other lanes held only at network steps, a dead or yielded lane restarted from its last commit with its edits kept for review, and the 8-hour give-up ending in one notification. The product thinker ruled on 2026-10-09 that this lab runs after the next patch release is cut, since it switches off the machine's network for a few minutes.
The lost-connection fix of iss-2610080620372731 is proven by unit tests with an injected clock and prober, not yet by a live run: the record asks for a lab that cuts the network during a real autonomous run and shows each kind of loss (the host's own turn, a sub-agent, a tool's network call, and the model service) waited out on the one shared probe, the other lanes held only at network steps, a dead or yielded lane restarted from its last commit with its edits kept for review, and the 8-hour give-up ending in one notification. The product thinker ruled on 2026-10-09 that this lab runs after the next patch release is cut, since it switches off the machine's network for a few minutes.
Frontmatter
| id | iss-2610091937218987 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610091937218987-run-the-live-network-cut-lab-for-the.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2610080620372731When an agent or sub-agent loses its network connection mid-task, the work stalls or fails instead of waiting the outage out, and this keeps happening on the product thinker's machine. An agent that notices a lost connection should pause and retry on a widening schedule: wait one minute and try again, then five minutes, then ten, then an hour. Sibling agents should also learn of the outage without depending on each other over the network, since they may have lost the connection too: a channel on the machine itself, such as the run state and run log abcd already shares between sessions, would let one agent record the outage and the others hold off instead of each failing on its own.