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
Fixes the pup toolbar logo for real, and roots out why it was missing. Chrome for Testing now DISABLES unpacked (load-extension) extensions until the profiles Developer mode is on, so the Adom action icons had no action, could not be pinned, and hid in the puzzle-piece overflow. Developer mode lives in HMAC-signed Secure Preferences that pup cannot seed by writing files, so pup now calls the developerPrivate API on a short-lived background chrome://extensions page at each launch to turn Developer mode on and pin every Adom action icon. This is also the only path that fixes a fresh profile, where dev mode starts off. The four-dot pup mark, the identity avatar, and the annotate pen now sit pinned in the toolbar
4 files changed
+51−6
adom-bridge-puppeteer-manifest.json+4−4@@ -1,10 +1,10 @@ { "manifest_version": 1, "name": "puppeteer",- "version": "2.0.113",- "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.113/adom-bridge-puppeteer-v2.0.113.zip",- "sha256": "a79368149c3fba7affca3b5828a9564992cda246625140c41b9b13c7173b158b",- "size": 861538,+ "version": "2.0.114",+ "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.114/adom-bridge-puppeteer-v2.0.114.zip",+ "sha256": "accf09d0bff7c6a92b8ee50f827ba07aecada5ad9aa9327b9e1a24c91918452e",+ "size": 862537, "verbPrefixes": [ "browser_", "desktop_recorder_",
src/BRIDGE_VERSION+1−1@@ -1 +1 @@-2.0.113+2.0.114
src/bridge.json+1−1@@ -2,7 +2,7 @@ "manifest_version": 1, "name": "puppeteer", "displayName": "Puppeteer (Chrome for Testing + Native)",- "version": "2.0.113",+ "version": "2.0.114", "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+45@@ -2613,6 +2613,43 @@ function prepareCleanProfile(userDataDir) { // // Runs pre-launch (Chrome not yet holding this dir), same as prepareCleanProfile — // Local State can only be safely rewritten while the profile's Chrome is closed.+// v2.0.114: turn on the profile's Developer mode (so CfT enables unpacked extensions) and pin+// every Adom action icon, via the developerPrivate API on a short-lived chrome://extensions page.+// Idempotent + guarded per browser instance; entirely background (a hidden about:blank→extensions+// page opened and closed, never surfaced). Once dev mode is set, Chrome persists it in Secure+// Preferences with a valid HMAC, so later launches of this profile keep it — but running every+// launch is cheap insurance and the only path that fixes a FRESH profile (dev mode starts off).+const _extEnabledFor = new Set();+async function ensureExtensionsEnabled(browser, profileName) {+ if (_extEnabledFor.has(profileName)) return;+ let page = null;+ try {+ page = await browser.newPage();+ await page.goto('chrome://extensions', { waitUntil: 'domcontentloaded', timeout: 8000 }).catch(() => {});+ const r = await page.evaluate(() => new Promise((resolve) => {+ try {+ if (!(chrome && chrome.developerPrivate)) return resolve({ ok: false, why: 'no developerPrivate' });+ chrome.developerPrivate.updateProfileConfiguration({ inDeveloperMode: true }, () => {+ chrome.developerPrivate.getExtensionsInfo((infos) => {+ const adom = (infos || []).filter((i) => /^Adom /.test(i.name || ''));+ let pending = adom.length;+ if (!pending) return resolve({ ok: true, devMode: true, pinned: 0 });+ let pinned = 0;+ adom.forEach((i) => {+ chrome.developerPrivate.updateExtensionConfiguration({ extensionId: i.id, pinnedToToolbar: true }, () => {+ if (!chrome.runtime.lastError) pinned++;+ if (--pending === 0) resolve({ ok: true, devMode: true, pinned, total: adom.length });+ });+ });+ });+ });+ } catch (e) { resolve({ ok: false, why: e.message }); }+ }));+ if (r && r.ok) { _extEnabledFor.add(profileName); console.log(`[ext] "${profileName}": developer mode on, pinned ${r.pinned}/${r.total || 0} Adom toolbar icons`); }+ else { console.log(`[ext] "${profileName}": could not enable/pin (${r && r.why})`); }+ } catch (e) { console.log(`[ext] ensureExtensionsEnabled("${profileName}") error: ${e.message}`); }+ finally { try { if (page) await page.close(); } catch (e) {} }+} function brandPupProfile(userDataDir, profileName, displayName) { if (!userDataDir) return; try {@@ -8507,6 +8544,14 @@ async function getOrLaunchBrowser(profileName, { freshProfile = false, strictPer browsers.set(profileName, { browser, refCount: 0 }); + // v2.0.114 (John: "get your pup icon into this toolbar"). ROOT CAUSE of the missing toolbar+ // tiles: Chrome for Testing now DISABLES unpacked (--load-extension) extensions until the+ // profile's Developer mode is on — so the Adom action icons had no action, could not be pinned,+ // and hid in the puzzle menu. Developer mode lives in HMAC-signed Secure Preferences, so pup+ // cannot seed it by writing files; it must call the developerPrivate API in a chrome://extensions+ // page. This does that once per launch (fire-and-forget), then pins every Adom action icon.+ if (pupSettings().toolbarExtension !== 'off') ensureExtensionsEnabled(browser, profileName).catch(() => {});+ // v1.4.12: pre-grant the dialog-suppressing permissions before any // navigation happens. Done at browser-context level so every tab/origin // inherits — caller doesn't need to re-grant per origin. See