@addai/node 0.29.0 → 0.30.0

package/dist/desktop/vault-seed.mjs

@@ -1,112 +1,112 @@
-// Plants the add.ai session cookie in a desktop's browser, from inside it.
-//
-// Runs in the container, not the daemon: the debugging port is bound to
-// loopback there on purpose (CDP is total control of a browser, and the host
-// must not be able to reach it), so the only place that can talk to it is the
-// container itself. Node 22 is in the image already — this is the same
-// arrangement +Ai Learn's recorder uses.
-//
-// Launched by the browser wrapper, in the background, immediately before Chrome
-// starts. It waits for the port rather than assuming, sets the cookie, and
-// exits. Nothing depends on its exit code: a browser that comes up without a
-// vault session is worse than one with, but it is still a working browser.
-import * as fs from 'node:fs';
-
-const PORT = Number(process.env.ADDAI_CDP_PORT || 9222);
-const SESSION_FILE = process.env.ADDAI_VAULT_SESSION || '/conf/vault/session.json';
-const DEADLINE_MS = 60_000;
-const POLL_MS = 250;
-
-const log = (m) => process.stdout.write(`[vault-seed] ${m}\n`);
-
-/** The cookie the extension reads: URI-encoded JSON with the two tokens. */
-export function cookieValue(session) {
-  return encodeURIComponent(JSON.stringify({
-    access_token: session.access_token,
-    refresh_token: session.refresh_token,
-  }));
-}
-
-/** Both add.ai itself and every *.add.ai app, which is what the session is
- *  for — signing in at auth.add.ai signs you in across all of them. */
-export function cookieParams(session) {
-  return {
-    name: 'auth',
-    value: cookieValue(session),
-    domain: '.add.ai',
-    path: '/',
-    secure: true,
-    httpOnly: false,
-    sameSite: 'Lax',
-  };
-}
-
-async function waitForBrowser(deadline) {
-  while (Date.now() < deadline) {
-    try {
-      const res = await fetch(`http://127.0.0.1:${PORT}/json/version`);
-      if (res.ok) return await res.json();
-    } catch { /* not up yet */ }
-    await new Promise((r) => setTimeout(r, POLL_MS));
-  }
-  return null;
-}
-
-async function setCookie(wsUrl, params) {
-  const ws = new WebSocket(wsUrl);
-  await new Promise((resolve, reject) => {
-    ws.addEventListener('open', resolve, { once: true });
-    ws.addEventListener('error', () => reject(new Error('could not open the debugger')), { once: true });
-  });
-  const done = new Promise((resolve, reject) => {
-    const timer = setTimeout(() => reject(new Error('the browser did not answer')), 10_000);
-    ws.addEventListener('message', (ev) => {
-      let msg;
-      try { msg = JSON.parse(ev.data); } catch { return; }
-      if (msg.id !== 1) return;
-      clearTimeout(timer);
-      if (msg.error) reject(new Error(msg.error.message || 'setCookie failed'));
-      else resolve(msg.result);
-    });
-  });
-  ws.send(JSON.stringify({ id: 1, method: 'Network.setCookie', params }));
-  // finally, not after the await: an error reply rejects, and a socket left
-  // open holds the event loop forever. The failure mode is a hung node process
-  // per browser launch, which is worse than the failure it is reporting.
-  try {
-    return await done;
-  } finally {
-    ws.close();
-  }
-}
-
-async function main() {
-  let session;
-  try {
-    session = JSON.parse(fs.readFileSync(SESSION_FILE, 'utf8'));
-  } catch {
-    log('no session staged for this desktop — the vault will be empty until somebody signs in');
-    return;
-  }
-  if (!session?.access_token || !session?.refresh_token) {
-    log('the staged session is not usable');
-    return;
-  }
-
-  const version = await waitForBrowser(Date.now() + DEADLINE_MS);
-  if (!version?.webSocketDebuggerUrl) {
-    log('the browser never opened its debugging port');
-    return;
-  }
-  try {
-    const res = await setCookie(version.webSocketDebuggerUrl, cookieParams(session));
-    log(res?.success === false ? 'the browser refused the cookie' : 'signed in');
-  } catch (err) {
-    log(`could not sign in: ${err.message}`);
-  }
-}
-
-// Importable for tests; only runs when executed directly.
-if (process.argv[1] && process.argv[1].endsWith('vault-seed.mjs')) {
-  main().catch((err) => log(`unexpected: ${err.message}`));
-}
+// Plants the add.ai session cookie in a desktop's browser, from inside it.
+//
+// Runs in the container, not the daemon: the debugging port is bound to
+// loopback there on purpose (CDP is total control of a browser, and the host
+// must not be able to reach it), so the only place that can talk to it is the
+// container itself. Node 22 is in the image already — this is the same
+// arrangement +Ai Learn's recorder uses.
+//
+// Launched by the browser wrapper, in the background, immediately before Chrome
+// starts. It waits for the port rather than assuming, sets the cookie, and
+// exits. Nothing depends on its exit code: a browser that comes up without a
+// vault session is worse than one with, but it is still a working browser.
+import * as fs from 'node:fs';
+
+const PORT = Number(process.env.ADDAI_CDP_PORT || 9222);
+const SESSION_FILE = process.env.ADDAI_VAULT_SESSION || '/conf/vault/session.json';
+const DEADLINE_MS = 60_000;
+const POLL_MS = 250;
+
+const log = (m) => process.stdout.write(`[vault-seed] ${m}\n`);
+
+/** The cookie the extension reads: URI-encoded JSON with the two tokens. */
+export function cookieValue(session) {
+  return encodeURIComponent(JSON.stringify({
+    access_token: session.access_token,
+    refresh_token: session.refresh_token,
+  }));
+}
+
+/** Both add.ai itself and every *.add.ai app, which is what the session is
+ *  for — signing in at auth.add.ai signs you in across all of them. */
+export function cookieParams(session) {
+  return {
+    name: 'auth',
+    value: cookieValue(session),
+    domain: '.add.ai',
+    path: '/',
+    secure: true,
+    httpOnly: false,
+    sameSite: 'Lax',
+  };
+}
+
+async function waitForBrowser(deadline) {
+  while (Date.now() < deadline) {
+    try {
+      const res = await fetch(`http://127.0.0.1:${PORT}/json/version`);
+      if (res.ok) return await res.json();
+    } catch { /* not up yet */ }
+    await new Promise((r) => setTimeout(r, POLL_MS));
+  }
+  return null;
+}
+
+async function setCookie(wsUrl, params) {
+  const ws = new WebSocket(wsUrl);
+  await new Promise((resolve, reject) => {
+    ws.addEventListener('open', resolve, { once: true });
+    ws.addEventListener('error', () => reject(new Error('could not open the debugger')), { once: true });
+  });
+  const done = new Promise((resolve, reject) => {
+    const timer = setTimeout(() => reject(new Error('the browser did not answer')), 10_000);
+    ws.addEventListener('message', (ev) => {
+      let msg;
+      try { msg = JSON.parse(ev.data); } catch { return; }
+      if (msg.id !== 1) return;
+      clearTimeout(timer);
+      if (msg.error) reject(new Error(msg.error.message || 'setCookie failed'));
+      else resolve(msg.result);
+    });
+  });
+  ws.send(JSON.stringify({ id: 1, method: 'Network.setCookie', params }));
+  // finally, not after the await: an error reply rejects, and a socket left
+  // open holds the event loop forever. The failure mode is a hung node process
+  // per browser launch, which is worse than the failure it is reporting.
+  try {
+    return await done;
+  } finally {
+    ws.close();
+  }
+}
+
+async function main() {
+  let session;
+  try {
+    session = JSON.parse(fs.readFileSync(SESSION_FILE, 'utf8'));
+  } catch {
+    log('no session staged for this desktop — the vault will be empty until somebody signs in');
+    return;
+  }
+  if (!session?.access_token || !session?.refresh_token) {
+    log('the staged session is not usable');
+    return;
+  }
+
+  const version = await waitForBrowser(Date.now() + DEADLINE_MS);
+  if (!version?.webSocketDebuggerUrl) {
+    log('the browser never opened its debugging port');
+    return;
+  }
+  try {
+    const res = await setCookie(version.webSocketDebuggerUrl, cookieParams(session));
+    log(res?.success === false ? 'the browser refused the cookie' : 'signed in');
+  } catch (err) {
+    log(`could not sign in: ${err.message}`);
+  }
+}
+
+// Importable for tests; only runs when executed directly.
+if (process.argv[1] && process.argv[1].endsWith('vault-seed.mjs')) {
+  main().catch((err) => log(`unexpected: ${err.message}`));
+}

package/dist/tui/run.js

@@ -91,6 +91,9 @@ function createConsole(build, hooks = {}) {
     function onKeypress(_s, key) {
         void app.handleKey(key);
     }
+    function onStdinError() {
+        teardown();
+    }
     function attachInput() {
         if (inputAttached)
             return;
@@ -99,12 +102,20 @@ function createConsole(build, hooks = {}) {
             process.stdin.setRawMode(true);
         process.stdin.resume();
         process.stdin.on('keypress', onKeypress);
+        // A terminal can be taken away mid-read: an ssh session drops, a window
+        // closes. The read then fails with EIO, and an 'error' with no listener is
+        // a thrown exception in node — the process dies without ever running
+        // teardown, so raw mode is never turned off and the shell that inherits
+        // the terminal reports its own "error on TTY read" afterwards. Treat it as
+        // what it is: the terminal is gone, so put it back and leave quietly.
+        process.stdin.on('error', onStdinError);
         inputAttached = true;
     }
     function detachInput() {
         if (!inputAttached)
             return;
         process.stdin.off('keypress', onKeypress);
+        process.stdin.off('error', onStdinError);
         if (process.stdin.isTTY)
             process.stdin.setRawMode(false);
         process.stdin.pause();
@@ -142,6 +153,16 @@ function createConsole(build, hooks = {}) {
             draw();
         }
     };
+    // Backgrounding a TUI is not an error, but reading the terminal from a
+    // background process group earns SIGTTIN, and the default action is to STOP
+    // the process — which is what "zsh: suspended (tty input)" is. Stopped mid-
+    // draw it still holds the terminal in raw mode, so the session it was
+    // sharing degrades too. Stop reading and leave instead; the daemon is a
+    // separate process and keeps running either way.
+    process.on('SIGTTIN', teardown);
+    process.on('SIGTTOU', teardown);
+    // The terminal went away without the read failing first.
+    process.on('SIGHUP', teardown);
     app.replace(build(app, suspend));
     return {
         host: app,

package/package.json

@@ -1,62 +1,62 @@
-{
-  "name": "@addai/node",
-  "version": "0.29.0",
-  "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": [
-    "addai",
-    "entity-studio",
-    "claude",
-    "codex",
-    "kimi",
-    "gemini",
-    "agent",
-    "daemon",
-    "supabase",
-    "mcp"
-  ],
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/just-AddAi/addai-entity-runtime.git"
-  },
-  "homepage": "https://github.com/just-AddAi/addai-entity-runtime#readme",
-  "bugs": {
-    "url": "https://github.com/just-AddAi/addai-entity-runtime/issues"
-  },
-  "type": "commonjs",
-  "main": "dist/index.js",
-  "bin": {
-    "ainode": "dist/cli.js"
-  },
-  "publishConfig": {
-    "access": "public"
-  },
-  "files": [
-    "dist",
-    "scripts",
-    "README.md",
-    "assets"
-  ],
-  "scripts": {
-    "build": "tsc -p tsconfig.json && node scripts/copy-assets.js",
-    "start": "node dist/cli.js",
-    "dev": "tsc -p tsconfig.json && node dist/cli.js",
-    "test": "npm run build && node --test test/*.test.mjs",
-    "clean": "node -e \"fs.rmSync('dist',{recursive:true,force:true})\"",
-    "postinstall": "node scripts/fix-pty-helper.js",
-    "prepublishOnly": "npm run build"
-  },
-  "engines": {
-    "node": ">=18"
-  },
-  "dependencies": {
-    "@addai/node-flows": "^1.0.0",
-    "node-pty": "^1.1.0",
-    "ws": "^8.21.3"
-  },
-  "devDependencies": {
-    "@types/node": "^20.0.0",
-    "@types/ws": "^8.18.1",
-    "typescript": "^5.6.0"
-  }
-}
+{
+  "name": "@addai/node",
+  "version": "0.30.0",
+  "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": [
+    "addai",
+    "entity-studio",
+    "claude",
+    "codex",
+    "kimi",
+    "gemini",
+    "agent",
+    "daemon",
+    "supabase",
+    "mcp"
+  ],
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/just-AddAi/addai-entity-runtime.git"
+  },
+  "homepage": "https://github.com/just-AddAi/addai-entity-runtime#readme",
+  "bugs": {
+    "url": "https://github.com/just-AddAi/addai-entity-runtime/issues"
+  },
+  "type": "commonjs",
+  "main": "dist/index.js",
+  "bin": {
+    "ainode": "dist/cli.js"
+  },
+  "publishConfig": {
+    "access": "public"
+  },
+  "files": [
+    "dist",
+    "scripts",
+    "README.md",
+    "assets"
+  ],
+  "scripts": {
+    "build": "tsc -p tsconfig.json && node scripts/copy-assets.js",
+    "start": "node dist/cli.js",
+    "dev": "tsc -p tsconfig.json && node dist/cli.js",
+    "test": "npm run build && node --test test/*.test.mjs",
+    "clean": "node -e \"fs.rmSync('dist',{recursive:true,force:true})\"",
+    "postinstall": "node scripts/fix-pty-helper.js",
+    "prepublishOnly": "npm run build"
+  },
+  "engines": {
+    "node": ">=18"
+  },
+  "dependencies": {
+    "@addai/node-flows": "^1.0.0",
+    "node-pty": "^1.1.0",
+    "ws": "^8.21.3"
+  },
+  "devDependencies": {
+    "@types/node": "^20.0.0",
+    "@types/ws": "^8.18.1",
+    "typescript": "^5.6.0"
+  }
+}

package/scripts/copy-assets.js

@@ -1,18 +1,18 @@
-// tsc compiles .ts and ignores everything else, but two files in this package
-// are deliberately plain .mjs: they run inside a desktop container (node 22,
-// no build step, no node_modules) rather than in the daemon. Ship them next to
-// the compiled output so dist/ is self-contained.
-const fs = require('fs');
-const path = require('path');
-
-const ASSETS = [
-  ['src/desktop/learn/recorder.mjs', 'dist/desktop/learn/recorder.mjs'],
-  ['src/desktop/learn/injected.mjs', 'dist/desktop/learn/injected.mjs'],
-  ['src/desktop/vault-seed.mjs', 'dist/desktop/vault-seed.mjs'],
-];
-
-for (const [from, to] of ASSETS) {
-  fs.mkdirSync(path.dirname(to), { recursive: true });
-  fs.copyFileSync(from, to);
-}
-console.log(`copied ${ASSETS.length} runtime assets into dist/`);
+// tsc compiles .ts and ignores everything else, but two files in this package
+// are deliberately plain .mjs: they run inside a desktop container (node 22,
+// no build step, no node_modules) rather than in the daemon. Ship them next to
+// the compiled output so dist/ is self-contained.
+const fs = require('fs');
+const path = require('path');
+
+const ASSETS = [
+  ['src/desktop/learn/recorder.mjs', 'dist/desktop/learn/recorder.mjs'],
+  ['src/desktop/learn/injected.mjs', 'dist/desktop/learn/injected.mjs'],
+  ['src/desktop/vault-seed.mjs', 'dist/desktop/vault-seed.mjs'],
+];
+
+for (const [from, to] of ASSETS) {
+  fs.mkdirSync(path.dirname(to), { recursive: true });
+  fs.copyFileSync(from, to);
+}
+console.log(`copied ${ASSETS.length} runtime assets into dist/`);

package/scripts/fix-pty-helper.js

@@ -1,28 +1,28 @@
-#!/usr/bin/env node
-// node-pty ships POSIX prebuilds whose `spawn-helper` binary can lose its
-// executable bit when the npm tarball is extracted. macOS node-pty
-// posix_spawn()s that helper, so without +x every PTY spawn dies with
-// "posix_spawnp failed." — see src/pty-helper.ts for the full story.
-//
-// This used to hunt for <pkg>/node_modules/node-pty by hand, a path that
-// only exists when node-pty is NESTED. npm hoists it to the tree root under
-// npx, so the fix silently did nothing on exactly the installs that needed
-// it. The real logic now lives in the daemon (dist/pty-helper.js) and
-// resolves the package the way Node does. The daemon also repairs at boot,
-// so if dist isn't built yet (a source checkout installing before its first
-// build) we exit quietly instead of duplicating the logic here.
-
-let mod;
-try {
-  mod = require('../dist/pty-helper.js');
-} catch {
-  process.exit(0);
-}
-
-try {
-  const line = mod.describeRepair(mod.ensurePtyHelperExecutable());
-  if (line) process.stdout.write(`[entities-runtime] ${line}\n`);
-} catch (err) {
-  process.stderr.write(`[entities-runtime] pty helper check failed: ${err.message}\n`);
-}
-process.exit(0);
+#!/usr/bin/env node
+// node-pty ships POSIX prebuilds whose `spawn-helper` binary can lose its
+// executable bit when the npm tarball is extracted. macOS node-pty
+// posix_spawn()s that helper, so without +x every PTY spawn dies with
+// "posix_spawnp failed." — see src/pty-helper.ts for the full story.
+//
+// This used to hunt for <pkg>/node_modules/node-pty by hand, a path that
+// only exists when node-pty is NESTED. npm hoists it to the tree root under
+// npx, so the fix silently did nothing on exactly the installs that needed
+// it. The real logic now lives in the daemon (dist/pty-helper.js) and
+// resolves the package the way Node does. The daemon also repairs at boot,
+// so if dist isn't built yet (a source checkout installing before its first
+// build) we exit quietly instead of duplicating the logic here.
+
+let mod;
+try {
+  mod = require('../dist/pty-helper.js');
+} catch {
+  process.exit(0);
+}
+
+try {
+  const line = mod.describeRepair(mod.ensurePtyHelperExecutable());
+  if (line) process.stdout.write(`[entities-runtime] ${line}\n`);
+} catch (err) {
+  process.stderr.write(`[entities-runtime] pty helper check failed: ${err.message}\n`);
+}
+process.exit(0);