← Commit history

v2.0.338: Send to AI waits 120 seconds (the editor can take 60s just to create a tab), proves delivery by delivered_to rather than by a nicely-named tab, and surfaces the API's own recovery hints on failure instead of retrying blind.

John Lauer ·0118040efa ·1mo ago ·parent 71d75d5
4 files changed +31−14
adom-bridge-puppeteer-manifest.json+5−5
@@ -1,10 +1,10 @@ {   "manifest_version": 1,   "name": "puppeteer",-  "version": "2.0.337",-  "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.337/adom-bridge-puppeteer-v2.0.337.zip",-  "sha256": "cad7f339ec2012924c7e7ee8cd3fd678db05368a1cefdf616bcc16f4accf8f46",-  "size": 1446645,+  "version": "2.0.338",+  "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.338/adom-bridge-puppeteer-v2.0.338.zip",+  "sha256": "0f5f3a2d9713b33cbcd2cf4ef0ab82d53ae50b9591f2c2b177737e393c8c2ff3",+  "size": 1447149,   "verbPrefixes": [     "browser_",     "desktop_recorder_",@@ -12,5 +12,5 @@   ],   "healthEndpoint": "/status",   "statusVerb": "browser_readiness",-  "released_at": "2026-08-24T15:02:25.363104Z"+  "released_at": "2026-08-24T15:04:01.169310Z" }
src/BRIDGE_VERSION+1−1
@@ -1 +1 @@-2.0.337\ No newline at end of file+2.0.338\ No newline at end of file
src/bridge.json+1−1
@@ -2,7 +2,7 @@   "manifest_version": 1,   "name": "puppeteer",   "displayName": "Puppeteer (Chrome for Testing + Native)",-  "version": "2.0.337",+  "version": "2.0.338",   "description": "Drives a browser ALREADY on the machine \u2014 installed Chrome, else Microsoft Edge (every Windows PC ships with Edge) \u2014 launched with a FRESH isolated profile, so the common case has NO ~150 MB Chrome-for-Testing download and it never touches the user's real tabs/logins. Binds its local server to LOOPBACK (127.0.0.1) only, so no Windows Firewall 'allow Node through the firewall' prompt ever pops. Chrome for Testing is fetched only as a LAST RESORT if the machine has no Chromium browser at all. SPAWN-VERIFIED fallback: pup tries each detected browser (Chrome \u2192 Edge \u2192 CfT) and actually launches it, falling through to the next if one won't start (and handling browsers like Edge that relaunch onto another PID), so a corrupt/partial install never hard-fails an open. The browser that launches is cached as the default (persisted across restarts) so it isn't re-probed each time. On spawn the bridge SELF-WARMS: detects browsers + disk, and only if the box has no Chrome/Edge and no cached CfT does it background-fetch CfT so the first open is instant. pup_use pins a specific browser (chrome | edge | cft | auto); {browser:'chrome',install:true} downloads & installs REAL Google Chrome (user-scoped, no admin) on an Edge-only box. pup_readiness (READ-ONLY) reports which browser will be used + the full candidate list + the default + free disk. Every failure returns a specific errorCode + _hint (chrome_install_no_disk, chrome_download_network, chrome_install_permission, chrome_stable_not_detected, \u2026). Launches with FULL browser permissions by default for full debug (strictPermissions:true opts out). Headful automation: open/close windows+tabs, navigate, screenshot, eval JS, record. pup is a GENERIC, non-profile browser only \u2014 every session is a fresh isolated Chrome/Edge process, never the user's real signed-in browser; profile defaults to sessionId. To drive the user's REAL Chrome/Edge (their profile, cookies, SSO), use the Adom browser EXTENSION's nbrowser_* verbs \u2014 a separate bridge, not pup's job. macOS (v1.9.74+): full parity with mac-native mechanics \u2014 background-by-default is the app-level hide (windows stay drivable/screenshottable while hidden), raise/lower map to unhide+activate/hide, pup_alert_window posts a native toast whose click focuses the window, pup_use {browser:'chrome',install:true} installs Chrome from the official dmg, and taskbar identity/badging remains Windows-only.",   "homepage": "https://wiki.adom.inc/adom/adom-bridge",   "author": "Adom Inc.",
src/server.js+24−7
@@ -13453,7 +13453,7 @@ const SAY = ${JSON.stringify(SAY_PHRASES)};       var b=ev.target.closest('.act-send'); b.disabled=true; b.classList.add('busy');       /* Opening a thread drives the editor and legitimately takes 10-30s on a busy workbench, so          SAY so at click time: a silently disabled button for half a minute reads as a hang. */-      toast('Opening a new AI thread. This can take up to half a minute.','info');+      toast('Opening a new AI thread. On a busy workbench this can take up to two minutes.','info');       var r=await fetch('/api/say-send',{method:'POST',headers:{'content-type':'application/json'},body:JSON.stringify({phrase:phrase})}).then(function(x){return x.json();}).catch(function(){return null;});       b.disabled=false; b.classList.remove('busy');       if(r&&r.ok) toast('Sent to a new AI thread.','ok');@@ -13497,7 +13497,7 @@ async function paintLeds(){   var d=document.getElementById('demo'); if(!d) return;   d.addEventListener('click',async function(){     d.disabled=true; d.classList.add('busy');-    toast('Handing the demo script to a new AI thread. This can take up to half a minute.','info');+    toast('Handing the demo script to a new AI thread. This can take up to two minutes.','info');     var r=await fetch('/api/say-send',{method:'POST',headers:{'content-type':'application/json'},body:JSON.stringify({phrase:'__demo__'})}).then(function(x){return x.json();}).catch(function(){return null;});     d.disabled=false; d.classList.remove('busy');     if(r&&r.ok) toast('The demo is running in a new AI thread.','ok');@@ -19197,9 +19197,13 @@ const server = http.createServer(async (req, res) => {         else if (!SAY_PHRASES.includes(phrase)) { sendJSON(res, { ok: false, why: 'unknown phrase' }); return; }         const guard = await shellSupportsSend();         if (!guard.ok) { sendJSON(res, { ok: false, why: guard.why }); return; }+        // 120 SECONDS, not 45 (ah build thread, 2026-08-24). The tab CREATE alone can take 60s on+        // a loaded workbench now that the composite adopts an idle empty tab and the server create+        // cap moved 30s -> 60s, so a 45s client timeout would manufacture a failure on exactly the+        // slow path this has to survive.         const r = await hydrogenPost('/ai-threads/run-prompt', {           new: true, prompt: outgoing, submit: true, name: tname, tags: ['dock:pup-bridge'],-        }, 45000);+        }, 120000);         if (!r.status) { sendJSON(res, { ok: false, why: 'Could not reach the AI panel (' + (r.error || 'no response') + '); the phrase was copied instead.' }); return; }         if (!(r.status >= 200 && r.status < 300)) { sendJSON(res, { ok: false, why: 'The AI panel refused the prompt (HTTP ' + r.status + '); the phrase was copied instead.' }); return; }         const j = r.json || {};@@ -19208,12 +19212,25 @@ const server = http.createServer(async (req, res) => {         // (new_thread.created 1) while inject reported "typing into the new thread timed out after         // 40s" and delivered_to came back null. Trusting the status code would have told the user         // their prompt was sent when nothing was ever typed into it.-        if (j.ok === false) {-          const why = (j.inject && j.inject.error) || j.error || 'no reason given';-          sendJSON(res, { ok: false, why: 'The thread opened but the prompt was not delivered (' + why + '); the phrase was copied instead.' });+        // PROOF IS delivered_to, NEVER THE NAME. Staged names can lag or miss entirely on an+        // ADOPTED tab, so a correctly-named tab appearing proves nothing about the prompt; the API+        // verifies delivery against the on-disk transcript and reports it here. Measured on+        // AdomLapper before the editor fixes landed: HTTP 200 with new_thread.created 1 and a+        // perfectly named tab, while inject said "typing into the new thread timed out after 40s"+        // and delivered_to was null. Trusting the status code would have told the user their+        // prompt was sent when nothing was ever typed into it.+        const delivered = j.delivered_to || j.delivered || null;+        if (j.ok === false || !delivered) {+          // Surface the API's OWN recovery text rather than inventing wording, and never retry a+          // create timeout blind: that duplicates the thread. The hints teach polling for the+          // staged name/tags and delivering by tid.+          const hint = (j._hints && (j._hints.note || j._hints.text)) || '';+          const why = (j.inject && j.inject.error) || j.error || (j.ok === false ? 'no reason given' : 'the editor did not confirm delivery');+          sendJSON(res, { ok: false, tid: j.tid || null,+            why: 'The thread opened but delivery was not confirmed (' + why + '); the phrase was copied instead.' + (hint ? ' ' + hint : '') });           return;         }-        sendJSON(res, { ok: true, tid: j.tid || null, deliveredTo: j.delivered_to || null });+        sendJSON(res, { ok: true, tid: j.tid || null, deliveredTo: delivered });       });       return;     }