@nopeek/agent-bridge 0.7.6 → 0.7.8

package/dist/backends.js

@@ -15,7 +15,7 @@ import { spawn, spawnSync } from "node:child_process";
 import { createHash } from "node:crypto";
 import { copyFileSync, existsSync, mkdirSync, readFileSync, symlinkSync, writeFileSync } from "node:fs";
 import { homedir } from "node:os";
-import { join } from "node:path";
+import { basename, join } from "node:path";
 import { stripAnsi } from "./brain.js";
 const BRAIN_UNREACHABLE = "⚠️ I couldn't reach my brain just now — please try again in a moment.";
 // ------------------------------------------------------------------ souls ----
@@ -139,19 +139,31 @@ function runClaudeOnce(bin, args, text, cwd, timeoutMs, tag, onDelta) {
                 console.error(`${tag} stderr: ${stderr.slice(0, 1000)}`);
             resolvePromise({ reply, exitCode });
         };
-        const timer = setTimeout(() => {
-            console.error(`${tag} timed out after ${timeoutMs / 1000}s, killing`);
-            child.kill("SIGKILL");
-            finish(null);
-        }, timeoutMs);
+        // IDLE timeout (see the identical fix in the hermes runOnce() above): reset
+        // on every byte of output so a genuinely agentic, tool-using turn can run as
+        // long as it keeps producing output, and only true silence kills it.
+        let timer;
+        const armIdleTimer = () => {
+            clearTimeout(timer);
+            timer = setTimeout(() => {
+                console.error(`${tag} idle ${timeoutMs / 1000}s (no output), killing`);
+                child.kill("SIGKILL");
+                finish(null);
+            }, timeoutMs);
+        };
+        armIdleTimer();
         child.stdout.on("data", (d) => {
+            armIdleTimer();
             lineBuf += d.toString();
             const lines = lineBuf.split("\n");
             lineBuf = lines.pop() ?? "";
             for (const line of lines)
                 handleLine(line);
         });
-        child.stderr.on("data", (d) => (stderr += d.toString()));
+        child.stderr.on("data", (d) => {
+            armIdleTimer();
+            stderr += d.toString();
+        });
         child.on("error", (err) => {
             clearTimeout(timer);
             console.error(`${tag} spawn error: ${err.message}`);
@@ -307,17 +319,54 @@ const HERMES_NO_SESSION = /^No session found matching/i;
 /** Session footer Hermes prints on exit; we filter it as chrome but capture
  *  the id so a fresh session can be renamed for future --continue. */
 const HERMES_SESSION_ID = /^session(_| )?id:\s*(\S+)/i;
+/**
+ * How this Hermes CLI selects a profile. Hermes ≥ v0.14 DROPPED the global
+ * `--profile <path>` flag (profiles are now named, selected via the
+ * HERMES_PROFILE env var); passing the old flag makes it exit 2 with an
+ * argparse usage error and NO stdout — which surfaced to users as a bot that
+ * "stopped responding" (the empty reply fell through to BRAIN_UNREACHABLE).
+ * Detected once per process from `hermes --help`, then cached.
+ *   "env"  → HERMES_PROFILE=<name>   (v0.14+)
+ *   "flag" → --profile <path>        (legacy)
+ */
+let hermesProfileMode = null;
+function detectHermesProfileMode(bin) {
+    if (hermesProfileMode)
+        return hermesProfileMode;
+    try {
+        const r = spawnSync(bin, ["--help"], {
+            encoding: "utf8",
+            timeout: 20_000,
+            env: { ...process.env, HOME: hermesHome() },
+        });
+        const help = `${r.stdout || ""}${r.stderr || ""}`;
+        // Only the legacy CLI advertises a global --profile option.
+        hermesProfileMode = /^\s*--profile\b|\[--profile\b/m.test(help) ? "flag" : "env";
+    }
+    catch {
+        hermesProfileMode = "env"; // current CLI is the safer default
+    }
+    console.log(`[hermes] profile selection mode: ${hermesProfileMode}`);
+    return hermesProfileMode;
+}
 export function hermesBrain(cfg) {
     const runOnce = (profile, text, sessionName, tag, onChunk) => new Promise((resolvePromise) => {
         const bin = resolveBin("hermes", "HERMES_BIN");
-        const args = ["--profile", profile, "chat", "-Q"];
+        const mode = detectHermesProfileMode(bin);
+        // v0.14+ takes the profile NAME via env; legacy took the PATH via flag.
+        const profileName = basename(profile);
+        const args = mode === "flag" ? ["--profile", profile, "chat", "-Q"] : ["chat", "-Q"];
         if (sessionName)
             args.push("--continue", sessionName);
         args.push("-q", text);
         const child = spawn(bin, args, {
             stdio: ["ignore", "pipe", "pipe"],
             // Hermes keys everything off $HOME; point it at the Hermes install.
-            env: { ...process.env, HOME: hermesHome() },
+            env: {
+                ...process.env,
+                HOME: hermesHome(),
+                ...(mode === "env" ? { HERMES_PROFILE: profileName } : {}),
+            },
         });
         let out = "";
         let lineBuf = "";
@@ -384,20 +433,35 @@ export function hermesBrain(cfg) {
                 noSession = true;
             resolvePromise({ reply: out.trim(), noSession, sessionId, stderr, timedOut });
         };
-        const timer = setTimeout(() => {
-            console.error(`${tag} timed out after ${cfg.brainTimeoutMs / 1000}s, killing`);
-            timedOut = true;
-            child.kill("SIGKILL");
-            finish();
-        }, cfg.brainTimeoutMs);
+        // IDLE timeout, not a flat wall-clock one: reset on every byte of output
+        // (stdout OR stderr — either is a sign the process is alive and working,
+        // not hung). A genuinely agentic turn (tool use, indexing a fresh repo on
+        // a brand-new profile) can legitimately run for minutes while still
+        // producing periodic status output — a flat timer kills that productive
+        // work indiscriminately. Only true SILENCE this long means hung.
+        let timer;
+        const armIdleTimer = () => {
+            clearTimeout(timer);
+            timer = setTimeout(() => {
+                console.error(`${tag} idle ${cfg.brainTimeoutMs / 1000}s (no output), killing`);
+                timedOut = true;
+                child.kill("SIGKILL");
+                finish();
+            }, cfg.brainTimeoutMs);
+        };
+        armIdleTimer();
         child.stdout.on("data", (d) => {
+            armIdleTimer();
             lineBuf += d.toString();
             const lines = lineBuf.split("\n");
             lineBuf = lines.pop() ?? "";
             for (const line of lines)
                 handleLine(line);
         });
-        child.stderr.on("data", (d) => (stderr += d.toString()));
+        child.stderr.on("data", (d) => {
+            armIdleTimer();
+            stderr += d.toString();
+        });
         child.on("error", (err) => {
             clearTimeout(timer);
             console.error(`${tag} spawn error: ${err.message}`);
@@ -435,9 +499,16 @@ export function hermesBrain(cfg) {
             run = await runOnce(profile, text, null, tag, onChunk);
             if (run.sessionId) {
                 const bin = resolveBin("hermes", "HERMES_BIN");
-                const rn = spawn(bin, ["--profile", profile, "sessions", "rename", run.sessionId, sessionName], {
+                const mode = detectHermesProfileMode(bin);
+                const rn = spawn(bin, mode === "flag"
+                    ? ["--profile", profile, "sessions", "rename", run.sessionId, sessionName]
+                    : ["sessions", "rename", run.sessionId, sessionName], {
                     stdio: "ignore",
-                    env: { ...process.env, HOME: hermesHome() },
+                    env: {
+                        ...process.env,
+                        HOME: hermesHome(),
+                        ...(mode === "env" ? { HERMES_PROFILE: basename(profile) } : {}),
+                    },
                 });
                 rn.on("error", () => {
                     /* best-effort — worst case the next message starts fresh again */
@@ -456,9 +527,21 @@ export function hermesBrain(cfg) {
             // start), which misdirects the user to run a command that isn't the fix.
             if (run.timedOut) {
                 const secs = Math.round(cfg.brainTimeoutMs / 1000);
-                return `⚠️ My brain took longer than ${secs}s to respond and I had to give up — this can happen on the very first message while a session/provider is warming up. Try messaging me again.`;
+                return `⚠️ My brain went quiet for over ${secs}s with no output and I had to give up on that turn — a long tool-use step or a very slow provider response can trigger this. Try messaging me again.`;
+            }
+            // Surface the REAL reason. Blaming "no authenticated provider" for every
+            // empty reply hid a CLI-flag incompatibility (Hermes v0.14 dropped
+            // --profile) for a full day: the bot kept answering "run hermes model",
+            // which was not the fix and sent debugging down the wrong path.
+            const err = run.stderr.trim();
+            if (/usage: hermes|invalid choice|unrecognized arguments/i.test(err)) {
+                return "⚠️ My brain couldn't start — the Hermes CLI on the host rejected the command (its options changed). The bridge needs updating: run `npm i -g @nopeek/agent-bridge@latest` on that computer.";
+            }
+            if (err) {
+                const first = err.split("\n").find((l) => l.trim()) ?? "";
+                return `⚠️ My brain returned no answer. Host reported: ${first.slice(0, 180)}`;
             }
-            return "⚠️ My brain isn't reachable right now — Hermes has no authenticated provider on the host. Run 'hermes model' there, then message me again.";
+            return "⚠️ My brain isn't reachable right now — Hermes returned nothing. Check `hermes status` / `hermes model` on the host, then message me again.";
         }
         return run.reply;
     };

package/dist/bridge.d.ts

@@ -1,5 +1,5 @@
 import type { BridgeConfig, Pairing, BrainSpec, BrainBackend } from "./config.js";
-export declare const VERSION = "0.7.6";
+export declare const VERSION = "0.7.8";
 export interface PairRequest {
     pairingSecret: string;
     appId: string;

package/dist/bridge.js

@@ -17,7 +17,7 @@ import { resolveBrain } from "./brain.js";
 import { provisionSoul, provisionHermesProfile } from "./backends.js";
 import { reportCapabilities } from "./capabilities.js";
 import { isBrainBackend } from "./config.js";
-export const VERSION = "0.7.6";
+export const VERSION = "0.7.8";
 /** How often to re-probe + report brain availability to the server. */
 const CAPABILITIES_INTERVAL_MS = 5 * 60_000;
 // ---- Reconnect watchdog -----------------------------------------------------

package/dist/config.d.ts

@@ -82,9 +82,9 @@ export interface BridgeConfig {
 export declare const DEFAULT_API_URL = "https://d3qweh72vesa98.cloudfront.net";
 export declare const DEFAULT_APP_URL = "https://d32w3to73s0pu5.cloudfront.net/messenger/";
 export declare const DEFAULT_PORT = 8790;
-export declare const DEFAULT_BRAIN_TIMEOUT_MS = 180000;
+export declare const DEFAULT_BRAIN_TIMEOUT_MS = 300000;
 export declare function defaultHomeDir(): string;
-export declare const HELP = "nopeek-agent-bridge \u2014 run your agents as E2EE NoPeek bots\n\nUsage:\n  nopeek-agent-bridge install     Install as a background service (launchd/systemd),\n                                  then finish setup from the NoPeek app:\n                                  Bots -> Connect this computer.\n  nopeek-agent-bridge uninstall   Remove the background service (keeps data/settings).\n  nopeek-agent-bridge status      Show the running bridge's status.\n  nopeek-agent-bridge [run]       Run in the foreground. Unpaired bridges wait to be\n                                  paired from the NoPeek app; --pair still works:\n                                    npx @nopeek/agent-bridge --pair npr_\u2026 --app-id app_\u2026\n\nOptions:\n  --pair <code>            Pairing code from the NoPeek app             (env NOPEEK_PAIRING_CODE)\n  --app-id <id>            NoPeek app id                                (env NOPEEK_APP_ID)\n  --api-url <url>          API base, default https://d3qweh72vesa98.cloudfront.net  (env NOPEEK_API_URL)\n  --brain-cmd <cmd>        Shell brain: message on stdin -> reply on stdout   (env BRAIN_CMD)\n  --brain-url <url>        Webhook brain: POST {text,...} -> {text|reply}     (env BRAIN_URL)\n  --brain-map <json>       Per-bot overrides {\"<handle>\":{\"cmd\":\"\u2026\"}|{\"url\":\"\u2026\"}|\n                           {\"backend\":\"claude\"|\"hermes\"|\"echo\"}}              (env BRAIN_MAP)\n  --brain-provision-cmd <cmd>  Run once per new bot; stdout becomes its brain command\n                           (env BRAIN_PROVISION_CMD \u2014 e.g. a script that creates a\n                           fresh Hermes profile with its own soul + memory)\n  --app-url <url>          App opened after install                     (env NOPEEK_APP_URL)\n  --no-open                install: don't open the app in the browser\n  --brain-timeout-ms <ms>  Brain timeout, default 180000          (env BRAIN_TIMEOUT_MS)\n  --port <port>            Local control API port, default 8790    (env NOPEEK_BRIDGE_PORT)\n  --data-dir <dir>         Device-key store dir                        (env NOPEEK_BRIDGE_DATA_DIR)\n  --home <dir>             Bridge home, default ~/.nopeek-bridge       (env NOPEEK_BRIDGE_HOME)\n  --config <path>          Config file, default ./nopeek-bridge.config.json\n  -h, --help               Show this help\n\nWith no brain configured, bots run in echo mode (\"You said: \u2026\") \u2014 a zero-config smoke test.\nPairing and brains can be managed entirely from the NoPeek app once the service is running.";
+export declare const HELP = "nopeek-agent-bridge \u2014 run your agents as E2EE NoPeek bots\n\nUsage:\n  nopeek-agent-bridge install     Install as a background service (launchd/systemd),\n                                  then finish setup from the NoPeek app:\n                                  Bots -> Connect this computer.\n  nopeek-agent-bridge uninstall   Remove the background service (keeps data/settings).\n  nopeek-agent-bridge status      Show the running bridge's status.\n  nopeek-agent-bridge [run]       Run in the foreground. Unpaired bridges wait to be\n                                  paired from the NoPeek app; --pair still works:\n                                    npx @nopeek/agent-bridge --pair npr_\u2026 --app-id app_\u2026\n\nOptions:\n  --pair <code>            Pairing code from the NoPeek app             (env NOPEEK_PAIRING_CODE)\n  --app-id <id>            NoPeek app id                                (env NOPEEK_APP_ID)\n  --api-url <url>          API base, default https://d3qweh72vesa98.cloudfront.net  (env NOPEEK_API_URL)\n  --brain-cmd <cmd>        Shell brain: message on stdin -> reply on stdout   (env BRAIN_CMD)\n  --brain-url <url>        Webhook brain: POST {text,...} -> {text|reply}     (env BRAIN_URL)\n  --brain-map <json>       Per-bot overrides {\"<handle>\":{\"cmd\":\"\u2026\"}|{\"url\":\"\u2026\"}|\n                           {\"backend\":\"claude\"|\"hermes\"|\"echo\"}}              (env BRAIN_MAP)\n  --brain-provision-cmd <cmd>  Run once per new bot; stdout becomes its brain command\n                           (env BRAIN_PROVISION_CMD \u2014 e.g. a script that creates a\n                           fresh Hermes profile with its own soul + memory)\n  --app-url <url>          App opened after install                     (env NOPEEK_APP_URL)\n  --no-open                install: don't open the app in the browser\n  --brain-timeout-ms <ms>  Brain timeout, default 300000          (env BRAIN_TIMEOUT_MS)\n  --port <port>            Local control API port, default 8790    (env NOPEEK_BRIDGE_PORT)\n  --data-dir <dir>         Device-key store dir                        (env NOPEEK_BRIDGE_DATA_DIR)\n  --home <dir>             Bridge home, default ~/.nopeek-bridge       (env NOPEEK_BRIDGE_HOME)\n  --config <path>          Config file, default ./nopeek-bridge.config.json\n  -h, --help               Show this help\n\nWith no brain configured, bots run in echo mode (\"You said: \u2026\") \u2014 a zero-config smoke test.\nPairing and brains can be managed entirely from the NoPeek app once the service is running.";
 /** Load config from argv + env + cwd config file + home settings. Never
  *  requires pairing — an unpaired bridge waits for the app to pair it. */
 export declare function loadConfig(argv?: string[]): BridgeConfig;

package/dist/config.js

@@ -15,7 +15,12 @@ export function isBrainBackend(v) {
 export const DEFAULT_API_URL = "https://d3qweh72vesa98.cloudfront.net";
 export const DEFAULT_APP_URL = "https://d32w3to73s0pu5.cloudfront.net/messenger/";
 export const DEFAULT_PORT = 8790;
-export const DEFAULT_BRAIN_TIMEOUT_MS = 180_000;
+// Idle timeout (resets on any child-process output, not a flat wall-clock cap
+// — see backends.ts). 300s of true SILENCE covers a long tool-use step (repo
+// indexing, slow provider call) on a genuinely agentic brain without needing
+// per-deployment tuning, while still killing a truly hung process reasonably
+// fast.
+export const DEFAULT_BRAIN_TIMEOUT_MS = 300_000;
 export function defaultHomeDir() {
     return process.env.NOPEEK_BRIDGE_HOME || join(homedir(), ".nopeek-bridge");
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nopeek/agent-bridge",
-  "version": "0.7.6",
+  "version": "0.7.8",
   "description": "Run your own agents as E2EE NoPeek bots. Pairs with one-time codes (multiple accounts per computer), runs every bot each account owns, and pipes messages to any command or webhook.",
   "type": "module",
   "license": "MIT",