agent-dag 1.30.7 → 1.30.8

package/README.md

@@ -27,6 +27,7 @@ No config. No install step. Ctrl+C to stop.
 - **Persistent replay** — events survive restarts; the log at `~/.claude/agent-dag/events.jsonl` replays the last session on open
 - **Workspace filter** — `--scope` limits capture to the current directory; `--workspace <path>` for any subtree
 - **Zero trust step for Codex** — no hook install, no `/hooks` trust prompt; the server tails `~/.codex/sessions/` directly
+- **Version drift warning** — Node caches modules at startup, so a deck upgraded while running keeps executing the old code. The topbar says so, and points at the restart or the upgrade command
 
 ## How it works
 
@@ -62,6 +63,22 @@ agents-deck [options]
   -h, --help               Show this help
 ```
 
+Environment:
+
+```
+AGENT_DAG_PORT               Default port, same as -p
+CODEX_HOME                   Override ~/.codex
+AGENTS_DECK_NO_INSTALL=1     Never install or update claude-swap / ccusage,
+                             and don't ask npm about newer agents-deck releases
+AGENTS_DECK_NO_UPDATE_CHECK=1  Don't ask npm about releases, but keep everything else
+AGENTS_DECK_NO_FRESHEN=1     Never nudge claude-swap to collect usage early
+```
+
+The update check is one ~20-byte GET to `registry.npmjs.org`, at most once a day,
+and it never installs anything. Being told to restart after an upgrade is local
+only — no network involved — and cannot be turned off, because a deck running
+superseded code is a bug you cannot see any other way.
+
 ## Uninstall
 
 ```bash

package/bin/agent-dag.js

@@ -201,6 +201,24 @@ if (process.env.AGENTS_DECK_NO_INSTALL !== "1") {
   else if (cu.state === "installing") process.stdout.write(`  ${C.green}✓${C.reset} ccusage          ${C.dim}installing in background${C.reset}\n`);
 }
 
+// A newer release on npm, said once, in the place the upgrade gets typed.
+// Started here and collected below so the lookup overlaps the rest of boot, and
+// hard-capped so a slow registry cannot delay the server — the answer is
+// usually already cached in ~/.agents-deck/.self-update-check anyway. It has to
+// resolve BEFORE the pulse indicator starts writing over the last line.
+const selfCheck = import(pathToFileURL(join(PKG_ROOT, "src/server/self-update.mjs")).href)
+  .then(m => m.versionReport({ running: PKG_VERSION, pkgRoot: PKG_ROOT }))
+  .catch(() => null);
+const upgrade = await Promise.race([
+  selfCheck.then(r => r?.notice?.kind === "upgrade" ? r : null),
+  new Promise(r => setTimeout(() => r(null), 1200)),
+]);
+if (upgrade) {
+  process.stdout.write(
+    `  ${C.yellow}↑${C.reset} update           ${C.dim}v${upgrade.notice.to} available — ${C.reset}${C.yellow}${upgrade.command}${C.reset}\n`,
+  );
+}
+
 sp = spinner("starting server…");
 const server = await startServer({ port, persist, workspace, codex: wantCodex }).catch(err => {
   sp.stop(false, `server failed: ${err.message}`);