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
Pup window frame color changed from bright teal (20,184,184) to the Adom near-black ground #0d1117 (13,17,23) per John: the teal was 'a bit ugly', wanted something closer to black but on-brand that still color-codes pup/adom-you windows as distinct from the user's real Chrome profiles. Applied via --install-autogenerated-theme on the adom-you (DEFAULT_PROFILE) launch.
4 files changed
+11−7
adom-bridge-puppeteer-manifest.json+4−4@@ -1,10 +1,10 @@ { "manifest_version": 1, "name": "puppeteer",- "version": "1.9.344",- "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.344/adom-bridge-puppeteer-v1.9.344.zip",- "sha256": "7d7555830e7eb45dd93c288d0cd938ab48782b628eea1686930c25a6a8746dfb",- "size": 635563,+ "version": "1.9.345",+ "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.345/adom-bridge-puppeteer-v1.9.345.zip",+ "sha256": "e72e3bb800cdc065bf49e7338cf1b8f552e138a2a4d7ee9c0eb46c40513f7f80",+ "size": 635726, "verbPrefixes": [ "browser_", "desktop_recorder_",
src/BRIDGE_VERSION+1−1@@ -1 +1 @@-1.9.344+1.9.345
src/bridge.json+1−1@@ -2,7 +2,7 @@ "manifest_version": 1, "name": "puppeteer", "displayName": "Puppeteer (Chrome for Testing + Native)",- "version": "1.9.344",+ "version": "1.9.345", "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+5−1@@ -7261,7 +7261,11 @@ async function getOrLaunchBrowser(profileName, { freshProfile = false, strictPer // unmistakably an Adom window at a glance. Only the durable shared jar gets // it (John's pick); isolated throwaways stay plain Chrome. The flag installs // the theme INTO the profile, so it persists across later launches too.- ...(profileName === DEFAULT_PROFILE ? ['--install-autogenerated-theme=20,184,184'] : []),+ // v1.9.345 (John): frame color is the Adom near-black ground #0d1117 (RGB 13,17,23), NOT the old+ // bright teal (20,184,184) — "the teal is a bit ugly; something closer to black but within the Adom+ // brand". This dark-slate frame color-codes pup windows as the adom-you doppelganger's own windows,+ // distinct from the user's real Chrome profiles, without a garish tint.+ ...(profileName === DEFAULT_PROFILE ? ['--install-autogenerated-theme=13,17,23'] : []), // #435 — CRASH-RESTORE SUPPRESSION. pup profiles are AI-driven and never want Chrome's "Restore // pages? Chrome didn't shut down correctly" flow. After a shared-Chrome crash it reopens the DEAD // session's tabs (URL dupes + about:blank) into whatever window relaunches, and pup then adopts