@addai/node 0.30.4 → 0.30.5

package/dist/desktop/learn/browser.js

@@ -171,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} --user-data-dir=${PROFILE_DIR} --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.4",
+  "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": [