@alphacoder-v0/pi-loops 0.19.2 → 0.19.3

package/CHANGELOG.md

@@ -3,6 +3,19 @@
 All notable changes to pi-loops are documented here. The format follows
 [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); versions follow SemVer.
 
+## [0.19.3] - 2026-09-14
+
+### Fixed
+- **Six tabs of the browser front end and nothing you typed was sent** (#14). A browser gives one
+  address six connections, and every open tab held one for its event stream — so the sixth tab, or
+  a few left behind the first, left nothing for `POST /prompt`: the fetch queued, neither
+  succeeding nor failing, the bubble drawn and the message never delivered. A tab now closes its
+  stream fifteen seconds after going into the background (`paused in background`) and opens a new
+  one when looked at again, polling at once so the seq/epoch check reloads what it missed; the pi
+  process behind the page, and its jobs, are not involved either way. And a send that has not
+  settled in six seconds says `still sending — if it never lands, close the other tabs of this
+  address` instead of looking alive.
+
 ## [0.19.2] - 2026-09-14
 
 ### Fixed

package/README.md

@@ -38,7 +38,7 @@ the first sign of credentials that do not work should not be an empty inbox tomo
 
 ```bash
 pi install npm:@alphacoder-v0/pi-loops                      # from npm, following new releases
-pi install git:github.com/alphacoder-v0/pi-loops@v0.19.2    # or from GitHub, at a pinned tag
+pi install git:github.com/alphacoder-v0/pi-loops@v0.19.3    # or from GitHub, at a pinned tag
 pi install /path/to/pi-loops                                # or a local checkout — `pi install .` in this repo
 pi -e /path/to/pi-loops                                     # or none of them: try it for one run, installing nothing
 ```

package/README.zh-CN.md

@@ -45,7 +45,7 @@ pi-loops 自己没有任何运行时依赖。
 
 ```bash
 pi install npm:@alphacoder-v0/pi-loops                      # 从 npm 装，跟着新版本走
-pi install git:github.com/alphacoder-v0/pi-loops@v0.19.2    # 或者从 GitHub 装，钉住一个 tag
+pi install git:github.com/alphacoder-v0/pi-loops@v0.19.3    # 或者从 GitHub 装，钉住一个 tag
 pi install /path/to/pi-loops                                # 或者本地检出；本仓库里就是 pi install .
 ```
 

package/docs/web-ui-parity.md

@@ -171,6 +171,18 @@ weaker, and worth converting whenever one of them breaks.
       be read as prose and waved through. `test/web-page.test.ts`: *a confirmation shows what is
       about to run*.
 - [x] Enter does not approve: the focus starts on cancel.
+- [x] **A tab in the background does not hold one of the browser's six connections.** Every tab
+      used to keep an event stream open for as long as it existed, so the sixth tab — or a few
+      forgotten behind the first — left nothing for the request that sends what you typed, and the
+      message sat drawn and unsent (#14). A tab closes its stream fifteen seconds after going into the
+      background and says `paused in background`; looked at again, it subscribes anew and polls, and
+      the seq/epoch check reloads what it missed. The pi behind the page runs, and its jobs run, either
+      way. `test/web-page.test.ts`: *a tab in the background gives its connection back, and takes a
+      new one when looked at again*.
+- [x] **A send that goes nowhere says so.** Six seconds without an answer to `/prompt` and the
+      status line reads `still sending — if it never lands, close the other tabs of this address`;
+      the request is not abandoned, and the line goes when it settles. `test/web-page.test.ts`: *a
+      send that goes nowhere says so instead of looking alive*.
 - [x] A slash command that waits in a dialog is not reported as timed out while the person reads:
       the browser waits up to fifteen minutes for a `/…` prompt, sixty seconds for anything else.
 - [x] Clicking away from any dialog closes it. `test/web-page.test.ts`: *clicking outside a dialog

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@alphacoder-v0/pi-loops",
-  "version": "0.19.2",
+  "version": "0.19.3",
   "description": "An automation layer for pi: cron + stateful loops with a triage inbox, maker/checker verification, dynamic triggers, MCP notifications and tools, lifecycle hooks, session archives. A non-invasive pi extension.",
   "type": "module",
   "license": "MIT",

package/src/web.mjs

@@ -2442,6 +2442,10 @@ const api = (p, b) =>
 		.catch((e) => ({ success: false, error: String(e) }));
 const $ = (id) => document.getElementById(id);
 const feed = $("feed"), statusEl = $("status");
+/** How long a tab stays subscribed after it goes into the background. */
+const STREAM_PARK_MS = 15000;
+/** How long a send may take before the page says that it is taking long. */
+const SEND_WATCHDOG_MS = 6000;
 let state = {}, cwd = "", busy = false, atBottom = true, takesImages = true;
 /** Installed once the stream is up; until then a poll has nothing to compare against. */
 let checkStream;
@@ -3808,7 +3812,17 @@ $("composer").onsubmit = async (e) => {
     if (drewLocally.length > 20) drewLocally.shift();
   }
   images = []; drawThumbs();
-  const r = await api("/prompt", payload);
+  // A send that neither succeeds nor fails is a send the browser has queued behind its connection
+  // pool — every other tab of this address holding a stream is the usual reason (#14). The fetch is
+  // not given up on; the page says what is happening instead of looking alive.
+  const slow = setTimeout(() => { statusEl.textContent = "still sending — if it never lands, close the other tabs of this address"; }, SEND_WATCHDOG_MS);
+  let r;
+  try {
+    r = await api("/prompt", payload);
+  } finally {
+    clearTimeout(slow);
+    if (statusEl.textContent.startsWith("still sending")) statusEl.textContent = busy ? "working…" : "ready";
+  }
   if (!r.success) row("err", "error", r.error || JSON.stringify(r));
 };
 $("stop").onclick = () => api("/abort", {});
@@ -4498,15 +4512,46 @@ function applyEvent(ev) {
     }
   };
 
-  const es = new EventSource("/events?token=" + TOKEN);
-  es.onmessage = (e) => {
-    const ev = JSON.parse(e.data);
-    if (resyncing) return void waiting.push(ev); // applied once the transcript is back
-    applyEvent(ev);
+  /*
+   * One stream per tab, and only while the tab is looked at.
+   *
+   * A browser gives one address six connections, and every open tab used to hold one of them for
+   * its event stream — so the sixth tab, or a few forgotten behind the first, left nothing for the
+   * request that sends what you typed: the fetch queued, neither succeeding nor failing, the bubble
+   * drawn and the message never sent (#14). A tab in the background does not need to hear events as
+   * they happen: it closes its stream after a moment, and when it is looked at again it opens a new
+   * one and polls, and the seq/epoch check above reloads whatever it missed. The pi process behind
+   * this page is not involved either way; it runs, and its jobs run, whether anyone is listening.
+   */
+  let es;
+  const openStream = () => {
+    if (es) return;
+    es = new EventSource("/events?token=" + TOKEN);
+    es.onmessage = (e) => {
+      const ev = JSON.parse(e.data);
+      if (resyncing) return void waiting.push(ev); // applied once the transcript is back
+      applyEvent(ev);
+    };
+    es.onerror = () => { statusEl.textContent = "reconnecting…"; };
+    es.onopen = () => refresh();
   };
-
-  es.onerror = () => { statusEl.textContent = "reconnecting…"; };
-  es.onopen = () => refresh();
+  openStream();
+  let parking;
+  document.addEventListener("visibilitychange", () => {
+    clearTimeout(parking);
+    if (document.visibilityState === "hidden") {
+      // Not at once: switching tabs and back should not cost a reconnect and a reload.
+      parking = setTimeout(() => {
+        if (!es || document.visibilityState !== "hidden") return;
+        es.close();
+        es = undefined;
+        statusEl.textContent = "paused in background";
+      }, STREAM_PARK_MS);
+    } else if (!es) {
+      openStream();
+      refresh().catch(() => {});
+    }
+  });
   setInterval(refresh, 8000);
 })();
 </script>`;