@addai/node 0.30.3 → 0.30.5

package/dist/desktop/learn/browser.js

@@ -115,6 +115,38 @@ const FIRST_RUN = ' --no-first-run --no-default-browser-check --hide-crash-resto
 /** The in-container script that signs the browser in. Beside the extension,
  *  under the same bind mount, so it arrives by the same route. */
 exports.SEED_SCRIPT = '/conf/vault/vault-seed.mjs';
+/**
+ * Chrome's profile, on the mount, and named.
+ *
+ * ⚠️ This one flag fixes three separate things, which is why it is worth the
+ * one-off cost below.
+ *
+ * THE DEBUG PORT. Chrome has refused --remote-debugging-port on the DEFAULT
+ * user data directory since M136. We have always passed the port and never
+ * passed a directory, so the port has never listened — verified on a live
+ * container, where Chrome's own command line carried
+ * --remote-debugging-port=9222 while nothing was bound to 9222. Every reason
+ * the wrapper exists — +Ai Learn watching which control was clicked, the vault
+ * seeder attaching — has therefore been quietly dead on modern Chrome.
+ *
+ * THE PROFILE. Chrome's default lives in the container's writable layer, which
+ * a rebuild destroys. So every login an entity has ever made was thrown away
+ * the next time its desktop was rebuilt. /conf is bind-mounted from the host
+ * (provider.ts publishes it), so a profile here SURVIVES — which is the first
+ * time that has been true.
+ *
+ * THE BOT WALL. A profile with no history and no cookies is a brand-new
+ * stranger, and Google treats it like one. That is a large part of why an
+ * entity meets a CAPTCHA on an ordinary search. A profile that persists earns
+ * reputation instead of resetting it daily.
+ *
+ * ⚠️ THE ONE-OFF COST, stated plainly: this abandons whatever is in the
+ * current default profile, so an entity signed into something appears signed
+ * out, once. That profile was already destroyed on every rebuild, so nothing
+ * durable is being lost — the loss has simply been happening quietly, and this
+ * is the last time.
+ */
+const PROFILE_DIR = '/conf/browser-profile';
 /**
  * The wrapper, exactly.
  *
@@ -139,10 +171,33 @@ function wrapperScript(realBrowser, extensionDir) {
     const seed = extensionDir
         ? `[ -f ${exports.SEED_SCRIPT} ] && (node ${exports.SEED_SCRIPT} >/dev/null 2>&1 &)\n`
         : '';
+    // ⚠️ A lock that now outlives the machine that made it.
+    //
+    // Chrome writes SingletonLock as a symlink to "<hostname>-<pid>" and refuses
+    // to open a profile locked by somebody else. That was harmless while the
+    // profile lived in the container's writable layer, because a rebuild
+    // destroyed the lock along with everything else. Putting the profile on the
+    // mount to make it SURVIVE means the lock survives too — and a container's
+    // hostname is its id, which changes every rebuild. So the next container
+    // finds a lock owned by a machine that no longer exists and shows
+    //
+    //     The profile appears to be in use by another Google Chrome process
+    //     (674) on another computer (7fd0c26e0fdf)
+    //
+    // instead of the page it was asked for. Persistence brought this with it;
+    // it is the cost of the same change, and it needed paying here.
+    //
+    // Guarded on nothing being alive, which is what makes this safe rather than
+    // reckless: two Chromes on one profile corrupts it. If one IS running, the
+    // lock is real and must stand — the singleton then does its actual job and
+    // hands the url to the running browser, which is the behaviour we want.
+    const unlock = `pgrep -f '${realBrowser}' >/dev/null 2>&1 || `
+        + `rm -f ${PROFILE_DIR}/SingletonLock ${PROFILE_DIR}/SingletonCookie `
+        + `${PROFILE_DIR}/SingletonSocket\n`;
     return `#!/bin/sh
 # Written by @addai/node so +Ai Learn can watch this browser${extensionDir ? ' and the +Ai Vault can fill logins in it' : ''}.
 # Removing it costs you the page detail in a lesson${extensionDir ? ' and vault autofill' : ''} and nothing else.
-${seed}exec ${realBrowser} --remote-debugging-port=${exports.DEBUG_PORT} --remote-debugging-address=127.0.0.1${FIRST_RUN}${ext} "$@"
+${unlock}${seed}exec ${realBrowser} --user-data-dir=${PROFILE_DIR} --remote-debugging-port=${exports.DEBUG_PORT} --remote-debugging-address=127.0.0.1${FIRST_RUN}${ext} "$@"
 `;
 }
 /** Is what is on disk already what we would write? Exact match, so a change to

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@addai/node",
-  "version": "0.30.3",
+  "version": "0.30.5",
   "description": "Daemon that pairs a machine with your +Ai account and runs Claude / Codex / Kimi / Gemini agents on its behalf. Reachable via Supabase from Vault, Entity Studio, or any other +Ai surface.",
   "license": "MIT",
   "keywords": [