@addai/node 0.8.2 → 0.10.0

package/README.md

@@ -1,96 +1,96 @@
-# entities-runtime
-
-A standalone Node.js daemon. Install it on any machine, pair with your
-+Ai account, and your account can then run Claude Code / Codex sessions
-on that machine on its behalf — from Vault, from Entity Studio, or from
-anywhere else in +Ai.
-
-## Quick start
-
-```bash
-npx entities-runtime
-```
-
-The first run prints a 5-letter pairing code and a URL:
-
-```
-Pair this runtime with your +Ai account.
-
-  https://vault.add.ai/entity/connect/HDXYC
-
-Enter this code: HDXYC
-```
-
-Open the URL while signed into Vault, enter the code, and the runtime
-starts polling for work. Capabilities (claude, codex, git, node) are
-reported every 30 s.
-
-## Commands
-
-```
-entities-runtime                  run the daemon (foreground)
-entities-runtime status           pairing + capabilities + last-seen
-entities-runtime sessions         recent requests handled (--limit N)
-entities-runtime unpair --yes     disconnect from +Ai
-entities-runtime version          print version
-```
-
-`status` and `sessions` work without the daemon running — they hit
-Supabase directly using the daemon token in
-`~/.entities-runtime/state.json`.
-
-## Architecture
-
-See [`docs/architecture.md`](docs/architecture.md) for the full picture:
-Supabase tables, RPC inventory, request lifecycle, and the cancel-watcher
-flow.
-
-## DiskGuard — Codex scratch-dir disk protection
-
-Each Codex run gets a throwaway `CODEX_HOME` under the OS temp dir
-(`entities-codex-<rand>`). Codex writes its `state_*.sqlite`, logs, caches
-and shell snapshots there — typically 50–350 MB per run. codex-spawn now
-deletes that dir on exit, but a `SIGKILL`, a crash, or an orphan left by a
-previous runtime process can skip that path. On a dedicated host doing
-thousands of runs, those leftovers once grew to ~158 GiB and filled the
-disk (`ENOSPC`, repeated crashes).
-
-**DiskGuard** is the safety net. Like a CCTV DVR overwriting the oldest
-footage when the disk fills, it watches free space on the volume holding
-the temp dir and, when usage crosses a high-water mark, deletes the
-**oldest inactive** scratch dirs — oldest first — until usage drops back
-below a low-water mark, leaving a buffer for the OS. It runs at startup, on
-an interval, and opportunistically right before each new Codex run.
-
-Safety guarantees: it only touches directories directly under the temp root
-whose names match the configured prefix (realpath-validated); it never
-deletes a dir owned by a live session (in-process, or one whose
-`session.lock` PID is still alive) or one younger than the min-age guard;
-and it removes symlink *entries* without following them, so the durable
-`~/.codex` targets behind `sessions`/`auth.json` are never harmed.
-
-Note: DiskGuard can only reclaim space by deleting scratch dirs it owns. If
-a disk is full of *other* data it will evict what it can and log that it
-couldn't reach the target rather than touching anything it doesn't own.
-
-Configure via environment variables (defaults shown):
-
-| Variable | Default | Meaning |
-|---|---|---|
-| `DISKGUARD_ENABLED` | `true` | Master switch for the sweeper. Cleanup-on-exit still runs when `false`. |
-| `DISKGUARD_HIGH_WATER_PCT` | `90` | Start evicting when volume usage reaches this %. |
-| `DISKGUARD_LOW_WATER_PCT` | `80` | Stop evicting once usage drops below this %. Clamped below high-water. |
-| `DISKGUARD_MIN_AGE_MINUTES` | `30` | Never evict a scratch dir younger than this. |
-| `DISKGUARD_CHECK_INTERVAL_SECONDS` | `60` | Periodic sweep cadence. |
-| `DISKGUARD_DRY_RUN` | `false` | Log what would be evicted without deleting anything. |
-| `DISKGUARD_PREFIXES` | `entities-codex-` | Comma-separated dir-name prefixes eligible for eviction. |
-| `DISKGUARD_TEMP_ROOT` | `os.tmpdir()` | Override the watched temp root (mainly for testing). |
-
-## Development
-
-```bash
-npm install
-npm run build
-node dist/cli.js
-npm test        # builds, then runs the node:test suite (see test/)
-```
+# entities-runtime
+
+A standalone Node.js daemon. Install it on any machine, pair with your
++Ai account, and your account can then run Claude Code / Codex sessions
+on that machine on its behalf — from Vault, from Entity Studio, or from
+anywhere else in +Ai.
+
+## Quick start
+
+```bash
+npx entities-runtime
+```
+
+The first run prints a 5-letter pairing code and a URL:
+
+```
+Pair this runtime with your +Ai account.
+
+  https://vault.add.ai/entity/connect/HDXYC
+
+Enter this code: HDXYC
+```
+
+Open the URL while signed into Vault, enter the code, and the runtime
+starts polling for work. Capabilities (claude, codex, git, node) are
+reported every 30 s.
+
+## Commands
+
+```
+entities-runtime                  run the daemon (foreground)
+entities-runtime status           pairing + capabilities + last-seen
+entities-runtime sessions         recent requests handled (--limit N)
+entities-runtime unpair --yes     disconnect from +Ai
+entities-runtime version          print version
+```
+
+`status` and `sessions` work without the daemon running — they hit
+Supabase directly using the daemon token in
+`~/.entities-runtime/state.json`.
+
+## Architecture
+
+See [`docs/architecture.md`](docs/architecture.md) for the full picture:
+Supabase tables, RPC inventory, request lifecycle, and the cancel-watcher
+flow.
+
+## DiskGuard — Codex scratch-dir disk protection
+
+Each Codex run gets a throwaway `CODEX_HOME` under the OS temp dir
+(`entities-codex-<rand>`). Codex writes its `state_*.sqlite`, logs, caches
+and shell snapshots there — typically 50–350 MB per run. codex-spawn now
+deletes that dir on exit, but a `SIGKILL`, a crash, or an orphan left by a
+previous runtime process can skip that path. On a dedicated host doing
+thousands of runs, those leftovers once grew to ~158 GiB and filled the
+disk (`ENOSPC`, repeated crashes).
+
+**DiskGuard** is the safety net. Like a CCTV DVR overwriting the oldest
+footage when the disk fills, it watches free space on the volume holding
+the temp dir and, when usage crosses a high-water mark, deletes the
+**oldest inactive** scratch dirs — oldest first — until usage drops back
+below a low-water mark, leaving a buffer for the OS. It runs at startup, on
+an interval, and opportunistically right before each new Codex run.
+
+Safety guarantees: it only touches directories directly under the temp root
+whose names match the configured prefix (realpath-validated); it never
+deletes a dir owned by a live session (in-process, or one whose
+`session.lock` PID is still alive) or one younger than the min-age guard;
+and it removes symlink *entries* without following them, so the durable
+`~/.codex` targets behind `sessions`/`auth.json` are never harmed.
+
+Note: DiskGuard can only reclaim space by deleting scratch dirs it owns. If
+a disk is full of *other* data it will evict what it can and log that it
+couldn't reach the target rather than touching anything it doesn't own.
+
+Configure via environment variables (defaults shown):
+
+| Variable | Default | Meaning |
+|---|---|---|
+| `DISKGUARD_ENABLED` | `true` | Master switch for the sweeper. Cleanup-on-exit still runs when `false`. |
+| `DISKGUARD_HIGH_WATER_PCT` | `90` | Start evicting when volume usage reaches this %. |
+| `DISKGUARD_LOW_WATER_PCT` | `80` | Stop evicting once usage drops below this %. Clamped below high-water. |
+| `DISKGUARD_MIN_AGE_MINUTES` | `30` | Never evict a scratch dir younger than this. |
+| `DISKGUARD_CHECK_INTERVAL_SECONDS` | `60` | Periodic sweep cadence. |
+| `DISKGUARD_DRY_RUN` | `false` | Log what would be evicted without deleting anything. |
+| `DISKGUARD_PREFIXES` | `entities-codex-` | Comma-separated dir-name prefixes eligible for eviction. |
+| `DISKGUARD_TEMP_ROOT` | `os.tmpdir()` | Override the watched temp root (mainly for testing). |
+
+## Development
+
+```bash
+npm install
+npm run build
+node dist/cli.js
+npm test        # builds, then runs the node:test suite (see test/)
+```

package/dist/autostart-mac.js

@@ -79,36 +79,36 @@ function buildPlist(spec) {
     const env = Object.entries(spec.env)
         .map(([k, v]) => `      <key>${esc(k)}</key>\n      <string>${esc(v)}</string>`)
         .join('\n');
-    return `<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
-<plist version="1.0">
-  <dict>
-    <key>Label</key>
-    <string>${esc(spec.label)}</string>
-    <key>ProgramArguments</key>
-    <array>
-${args}
-    </array>
-    <key>RunAtLoad</key>
-    <true/>
-    <key>KeepAlive</key>
-    <true/>
-    <key>ThrottleInterval</key>
-    <integer>10</integer>
-    <key>ProcessType</key>
-    <string>Interactive</string>
-    <key>WorkingDirectory</key>
-    <string>${esc(spec.workingDirectory)}</string>
-    <key>StandardOutPath</key>
-    <string>${esc(spec.logPath)}</string>
-    <key>StandardErrorPath</key>
-    <string>${esc(spec.logPath)}</string>
-    <key>EnvironmentVariables</key>
-    <dict>
-${env}
-    </dict>
-  </dict>
-</plist>
+    return `<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
+<plist version="1.0">
+  <dict>
+    <key>Label</key>
+    <string>${esc(spec.label)}</string>
+    <key>ProgramArguments</key>
+    <array>
+${args}
+    </array>
+    <key>RunAtLoad</key>
+    <true/>
+    <key>KeepAlive</key>
+    <true/>
+    <key>ThrottleInterval</key>
+    <integer>10</integer>
+    <key>ProcessType</key>
+    <string>Interactive</string>
+    <key>WorkingDirectory</key>
+    <string>${esc(spec.workingDirectory)}</string>
+    <key>StandardOutPath</key>
+    <string>${esc(spec.logPath)}</string>
+    <key>StandardErrorPath</key>
+    <string>${esc(spec.logPath)}</string>
+    <key>EnvironmentVariables</key>
+    <dict>
+${env}
+    </dict>
+  </dict>
+</plist>
 `;
 }
 /** Pull ProgramArguments back out of a plist we wrote, for `status`. */

package/dist/autostart-win.js

@@ -128,56 +128,56 @@ function buildVbs(cmdPath) {
  * a second daemon.
  */
 function buildTaskXml(spec) {
-    return `<?xml version="1.0" encoding="UTF-16"?>
-<Task version="1.2" xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">
-  <RegistrationInfo>
-    <Date>${xmlEsc(spec.createdAt)}</Date>
-    <Author>@addai/node</Author>
-    <Description>Runs this +Ai Node so entities can reach it. Created by \`ainode startup enable\`.</Description>
-  </RegistrationInfo>
-  <Triggers>
-    <LogonTrigger>
-      <Enabled>true</Enabled>
-      <UserId>${xmlEsc(spec.userId)}</UserId>
-      <Repetition>
-        <Interval>PT5M</Interval>
-        <StopAtDurationEnd>false</StopAtDurationEnd>
-      </Repetition>
-    </LogonTrigger>
-  </Triggers>
-  <Principals>
-    <Principal id="Author">
-      <UserId>${xmlEsc(spec.userId)}</UserId>
-      <LogonType>InteractiveToken</LogonType>
-      <RunLevel>LeastPrivilege</RunLevel>
-    </Principal>
-  </Principals>
-  <Settings>
-    <MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>
-    <DisallowStartIfOnBatteries>false</DisallowStartIfOnBatteries>
-    <StopIfGoingOnBatteries>false</StopIfGoingOnBatteries>
-    <AllowHardTerminate>true</AllowHardTerminate>
-    <StartWhenAvailable>true</StartWhenAvailable>
-    <RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
-    <IdleSettings>
-      <StopOnIdleEnd>false</StopOnIdleEnd>
-      <RestartOnIdle>false</RestartOnIdle>
-    </IdleSettings>
-    <AllowStartOnDemand>true</AllowStartOnDemand>
-    <Enabled>true</Enabled>
-    <Hidden>false</Hidden>
-    <RunOnlyIfIdle>false</RunOnlyIfIdle>
-    <WakeToRun>false</WakeToRun>
-    <ExecutionTimeLimit>PT0S</ExecutionTimeLimit>
-    <Priority>7</Priority>
-  </Settings>
-  <Actions Context="Author">
-    <Exec>
-      <Command>${xmlEsc(spec.wscriptPath)}</Command>
-      <Arguments>"${xmlEsc(spec.vbsPath)}"</Arguments>
-    </Exec>
-  </Actions>
-</Task>
+    return `<?xml version="1.0" encoding="UTF-16"?>
+<Task version="1.2" xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">
+  <RegistrationInfo>
+    <Date>${xmlEsc(spec.createdAt)}</Date>
+    <Author>@addai/node</Author>
+    <Description>Runs this +Ai Node so entities can reach it. Created by \`ainode startup enable\`.</Description>
+  </RegistrationInfo>
+  <Triggers>
+    <LogonTrigger>
+      <Enabled>true</Enabled>
+      <UserId>${xmlEsc(spec.userId)}</UserId>
+      <Repetition>
+        <Interval>PT5M</Interval>
+        <StopAtDurationEnd>false</StopAtDurationEnd>
+      </Repetition>
+    </LogonTrigger>
+  </Triggers>
+  <Principals>
+    <Principal id="Author">
+      <UserId>${xmlEsc(spec.userId)}</UserId>
+      <LogonType>InteractiveToken</LogonType>
+      <RunLevel>LeastPrivilege</RunLevel>
+    </Principal>
+  </Principals>
+  <Settings>
+    <MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>
+    <DisallowStartIfOnBatteries>false</DisallowStartIfOnBatteries>
+    <StopIfGoingOnBatteries>false</StopIfGoingOnBatteries>
+    <AllowHardTerminate>true</AllowHardTerminate>
+    <StartWhenAvailable>true</StartWhenAvailable>
+    <RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
+    <IdleSettings>
+      <StopOnIdleEnd>false</StopOnIdleEnd>
+      <RestartOnIdle>false</RestartOnIdle>
+    </IdleSettings>
+    <AllowStartOnDemand>true</AllowStartOnDemand>
+    <Enabled>true</Enabled>
+    <Hidden>false</Hidden>
+    <RunOnlyIfIdle>false</RunOnlyIfIdle>
+    <WakeToRun>false</WakeToRun>
+    <ExecutionTimeLimit>PT0S</ExecutionTimeLimit>
+    <Priority>7</Priority>
+  </Settings>
+  <Actions Context="Author">
+    <Exec>
+      <Command>${xmlEsc(spec.wscriptPath)}</Command>
+      <Arguments>"${xmlEsc(spec.vbsPath)}"</Arguments>
+    </Exec>
+  </Actions>
+</Task>
 `;
 }
 function schtasks(args) {

package/dist/cli.js

@@ -3,6 +3,7 @@
 // ainode CLI — the +Ai Node console.
 //
 //   ainode                run this node: daemon + live dashboard
+//   ainode entities       the same, pairing into +Ai Entities rather than Vault
 //   ainode harnesses      interactive harness manager (install / login)
 //   ainode startup …      start this node when the machine starts
 //   ainode unpair --yes   disconnect from +Ai, cancel in-flight work
@@ -53,7 +54,7 @@ Object.defineProperty(exports, "__esModule", { value: true });
 const lockfile_1 = require("./lockfile");
 const index_1 = require("./index");
 const store_1 = require("./store");
-const supabase_client_1 = require("./supabase-client");
+const unpair_1 = require("./unpair");
 const run_1 = require("./tui/run");
 const autostart = __importStar(require("./autostart"));
 const args = process.argv.slice(2);
@@ -72,21 +73,16 @@ async function cmdUnpair() {
     }
     const confirm = args.includes('--yes') || args.includes('-y');
     if (!confirm) {
-        console.log('This will disconnect the runtime from +Ai and cancel any in-flight requests.');
+        console.log('This disconnects the node from +Ai and cancels any in-flight requests.');
+        console.log((0, unpair_1.describeDisconnect)(0));
         console.log('Re-run with --yes to confirm.');
         return;
     }
-    try {
-        const r = await (0, supabase_client_1.rpc)('runtime_self_unpair', { p_token: token() });
-        if (r?.cancelled_requests) {
-            console.log(`Cancelled ${r.cancelled_requests} in-flight request(s).`);
-        }
-    }
-    catch (err) {
-        console.error(`server unpair failed (continuing with local cleanup): ${err.message}`);
-    }
-    (0, store_1.clearPairing)();
-    console.log('Unpaired. Run `ainode` to pair again.');
+    const r = await (0, unpair_1.disconnectNode)();
+    console.log((0, unpair_1.summariseDisconnect)(r));
+    if (!r.ok)
+        process.exit(1);
+    console.log('Run `ainode` to pair again.');
 }
 function cmdStartup() {
     const sub = args[1] ?? 'status';
@@ -128,7 +124,10 @@ function cmdStartup() {
 }
 async function main() {
     const cmd = args[0];
-    if (!cmd || cmd === 'run' || cmd === 'start' || cmd === '--run') {
+    // `entities` is the same run command with a destination attached: the page
+    // that printed it knows which product this machine is joining, so the user
+    // never gets asked. An already-paired node ignores it and just runs.
+    if (!cmd || cmd === 'run' || cmd === 'start' || cmd === '--run' || cmd === 'entities') {
         // `--ensure` means "make sure a node is running here, then get out of the
         // way". Windows' startup task repeats every five minutes to catch a
         // crashed daemon; without this it would stack a second one every time.
@@ -158,11 +157,9 @@ async function main() {
             });
             return;
         }
-        const runtime = await (0, index_1.start)();
+        const runtime = await (0, index_1.start)(args);
         if (!tui) {
             console.log(`ainode v${index_1.VERSION} running (pid ${runtime.pid}, port ${runtime.port})`);
-            if (!(0, store_1.isPaired)())
-                console.log('Not paired yet — pairing flow comes online in the next build.');
             await new Promise(() => { });
             return;
         }
@@ -192,23 +189,24 @@ async function main() {
         case 'help':
         case '--help':
         case '-h':
-            console.log(`ainode v${index_1.VERSION}
-
-usage:
-  ainode                    run this +Ai Node — daemon + live dashboard
-  ainode harnesses          install / log in agent harnesses (interactive)
-  ainode startup enable     start this node whenever you log in
-  ainode startup disable    stop starting at login
-  ainode startup status     where the startup entry is and what it runs
-  ainode unpair --yes       disconnect from +Ai
-  ainode version            print version
-
-Piped or headless output falls back to plain log lines. Set AINODE_NO_TUI=1
-to force that on a terminal. \`ainode run --ensure\` starts a node only if one
-isn't already running — what the Windows startup task uses.
-
-Pair the node by running it with no args and following the prompt
-to vault.add.ai/entity/connect/<CODE>.
+            console.log(`ainode v${index_1.VERSION}
+
+usage:
+  ainode                    run this +Ai Node — daemon + live dashboard
+  ainode entities           the same, but pair into +Ai Entities
+  ainode harnesses          install / log in agent harnesses (interactive)
+  ainode startup enable     start this node whenever you log in
+  ainode startup disable    stop starting at login
+  ainode startup status     where the startup entry is and what it runs
+  ainode unpair --yes       disconnect from +Ai
+  ainode version            print version
+
+Piped or headless output falls back to plain log lines. Set AINODE_NO_TUI=1
+to force that on a terminal. \`ainode run --ensure\` starts a node only if one
+isn't already running — what the Windows startup task uses.
+
+Pairing opens your browser to confirm the machine; nothing to type. Over SSH
+or on a headless box it prints a code and a link instead.
 `);
             return;
     }

package/dist/config.d.ts

@@ -1,6 +1,7 @@
 export declare const SUPABASE_URL = "https://syhzpqqvrplaqdipcymw.supabase.co";
 export declare const SUPABASE_ANON_KEY: string;
 export declare const VAULT_PAIR_URL = "https://vault.add.ai/add/entity";
+export declare const ENTITIES_PAIR_URL = "https://entities.add.ai/connect";
 export declare const HEARTBEAT_INTERVAL_MS = 30000;
 export declare const HANG_WATCHDOG_IDLE_MS: number;
 export declare const PAIR_POLL_INTERVAL_MS = 2000;

package/dist/config.js

@@ -3,7 +3,7 @@
 // public (PostgREST anon role only sees what RLS permits), so it's fine
 // to ship in the npm package.
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.PAIR_TIMEOUT_MS = exports.PAIR_POLL_INTERVAL_MS = exports.HANG_WATCHDOG_IDLE_MS = exports.HEARTBEAT_INTERVAL_MS = exports.VAULT_PAIR_URL = exports.SUPABASE_ANON_KEY = exports.SUPABASE_URL = void 0;
+exports.PAIR_TIMEOUT_MS = exports.PAIR_POLL_INTERVAL_MS = exports.HANG_WATCHDOG_IDLE_MS = exports.HEARTBEAT_INTERVAL_MS = exports.ENTITIES_PAIR_URL = exports.VAULT_PAIR_URL = exports.SUPABASE_ANON_KEY = exports.SUPABASE_URL = void 0;
 exports.SUPABASE_URL = 'https://syhzpqqvrplaqdipcymw.supabase.co';
 // Legacy anon JWT for the +Ai Project. Used by the daemon for every RPC
 // call; per-runtime authentication happens inside each RPC via the
@@ -16,6 +16,11 @@ exports.SUPABASE_ANON_KEY = 'eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.' +
 // Entity provider pre-selected and the code pre-filled. Vault's
 // LegacyRedirect prepends the user's default workspace slug.
 exports.VAULT_PAIR_URL = 'https://vault.add.ai/add/entity';
+// Where `ainode entities` sends you instead: Entity Studio's own confirm
+// page. It takes the code on the end of the path, is workspace-less (this
+// machine has no idea which workspace its human is in), and shows the
+// hostname before it attaches anything.
+exports.ENTITIES_PAIR_URL = 'https://entities.add.ai/connect';
 // Heartbeat interval. Picked so the desktop can mark a runtime offline
 // after ~2x missed heartbeats (~60s) without too much chatty traffic.
 exports.HEARTBEAT_INTERVAL_MS = 30_000;
@@ -24,8 +29,18 @@ exports.HEARTBEAT_INTERVAL_MS = 30_000;
 // Deliberately generous: a legit slow tool call (e.g. grok kicking off an
 // image/video flow, which emits no intermediate events) must complete inside
 // this window or a false kill would waste the run. 8 min clears typical flows
-// while still firing well before the 1h node-timeout ceiling and the 10-min
-// server watchdog's hard fail. Override with HANG_WATCHDOG_IDLE_MS (0 = off).
+// while still firing well before the 1h node-timeout ceiling.
+//
+// The ordering that matters: this leash must fire BEFORE the server gives up on
+// the run, or the server's guess wins and the user gets a failure for a run that
+// is still working. A run that has shown activity gets 3x this window (see the
+// idleMsFn call sites in session-runner), so the real node budget is 24 min —
+// which for a long time was more than DOUBLE the server's 10-minute verdict, and
+// is exactly why chats showed "No response from the entity in time" while the
+// agent was mid-turn. The server now measures liveness from the per-run
+// heartbeat instead of guessing, with a 30-min silence ceiling as its backstop:
+// 24 < 30, so this leash gets to decide. Keep it that way if either changes.
+// Override with HANG_WATCHDOG_IDLE_MS (0 = off).
 exports.HANG_WATCHDOG_IDLE_MS = (() => {
     const raw = process.env.HANG_WATCHDOG_IDLE_MS;
     if (raw == null || raw === '')

package/dist/heartbeat.js

@@ -11,6 +11,7 @@ exports.stop = stop;
 const supabase_client_1 = require("./supabase-client");
 const store_1 = require("./store");
 const capabilities_1 = require("./capabilities");
+const request_pump_1 = require("./request-pump");
 const config_1 = require("./config");
 let timer = null;
 let stopped = false;
@@ -78,6 +79,45 @@ async function goOffline() {
 async function beat() {
     await tick();
 }
+// ── Per-run liveness ────────────────────────────────────────────────────────
+// Tells the server which runs this daemon is holding a child process for. The
+// server's watchdog used to infer that from rows in entity_runtime_request_events
+// — i.e. from how CHATTY the agent was — and so failed runs that were alive but
+// quiet: a grok turn routinely goes ten minutes between its last streamed token
+// and turn_complete, and users were told "No response from the entity in time —
+// it may be offline" under an answer that had already been delivered.
+//
+// Deliberately its OWN timer rather than a line inside tick(): tick() runs a
+// capabilities probe that spawns agent CLIs and can be slow or throw, and
+// liveness reporting must not be starved by it. Sent even when nothing is
+// in-flight — the empty call is what tells the server this build claims its
+// runs at all, so a node rolled back to an older build ages out of the strict
+// rule by itself.
+let runTimer = null;
+let lastRunBeatError = '';
+async function runTick() {
+    if (stopped || (0, supabase_client_1.rpcShouldSkip)())
+        return;
+    const pairing = (0, store_1.readPairing)();
+    if (!pairing)
+        return;
+    try {
+        await (0, supabase_client_1.rpc)('runtime_request_heartbeat', {
+            p_token: pairing.daemonToken,
+            p_request_ids: (0, request_pump_1.activeRequestIdList)(),
+        });
+        lastRunBeatError = '';
+    }
+    catch (err) {
+        // Soft fail, deduped: a server without this RPC yet (or a blip) must not
+        // produce a log line every 30 seconds forever.
+        const msg = err.message || String(err);
+        if (msg !== lastRunBeatError) {
+            lastRunBeatError = msg;
+            console.error('[heartbeat] run heartbeat failed:', msg);
+        }
+    }
+}
 function start() {
     if (timer || stopped)
         return;
@@ -85,6 +125,8 @@ function start() {
     // 30s for the first interval.
     void tick();
     timer = setInterval(() => { void tick(); }, config_1.HEARTBEAT_INTERVAL_MS);
+    void runTick();
+    runTimer = setInterval(() => { void runTick(); }, config_1.HEARTBEAT_INTERVAL_MS);
 }
 function stop() {
     stopped = true;
@@ -92,4 +134,8 @@ function stop() {
         clearInterval(timer);
         timer = null;
     }
+    if (runTimer) {
+        clearInterval(runTimer);
+        runTimer = null;
+    }
 }

package/dist/index.d.ts

@@ -6,7 +6,11 @@ export interface RunningRuntime {
 }
 /**
  * Boot the daemon. If we don't have a pairing yet, run the user through
- * the 5-letter code flow first; once paired, kick off the heartbeat.
+ * pairing first; once paired, kick off the heartbeat.
+ *
+ * `argv` is passed through only so pairing knows which product this machine
+ * is joining — `ainode entities` lands on Entity Studio, everything else on
+ * Vault. An already-paired daemon never looks at it.
  */
-export declare function start(): Promise<RunningRuntime>;
+export declare function start(argv?: string[]): Promise<RunningRuntime>;
 export { VERSION };

package/dist/index.js

@@ -90,9 +90,13 @@ process.on('unhandledRejection', (reason) => {
 });
 /**
  * Boot the daemon. If we don't have a pairing yet, run the user through
- * the 5-letter code flow first; once paired, kick off the heartbeat.
+ * pairing first; once paired, kick off the heartbeat.
+ *
+ * `argv` is passed through only so pairing knows which product this machine
+ * is joining — `ainode entities` lands on Entity Studio, everything else on
+ * Vault. An already-paired daemon never looks at it.
  */
-async function start() {
+async function start(argv = []) {
     const migration = (0, state_migrate_1.migrateLegacyStateDir)();
     if (migration.migrated) {
         const parts = [
@@ -125,11 +129,7 @@ async function start() {
     }
     if (!(0, store_1.isPaired)()) {
         try {
-            const code = await (0, pairing_1.requestPairCode)();
-            (0, pairing_1.printPairingInstructions)(code);
-            const result = await (0, pairing_1.awaitPairing)(code);
-            console.log(`  ✓ Paired (runtime_id: ${result.runtime_id})`);
-            console.log('');
+            await (0, pairing_1.runPairing)(argv);
         }
         catch (err) {
             console.error('Pairing failed:', err.message || err);

package/dist/open-browser.d.ts

@@ -0,0 +1 @@
+export declare function openBrowser(url: string, platform?: NodeJS.Platform): boolean;