@addai/node 0.8.2 → 0.10.0

package/dist/unpair.js

@@ -0,0 +1,71 @@
+"use strict";
+// Disconnecting a node from +Ai.
+//
+// Shared by `ainode unpair` and the console's disconnect key, because the two
+// must not drift: this is the one action that takes work away from people, and
+// a version of it that forgets to cancel in-flight runs would leave whoever
+// was waiting on them waiting forever.
+//
+// The server soft-disables rather than deletes: the runtime row, its history
+// and its chats all survive, the token is scrubbed, and the status becomes
+// 'unpaired'. Reconnect on the AiNodes page mints a fresh code and the same
+// machine comes back as itself. That is worth saying out loud in the prompt —
+// someone who believes this is permanent will not press it when they should.
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.describeDisconnect = describeDisconnect;
+exports.summariseDisconnect = summariseDisconnect;
+exports.disconnectNode = disconnectNode;
+const supabase_client_1 = require("./supabase-client");
+const store_1 = require("./store");
+const plural = (n, word) => `${n} ${word}${n === 1 ? '' : 's'}`;
+/** The question to ask before doing it. */
+function describeDisconnect(inflight) {
+    const cost = inflight > 0
+        ? `This cancels ${plural(inflight, 'run')} still in flight. `
+        : '';
+    return `${cost}The node keeps its history and can reconnect later.`;
+}
+/** What to say once it is done. */
+function summariseDisconnect(r) {
+    if (!r.ok)
+        return `Could not disconnect: ${r.error ?? 'unknown error'}`;
+    if (r.serverFailed) {
+        // Honest about the half that worked: this machine has forgotten its
+        // pairing, but +Ai still lists the node as paired until it is removed
+        // there. Saying only "disconnected" leaves that to be discovered — and
+        // saying it without the reason leaves nobody able to act on it, which is
+        // how a transient 4s RPC timeout and a revoked grant look identical.
+        const why = r.error ? ` (${r.error})` : '';
+        return `Disconnected on this machine, but +Ai could not be told${why}. Remove the node there too.`;
+    }
+    const tail = r.cancelled > 0 ? ` ${plural(r.cancelled, 'run')} cancelled.` : '';
+    return `Disconnected from +Ai.${tail}`;
+}
+/**
+ * Tell +Ai, then forget the pairing locally.
+ *
+ * Local cleanup happens even when the server call fails. A node whose token
+ * the user has decided to abandon should not keep using it because the network
+ * was down at the wrong moment — and the alternative, refusing to disconnect,
+ * strands them on a machine they may be trying to hand back.
+ */
+async function disconnectNode() {
+    if (!(0, store_1.isPaired)())
+        return { ok: false, cancelled: 0, error: 'this node is not paired' };
+    const token = (0, store_1.readPairing)()?.daemonToken;
+    if (!token)
+        return { ok: false, cancelled: 0, error: 'this node is not paired' };
+    let cancelled = 0;
+    let serverFailed = false;
+    let serverError;
+    try {
+        const r = await (0, supabase_client_1.rpc)('runtime_self_unpair', { p_token: token });
+        cancelled = r?.cancelled_requests ?? 0;
+    }
+    catch (err) {
+        serverFailed = true;
+        serverError = err?.message || String(err);
+    }
+    (0, store_1.clearPairing)();
+    return { ok: true, cancelled, serverFailed, error: serverError };
+}

package/package.json

@@ -1,60 +1,60 @@
-{
-  "name": "@addai/node",
-  "version": "0.8.2",
-  "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"
-  ],
-  "scripts": {
-    "build": "tsc -p tsconfig.json",
-    "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": {
-    "node-pty": "^1.1.0",
-    "ws": "^8.21.1"
-  },
-  "devDependencies": {
-    "@types/node": "^20.0.0",
-    "@types/ws": "^8.18.1",
-    "typescript": "^5.6.0"
-  }
-}
+{
+  "name": "@addai/node",
+  "version": "0.10.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"
+  ],
+  "scripts": {
+    "build": "tsc -p tsconfig.json",
+    "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": {
+    "node-pty": "^1.1.0",
+    "ws": "^8.21.1"
+  },
+  "devDependencies": {
+    "@types/node": "^20.0.0",
+    "@types/ws": "^8.18.1",
+    "typescript": "^5.6.0"
+  }
+}

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);