thinkpool-pair 0.7.122 → 0.7.124

package/bridge.mjs

@@ -1663,6 +1663,15 @@ function openStructured({ id, model, resume, log, commands, mode, spawnedBy, rol
       // on the entry so the ANNOUNCE can hand it to clients that connect/reload
       // AFTER init (the one-time code-event would miss them), then re-announce.
       if (evt.kind === 'system' && Array.isArray(evt.commands) && evt.commands.length && !entry.commands) { entry.commands = evt.commands; announce(); persist() }
+      // Auto-resume trigger (Max, 2026-07-02): the init `system` event means the SDK session
+      // is LIVE (input stream now consumed). A restored mid-turn plain terminal flagged for
+      // resume gets its single "continue" HERE — not on a blind timer that raced the ~40s
+      // resume and dropped the turn into a dead input stream. Fires exactly once.
+      if (evt.kind === 'system' && entry.pendingAutoResume) {
+        entry.pendingAutoResume = false
+        try { entry.session?.sendTurn('continue') } catch { /* not resumable — stays idle, user can continue manually */ }
+        process.stderr.write(`\n  ◆ auto-resumed interrupted turn (${id.slice(0, 8)}) — sent continue.\n`)
+      }
       // Chrome events (mode / usage / clear / compact) are transient state, not
       // transcript — broadcast + print them but keep out of the persisted/replayed log.
       // 'stalled' is transient turn-liveness state (would replay as a stale frozen
@@ -2174,6 +2183,19 @@ channel
             if (re && rec.flowTaskKey && !restoredTurnOpen(rec.log || [])) {
               setTimeout(() => { try { re.markFlowDone?.() } catch { /* noop */ } }, 2000)
             }
+            // Auto-resume (Max, 2026-07-02): a PLAIN terminal (NOT a flow lane — those have their
+            // own re-dispatch) that was MID-TURN when the bridge stopped picks the work back up
+            // instead of sitting aborted. If its SDK context resumes (canResume), send ONE
+            // "continue" — like the user typing "continue" after a restart. We DON'T fire on a
+            // fixed timer: a resume takes ~40s to become live (MCP boot + sanitizeSession), and a
+            // 2.5s sendTurn pushed into an input stream nothing is consuming yet is silently lost
+            // (the 2026-07-02 "didn't autocontinue" bug). Instead FLAG it here and fire the single
+            // continue when the session's init `system` event actually arrives (onEvent), i.e. the
+            // instant it's live. openStructured already closed the interrupted turn idle, so a
+            // continue that can't be delivered just leaves it idle (recoverable) — never a hang.
+            if (re && !rec.flowSessionId && canResume(rec) && restoredTurnOpen(rec.log || [])) {
+              re.pendingAutoResume = true
+            }
           }
           // Fresh open: ONLY for an explicit `-- <claude>` share. In account mode
           // (autoAgent set, no attachedCmd) the web's `?new=1` flow opens the first

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "thinkpool-pair",
-  "version": "0.7.122",
+  "version": "0.7.124",
   "description": "Share a local coding-agent CLI (Claude Code, Codex, Gemini, Aider, …) into a ThinkPool Code room, live.",
   "type": "module",
   "bin": {