app
Pup - the AI's own browser
Public Made by Adomby adom
pup gives your AI a real browser on your desktop that it drives completely, in the background, signed in as you: windows that never jump in front of your work, one shared profile that learns your logins, and every window labeled on the taskbar with its AI thread's name.
← Commit history
Strip scope made explicit: TASKBAR (pup), with a tooltip stating it mimics ONLY pup-managed Chrome buttons. Root of John's 'not accurate to what is showing in the taskbar': two teal-tile buttons on his real taskbar that the mimic does not show were identified definitively (via window enumeration with owning process) as Hydrogen Desktop and Adom Desktop app windows - other Adom apps wearing the same teal brand tile, never pup windows. The mimic was right not to model them, but claiming 'TASKBAR' without scope read as a whole-taskbar claim, which is how the green MATCH light looked like a lie next to visibly unmodeled tiles. The 1.9.248 untracked-window detection remains for the case that IS pup's to own (zombie windows of pup Chrome processes - it caught one, hwnd 14552128, before that process exited).
4 files changed
+7−7
adom-bridge-puppeteer-manifest.json+4−4@@ -1,10 +1,10 @@ { "manifest_version": 1, "name": "puppeteer",- "version": "1.9.248",- "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.248/adom-bridge-puppeteer-v1.9.248.zip",- "sha256": "80e1f25941d471d226de6cbf5dd2e4737ac77086fa1f0801955ef670db37645b",- "size": 468061,+ "version": "1.9.249",+ "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.249/adom-bridge-puppeteer-v1.9.249.zip",+ "sha256": "aa745c81ed7c86fcd56639fdda1415e6a2244dc3ceabddbdc6c33b9201dd764c",+ "size": 468134, "verbPrefixes": [ "browser_", "desktop_recorder_",
src/BRIDGE_VERSION+1−1@@ -1 +1 @@-1.9.248+1.9.249
src/bridge.json+1−1@@ -2,7 +2,7 @@ "manifest_version": 1, "name": "puppeteer", "displayName": "Puppeteer (Chrome for Testing + Native)",- "version": "1.9.248",+ "version": "1.9.249", "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. 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, browser_alert_window posts a native toast whose click focuses the window, browser_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-desktop", "author": "Adom Inc.",
src/server.js+1−1@@ -8300,7 +8300,7 @@ function render(){ // from his actual taskbar), and NO overlay at all when pup has not painted one (a bare Chrome // button must render bare here too, otherwise the mimic lies). const ghosts=(d.untrackedWindows||[]).map(h=>'<div class="tbi ghost" title="a window of the pup-managed Chrome is on the real taskbar but pup has NO session for it (hwnd '+h+'). The mimic cannot know its icon - this is why the header LED is red.">?<span class="led red"></span></div>').join('');- _q('#taskbar').innerHTML='<span class="lbl">TASKBAR</span>'+groups.map((g,i)=>{+ _q('#taskbar').innerHTML='<span class="lbl" title="mimics ONLY the taskbar buttons of pup-managed Chrome windows. Other Adom apps (Hydrogen Desktop, Adom Desktop) have their own teal-tile buttons that are out of pup scope.">TASKBAR (pup)</span>'+groups.map((g,i)=>{ const fg=g.wins.some(w=>w.foreground); return '<div class="tbi'+(fg?' fg':'')+'" data-jump="g'+i+'" title="'+esc(g.label)+': '+esc(g.ledWhy||'')+'">' +'<img class="base" src="'+esc(g.baseIcon||'')+'" data-fallback="hide">'