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
ONE shared profile for ALL pup windows (John: 'i want all pup windows to use the same profile now so you have all of the users saved logins over time so the database of their logins builds up and this is pleasurable to use over time'). Every window — wiki AUTHED included — now uses the durable adom-you jar, so every login the user does anywhere (Google, Autodesk, Mouser, the wiki, anything) accumulates into one growing credential store that makes pup nicer the more it's used. The only windows that still get a separate jar are the three that definitionally require it: {webSecurity:false} (insecure per-process flags must never share the credentialed process), {isolated:true} (explicit fresh/throwaway jar for login tests or acting as another user), and the wiki PUBLIC view (logged-out by definition, needs a clean jar to show the world's view). The old separate adom-wiki-authed jar is retired for resolution; the view toggle now sends authed->the shared jar and public->an isolated logged-out jar. Accepted tradeoff, per John: one shared Chrome process means a crash takes all sessions down together (the crash-isolation the pup-vendor-login skill warned about is explicitly waived in favour of login accumulation).
4 files changed
+19−21
adom-bridge-puppeteer-manifest.json+4−4@@ -1,10 +1,10 @@ { "manifest_version": 1, "name": "puppeteer",- "version": "1.9.159",- "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.159/adom-bridge-puppeteer-v1.9.159.zip",- "sha256": "9a1d273f8ef558aecfb8aeacad49eec1c88cb1abdf6076df1d796cd2a81f954e",- "size": 402233,+ "version": "1.9.162",+ "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.162/adom-bridge-puppeteer-v1.9.162.zip",+ "sha256": "934cb0c38e427002b7f3c94b9ec7a2ed9f45b01e4a10bd37d9d31588bcd34de9",+ "size": 402341, "verbPrefixes": [ "browser_", "desktop_recorder_",
src/BRIDGE_VERSION+1−1@@ -1 +1 @@-1.9.159+1.9.162
src/bridge.json+1−1@@ -2,7 +2,7 @@ "manifest_version": 1, "name": "puppeteer", "displayName": "Puppeteer (Chrome for Testing + Native)",- "version": "1.9.159",+ "version": "1.9.162", "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+13−15@@ -6817,22 +6817,20 @@ const server = http.createServer(async (req, res) => { } catch (e) { /* fall through to a fresh window if the tab add failed */ } } }- if (args.wikiView === 'authed' && isAdomUrl(args.url)) args.profile = WIKI_AUTH_PROFILE;- // v1.9.123: default now resolves to the durable shared "you" profile, NOT a throwaway- // per-session dir. Order matters:- // explicit profile -> honored as-is (the managed/named escape hatch)- // isolated:true -> a private throwaway dir (fresh-login test, act-as-other-user)- // wiki PUBLIC view -> per-session, UNCHANGED (keeps the logged-out view truly fresh)- // everything else -> DEFAULT_PROFILE (durable, shared, credential-accumulating)- // v1.9.129: {webSecurity:false} is the dev escape hatch for cross-origin eval. It- // implies isolation — the insecure flags are per-PROCESS, and the shared credentialed- // profile must never run under them — so it overrides any profile the caller passed.+ // v1.9.162 (John: 'i want ALL pup windows to use the same profile now so you have all of+ // the user's saved logins over time — the database builds up and this is pleasurable to+ // use over time'). ONE durable jar (adom-you) for EVERYTHING, wiki AUTHED included, so+ // every login the user does anywhere accumulates into one growing credential store. The+ // ONLY windows that get a separate jar are the three that DEFINITIONALLY require it:+ // {webSecurity:false} — insecure per-process flags must never touch the credentialed jar+ // {isolated:true} — an explicit fresh/throwaway jar (login tests, act-as-another-user)+ // wiki PUBLIC view — logged-OUT by definition, needs a clean jar to show the world's view+ // Everything else, explicit profile aside, is DEFAULT_PROFILE. (wiki AUTHED no longer uses+ // the old separate adom-wiki-authed jar — its login now lives in the one shared profile.) if (args.webSecurity === false) args.isolated = true;+ if (args.wikiView === 'public' && isAdomUrl(args.url)) args.isolated = true; if (args.isolated === true) args.profile = 'iso-' + args.sessionId; // isolation beats any explicit profile- if (!args.profile) {- if (isAdomUrl(args.url)) args.profile = args.sessionId; // wiki public: unchanged- else args.profile = DEFAULT_PROFILE;- }+ if (!args.profile) args.profile = DEFAULT_PROFILE; const sessionId = args.sessionId; // v1.9.110 (issue #22): NEVER LEAVE A SESSION UNOWNED, and settle ownership at ADMISSION. // The owner is the explicit `owner` arg when given, else the calling AI thread's own name@@ -7571,7 +7569,7 @@ const server = http.createServer(async (req, res) => { if (be.refCount <= 0) { try { await killBrowserProcess(be.browser, oldProfile); } catch (e) {} browsers.delete(oldProfile); } } // Relaunch the SAME sessionId under the new profile at the same URL.- const newProfile = view === 'authed' ? WIKI_AUTH_PROFILE : publicProfile;+ const newProfile = view === 'authed' ? DEFAULT_PROFILE : ('iso-' + sessionId + '-pub'); // v1.9.162: authed = the ONE shared jar (accumulate); public = a clean logged-out jar let s2 = null; try { s2 = await launchSession(sessionId, _tabUrls[_activeIdx] || url, { profile: newProfile, owner, takeover: true, foreground: true }); } catch (e) { sendJSON(res, { success: false, error: `wiki view relaunch failed: ${e.message}` }); return; }