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
Force the canonical toolbar icon order on durable profiles. Re-pinning an already-pinned extension does not move it, so on the adom-you profile (where the three Adom icons were already pinned in a prior random order) 2.0.147's sequential pin had no effect. ensureExtensionsEnabled now UNPINS all three Adom extensions first, then re-pins them in rank order (Pup, Annotate, Identity) so Identity lands last / rightmost, next to Chrome's own profile avatar, deterministically on every profile including ones already pinned.
4 files changed
+16−7
adom-bridge-puppeteer-manifest.json+4−4@@ -1,10 +1,10 @@ { "manifest_version": 1, "name": "puppeteer",- "version": "2.0.148",- "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.148/adom-bridge-puppeteer-v2.0.148.zip",- "sha256": "1c7445289f50f015e846f55358783c8d0e9e47abd0473924ad12d28d195a79aa",- "size": 899573,+ "version": "2.0.149",+ "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.149/adom-bridge-puppeteer-v2.0.149.zip",+ "sha256": "a9ef1818d5705c72cfcda817c734b8af7e62f4c2e1a5198cb893f4b6456def88",+ "size": 899799, "verbPrefixes": [ "browser_", "desktop_recorder_",
src/BRIDGE_VERSION+1−1@@ -1 +1 @@-2.0.148+2.0.149
src/bridge.json+1−1@@ -2,7 +2,7 @@ "manifest_version": 1, "name": "puppeteer", "displayName": "Puppeteer (Chrome for Testing + Native)",- "version": "2.0.148",+ "version": "2.0.149", "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+10−1@@ -2908,7 +2908,16 @@ async function ensureExtensionsEnabled(browser, profileName) { // SEQUENTIALLY (await each before the next) so the layout is deterministic every time. const rank = (n) => /^Adom Pup\b/.test(n) ? 0 : /^Adom Annotate\b/.test(n) ? 1 : /^Adom Identity\b/.test(n) ? 3 : 2; adom.sort((a, b) => rank(a.name || '') - rank(b.name || '') || String(a.name).localeCompare(String(b.name)));+ // Chrome appends a newly-pinned action to the END of the toolbar row, and re-pinning an+ // already-pinned extension does NOT move it. So to FORCE the canonical left-to-right order+ // on a durable profile where they may already be pinned in some prior (random) order, we+ // UNPIN all three first, then PIN them back in rank order — Pup, Annotate, Identity — so+ // Identity lands last (rightmost, by Chrome's own profile avatar). All strictly sequential. let pinned = 0;+ const unpin = (idx, done) => {+ if (idx >= adom.length) return done();+ chrome.developerPrivate.updateExtensionConfiguration({ extensionId: adom[idx].id, pinnedToToolbar: false }, () => unpin(idx + 1, done));+ }; const pinNext = (idx) => { if (idx >= adom.length) return resolve({ ok: true, devMode: true, pinned, total: adom.length, order: adom.map(a => a.name) }); chrome.developerPrivate.updateExtensionConfiguration({ extensionId: adom[idx].id, pinnedToToolbar: true }, () => {@@ -2916,7 +2925,7 @@ async function ensureExtensionsEnabled(browser, profileName) { pinNext(idx + 1); // strictly sequential → deterministic toolbar order }); };- pinNext(0);+ unpin(0, () => pinNext(0)); }); }); } catch (e) { resolve({ ok: false, why: e.message }); }