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
v2.0.559 candidate (rust): The thread tile is rendered in the binary (John, 2026-09-14: 'it should just be in pup's rust binary. why would we use javascript?'). Until now the taskbar name tile was JavaScript evaluated inside whatever page the window was on, a leftover from the Node bridge that could not draw text; a strict Content-Security-Policy (claude.ai, the wiki) refused it and the button silently fell back to a nameless per-window icon. pup_identity::tile now lays out and rasterises the tile with fontdue from the same Familjen Grotesk Bold face (fg-700 converted to TTF), same layout rules, same plate, every ICO entry at its own pixel size; output verified pixel-for-pixel against the browser-rendered tiles on the laptop. The page-evaluation path, tile_js and the embedded woff2 are deleted. Also: the extension lane stamps the LIVE window before pup_open_window returns (birth used to bind Chrome's transient launch window), and recovery stamps a re-adopted window immediately; the 15 s health-tick rebind is now only a backstop. identity.rs was reconstructed after a bad restore this afternoon; all identity and verbs tests pass.
3 files changed
+7−7
adom-bridge-puppeteer-manifest-candidate.json+5−5@@ -1,17 +1,17 @@ { "manifest_version": 1, "name": "puppeteer",- "version": "2.0.558",- "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.558/adom-bridge-puppeteer-v2.0.558.zip",- "sha256": "4dd2e398538667d612ab2485c921d479fd5a70e0cc642b717a7bdedce761cbcc",- "size": 3155285,+ "version": "2.0.559",+ "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.559/adom-bridge-puppeteer-v2.0.559.zip",+ "sha256": "7e32c3c1f486f53996faf35ecacdb0dd5158bd26fc1710d3cf376d26c44400db",+ "size": 3203296, "verbPrefixes": [ "pup_", "browser_" ], "healthEndpoint": "/status", "statusVerb": "pup_readiness",- "released_at": "2026-09-14T12:05:36.543204Z",+ "released_at": "2026-09-14T12:27:57.929294Z", "shell": "rust", "tier": "insiders" }
src/BRIDGE_VERSION+1−1@@ -1 +1 @@-2.0.558+2.0.559
src/bridge.json+1−1@@ -2,7 +2,7 @@ "manifest_version": 1, "name": "puppeteer", "displayName": "Puppeteer (Chrome for Testing + Native)",- "version": "2.0.558",+ "version": "2.0.559", "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.",