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
Thread Tiles: set the owning ai-thread at window create so the taskbar button is BORN under the thread AUMID with the name tile, instead of relying on a fragile post-open re-stamp; bump tile generation to t4 for virgin button art.
4 files changed
+18−7
adom-bridge-puppeteer-manifest.json+4−4@@ -1,10 +1,10 @@ { "manifest_version": 1, "name": "puppeteer",- "version": "2.0.164",- "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.164/adom-bridge-puppeteer-v2.0.164.zip",- "sha256": "d956ae3c46574caa8b4c2f3daeacea768770e649ed74bca863dbbf4954d1b884",- "size": 909722,+ "version": "2.0.165",+ "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.165/adom-bridge-puppeteer-v2.0.165.zip",+ "sha256": "e1de419db673c45163bc7e45dfc7bf1afda904d76cd03e533f2f1a5c6cc093c6",+ "size": 910099, "verbPrefixes": [ "browser_", "desktop_recorder_",
src/BRIDGE_VERSION+1−1@@ -1 +1 @@-2.0.164+2.0.165
src/bridge.json+1−1@@ -2,7 +2,7 @@ "manifest_version": 1, "name": "puppeteer", "displayName": "Puppeteer (Chrome for Testing + Native)",- "version": "2.0.164",+ "version": "2.0.165", "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+12−1@@ -4264,7 +4264,7 @@ function writeAumidIcon(appId, iconPath) { // NAME rendered on the teal tile. The name is rendered in the real Adom font (Familjen Grotesk) by // CHROME — the ONE renderer guaranteed to have the woff2 — into a 256px PNG, which sharp downscales // to a multi-size .ico. Rendered once per thread name and cached on disk.-const THREAD_TILE_GEN = 't3';+const THREAD_TILE_GEN = 't4'; // t4: virgin AUMIDs for the owner-at-birth fix (2.0.165) — Windows caches button art per AUMID, and the janitor reaps prior gens const THREAD_TILE_DIR = path.join(os.tmpdir(), 'pup-thread-tiles', THREAD_TILE_GEN); let _fgFontB64 = null; function fgFontB64() {@@ -12588,6 +12588,17 @@ const server = http.createServer(async (req, res) => { const fgGranted = fgRequested && !!fgReason; const fgDenied = fgRequested && !fgReason; if (fgGranted) console.log(`[foreground] "${sessionId}" open GRANTED — reason: ${fgReason}`);+ // v2.0.165 THREAD TILES ROOT CAUSE: default the owner to the CALLING ai-thread when not+ // explicitly declared, BEFORE launchSession — session.owner must exist at CREATE time so the+ // FIRST identity stamp (the one that births the taskbar button) already computes the thread+ // AUMID + name tile. Previously owner came only from args.owner, so the button was BORN under+ // a per-session category appId, and the later thread re-stamp silently failed forever whenever+ // the hwnd could not be re-resolved (title fallback is dead with titleTag off) — the taskbar+ // kept the category icon and never grouped. User-surface callers (taskbar/toolbar) stay+ // ownerless: a human click is not an AI thread.+ if (!(typeof args.owner === 'string' && args.owner.trim()) && _callerThread && !USER_CALLERS.has(_callerThread)) {+ args.owner = _callerThread; args._ownerFromCallerIdentity = true;+ } let session; try { // v1.9.143: same-profile opens are serialized (see _profileOpenChain).