Pup - the AI's own browser

@@ -1,5 +1,12 @@ # Changelog — Adom Desktop Puppeteer Bridge +## 1.8.94 — 2026-07-19 — Wiki dual-view: single-window, hint-only (no two-window nag)++Reverted the "show BOTH views" push — double-reloading the same page in two windows is annoying+for the reload-100x loop. Now ONE window is normal; hints just make the AI AWARE it can switch+this window to wikiView:"authed" (or log the user in once) when a task needs the logged-in angle.+The deliberate public-vs-private visibility check flips the SAME window between views.+ ## 1.8.93 — 2026-07-19 — Wiki dual-view: public (default) + logged-in (wikiView:"authed")  pup can now open a wiki.adom.inc page from EITHER viewpoint, and hints teach the AI to show BOTH

@@ -1,10 +1,10 @@ {   "manifest_version": 1,   "name": "puppeteer",-  "version": "1.8.93",-  "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.8.93/adom-bridge-puppeteer-v1.8.93.zip",-  "sha256": "10d8c99cc1aceb4e2535051dced7c7ac6f9d3651785e6d5deaa86f3fc43bc792",-  "size": 206809,+  "version": "1.8.94",+  "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.8.94/adom-bridge-puppeteer-v1.8.94.zip",+  "sha256": "cb8992ceca44b62710ac745896b7aabacc4e49404e743fd1cbe09dd39af1b797",+  "size": 206843,   "verbPrefixes": [     "browser_",     "desktop_recorder_",

@@ -55,8 +55,10 @@ pup can now open a wiki page from **either viewpoint**, and the killer use is sh - **Logged-in:** `browser_open_window {sessionId, url:"...", wikiView:"authed"}` — routes to pup's   reserved persistent authed-wiki profile whose cookie jar holds a 30-day SSO session. -**THE verification pattern (do this after any publish where visibility matters):** open the page-BOTH ways and show the user side by side. Example John cares about: *"I published an app where the+**Use ONE window normally.** Don't open two windows for the same page — that double-reloads and+annoys. Just pick the view the task needs. The ONLY time to compare both is a deliberate+visibility check after a publish, and even then flip the SAME window between views rather than+opening two. Example John cares about: *"I published an app where the public should get only the binaries but I keep the source private — did the AI accidentally leak the source?"* The public view answers that directly (if you can see `src/` there, it leaked). The response `_hint` tells you which view you opened and nudges you to open the other.

@@ -1 +1 @@-1.8.93\ No newline at end of file+1.8.94\ No newline at end of file

@@ -2,7 +2,7 @@   "manifest_version": 1,   "name": "puppeteer",   "displayName": "Puppeteer (Chrome for Testing + Native)",-  "version": "1.8.93",+  "version": "1.8.94",   "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. browser_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. browser_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.",   "homepage": "https://wiki.adom.inc/adom/adom-desktop",   "author": "Adom Inc.",

@@ -1839,12 +1839,14 @@ async function checkWikiAuth(page) { } function wikiViewHint(url, view, auth) {   if (!isWikiUrl(url)) return '';+  // ONE window is the norm — do NOT push opening two. These hints just make the AI AWARE it can+  // switch THIS window's viewpoint (or log in) when the task calls for it.   if (view === 'authed') {-    if (auth && auth.authed) return ` 🔓 WIKI (LOGGED-IN view as ${auth.user || 'the user'}). To ALSO show the PUBLIC view — and CATCH visibility leaks (e.g. did source get published that should be private?) — open the SAME url WITHOUT wikiView (default = anonymous/public) and show the user BOTH side by side.`;-    return ` 🔑 WIKI LOGIN NEEDED: this window uses pup's persistent authed wiki profile but it is NOT signed in yet (first use, or the ~30-day session expired). To sign in ONCE: raise this window (browser_raise_os_window with a foregroundReason like "sign into the Adom wiki") so the user completes the hydrogen.adom.inc SSO; the session then persists in this profile and every later wikiView:"authed" open is logged in automatically. Tell the user this is a one-time login.`;+    if (auth && auth.authed) return ` 🔓 Wiki LOGGED-IN view (as ${auth.user || 'the user'}) — you see private source, drafts, owner-only cards. Reopen the SAME sessionId without wikiView for the public view when you want to check what the world sees (e.g. after a publish: did private source leak?).`;+    return ` 🔑 Wiki authed view requested but NOT signed in yet (first use, or the ~30-day session expired). Offer the user a ONE-TIME login: browser_raise_os_window with foregroundReason "sign into the Adom wiki" → user completes the hydrogen.adom.inc SSO → the session persists in this profile for ~30 days, so future wikiView:"authed" opens are silently logged in. Until then this window shows the public view.`;   }-  // anonymous/public open-  return ` 📖 WIKI (PUBLIC/anonymous view — pup's default fresh profile, logged out). This is the view the WORLD sees. To ALSO see the user's LOGGED-IN view (private source, unpublished drafts, owner-only cards), open the same url with wikiView:"authed". Showing BOTH is the way to verify what is/ isn't public before/after a publish.`;+  // public/default open — a light, one-line awareness note (no "open two windows" nag).+  return ` (Wiki public view — the default. If you need the user's LOGGED-IN angle (private source, drafts, owner cards) reopen this sessionId with wikiView:"authed"; pup can log them in once. Otherwise ignore this.)`; }  async function fetchPageFavicon(page) {