You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Open chat stays on "Disconnected from the host" after Ace Helper recovers #362
Two-person study scenario 18b (#218), 0.0.34, Mac B. B's Ace Helper was frozen (SIGSTOP) for 3 minutes while B was off the tailnet, then resumed at 00:29:59:
During the freeze the open chat showed "Loading chat…" with no explanation.
At 00:30:24 it changed to "Disconnected from the host" with Try again.
It stayed there until the tester clicked Try again at 00:31:16; then history loaded at once.
Expected: the chat reconnects by itself once the Helper answers again, as it does after the app reconnects, and says sooner that the Helper isn't responding. Confusion 2/3.
Fixed in #371. The chat now says "Ace Helper isn't responding" about 10 s after the Helper stops answering, instead of a bare "Loading chat…". In scenario 18b the error came from B's Helper: it was passing the watch on to A, that connection had dropped, and the app had nothing that would retry it. The chat now re-watches by itself in that case, and Try again is still there. Smoke-tested on a separate CLI host with a 90 s SIGSTOP in headless Chromium: history came back within 1 s of SIGCONT with no click.
Activity
iamnbutler commentedon Oct 15, 2026
Picked up by the overnight issue watcher (handed over by the study lead); a PR will link here.
fix(app): say when Ace Helper isn't responding and re-watch a chat a …
iamnbutler commentedon Oct 15, 2026
Fixed in #371. The chat now says "Ace Helper isn't responding" about 10 s after the Helper stops answering, instead of a bare "Loading chat…". In scenario 18b the error came from B's Helper: it was passing the watch on to A, that connection had dropped, and the app had nothing that would retry it. The chat now re-watches by itself in that case, and Try again is still there. Smoke-tested on a separate CLI host with a 90 s SIGSTOP in headless Chromium: history came back within 1 s of SIGCONT with no click.
iamnbutler commentedon Oct 15, 2026
Thanks for #371. I'll recheck the two-machine relay case (B watching A's channel while A's Helper is frozen) on 0.0.36.
iamnbutler commentedon Oct 15, 2026
Rechecked across two Macs in study 18c on 0.0.37:
This passes, so I'm closing. The teammate-side feedback gap is #385.