lattice-talk 0.1.4 → 0.1.6

package/README.md

@@ -90,20 +90,34 @@ Run `lattice-talk bridge gemini` to spawn a Gemini agent into your configured wo
 | Codex | `codex app-server` — injects into an in-flight turn via `turn/steer` |
 | Windsurf | Not supported — Windsurf has no public programmatic session API |
 
-Two things to know about the bridge: the harness CLI must be installed and logged in on the machine running the bridge, and bridged sessions auto-approve tool permissions so the agent can work unattended — run it with the same trust you'd give a `--dangerously-skip-permissions` session.
+Two things to know about the bridge: the harness CLI must be installed and logged in on the machine running the bridge (for Claude the bridge downloads the `claude-code-acp` adapter via `npx` on first run), and bridged sessions auto-approve tool permissions so the agent can work unattended — run it with the same trust you'd give a `--dangerously-skip-permissions` session.
 
 **Windsurf** stays on the MCP path: `mcp add windsurf` gives its agents `pull_messages` with `wait_ms`, which still wakes them the instant a message is published — it just requires the agent to ask.
 
+### Which delivery should I use?
+
+- **`mcp add`** — every harness, any agent you run yourself. Near-instant delivery via wake-up polling.
+- **`bridge`** — when you want an agent that receives messages *without asking*, e.g. an always-on coordinator or a reviewer you want to react to every message immediately.
+
+Both can run side by side on the same workspace.
+
 ## Requirements
 
 | Requirement | Needed for |
 | --- | --- |
-| Node.js 20+ | The MCP server (`serve`) that harnesses run |
+| Node.js 20+ | The MCP server (`serve`) and the bridge |
 | Redis | Sharing messages between agent processes — local, Docker, remote, or managed |
 | Bun, or Node.js 26.4+ | The interactive dashboard (OpenTUI renders via native FFI) |
+| The harness CLI (`claude`, `codex`, `gemini`, or `agent`) | `lattice-talk bridge` for that harness — installed and logged in |
 
 The dashboard auto-detects a compatible runtime and tells you clearly if none is found. The MCP server itself needs only plain Node 20+.
 
+**Terminal compatibility** — the dashboard adapts to what your terminal can render:
+
+- Truecolor terminals (Windows Terminal, iTerm2, VS Code, most modern emulators) get the full palette.
+- ANSI-16 terminals (legacy `conhost.exe`, Terminal.app, Linux console) automatically get a high-contrast named-color palette and, where needed, ASCII-only glyphs (`->`, `ret`, `u/d`) instead of Unicode.
+- `NO_COLOR=1` forces a monochrome look; `LATTICE_ASCII=1` forces ASCII glyphs (useful over SSH/tmux or inside screen readers).
+
 ## Configuration
 
 Setup writes user-level settings to `~/.lattice/config.json` (restricted permissions; override the location with `LATTICE_CONFIG_PATH`). Environment variables always win over saved values.
@@ -136,6 +150,8 @@ Don't paste passwords, API keys, or secrets into messages or shared memory.
 
 **Dashboard won't open** — install Bun, or Node.js 26.4+. `serve` still works on Node 20+.
 
+**Dashboard opens but looks wrong** — garbled icons or washed-out colors on an old terminal mean the capability detection missed. Try `LATTICE_ASCII=1` for plain-ASCII glyphs, or set `COLORTERM=truecolor` if your terminal does support 24-bit color. `NO_COLOR=1` gives a clean monochrome UI.
+
 **Agents can't see each other** — confirm every harness uses the same Redis, namespace, and workspace name, and the same `LATTICE_JOIN_TOKEN` if the workspace is protected. Restart the harness after changing MCP config.
 
 **A room is empty** — the agent hasn't joined it. Press `p` on the room, paste the prompt into that agent's session; it will join the workspace and room.

package/dist/index.js

@@ -21086,7 +21086,7 @@ init_esm_shims();
 // package.json
 var package_default = {
   name: "lattice-talk",
-  version: "0.1.4",
+  version: "0.1.6",
   description: "Lattice \u2014 Cross-Harness MCP Session Bus. Shared sessions, DMs, rooms, memory, and OpenTelemetry for agents across Claude Code, Cursor, Codex, and custom harnesses.",
   type: "module",
   main: "./dist/index.js",
@@ -22442,11 +22442,17 @@ var NdjsonRpc = class {
       const errRl = createInterface({ input: this.proc.stderr });
       errRl.on("line", (line) => opts.onStderr(line));
     }
-    this.proc.on("exit", (code) => {
+    const failAll = (err2) => {
       this.closed = true;
-      const err2 = new Error(`process exited with code ${code}`);
       for (const p of this.pending.values()) p.reject(err2);
       this.pending.clear();
+    };
+    this.proc.on("error", (e) => {
+      failAll(e);
+      opts.onExit?.(null);
+    });
+    this.proc.on("exit", (code) => {
+      failAll(new Error(`process exited with code ${code}`));
       opts.onExit?.(code);
     });
   }
@@ -22579,7 +22585,10 @@ var AcpDriver = class {
       env: opts.env,
       shell: this.shell,
       onStderr: (line) => onEvent(`[${this.id}] ${line}`),
-      onExit: (code) => onEvent(`[${this.id}] exited (code ${code ?? "?"})`)
+      onExit: (code) => {
+        onEvent(`[${this.id}] exited (code ${code ?? "?"})`);
+        opts.onExit?.(code);
+      }
     });
     this.rpc = rpc;
     rpc.onRequest("session/request_permission", (params) => {
@@ -22609,15 +22618,16 @@ var AcpDriver = class {
         if (text) onEvent(`[${this.id}] ${text}`);
       }
     });
-    const init = await rpc.request("initialize", {
-      protocolVersion: ACP_PROTOCOL_VERSION,
-      clientCapabilities: {
-        fs: { readTextFile: false, writeTextFile: false },
-        terminal: false
-      },
-      clientInfo: { name: "lattice-talk-bridge", version: "0" }
-    });
+    let init;
     try {
+      init = await rpc.request("initialize", {
+        protocolVersion: ACP_PROTOCOL_VERSION,
+        clientCapabilities: {
+          fs: { readTextFile: false, writeTextFile: false },
+          terminal: false
+        },
+        clientInfo: { name: "lattice-talk-bridge", version: "0" }
+      });
       const res = await rpc.request("session/new", {
         cwd: opts.cwd,
         mcpServers: opts.mcpServers.map(serializeMcpServer)
@@ -22685,7 +22695,10 @@ var CodexDriver = class {
       env: opts.env,
       shell: this.shell,
       onStderr: (line) => onEvent(`[codex] ${line}`),
-      onExit: (code) => onEvent(`[codex] exited (code ${code ?? "?"})`)
+      onExit: (code) => {
+        onEvent(`[codex] exited (code ${code ?? "?"})`);
+        opts.onExit?.(code);
+      }
     });
     this.rpc = rpc;
     rpc.onNotification("turn/started", (params) => {
@@ -22899,7 +22912,11 @@ async function runBridge(opts) {
       suggestedAgentId: opts.agentId,
       tokenProtected: Boolean(opts.conn.joinToken)
     }),
-    onEvent: log2
+    onEvent: log2,
+    onExit: (code) => {
+      log2(`[bridge] agent process exited (code ${code ?? "?"}) \u2014 shutting down.`);
+      stop.abort();
+    }
   });
   log2(`[bridge] ${opts.harness} session up \u2014 injecting room "${roomId}" traffic into it.`);
   if (bridgedAgentId) {
@@ -22922,13 +22939,15 @@ async function runBridge(opts) {
       }
     }
   );
+  await sweep();
   const sweepTimer = setInterval(() => void sweep(), SWEEP_MS);
-  const discoveryTimer = setTimeout(
-    () => log2(
-      "[bridge] still waiting for the agent to join the workspace \u2014 check that it ran join_session."
-    ),
-    DISCOVERY_TIMEOUT_MS
-  );
+  const discoveryTimer = setTimeout(() => {
+    if (!bridgedAgentId) {
+      log2(
+        "[bridge] still waiting for the agent to join the workspace \u2014 check that it ran join_session."
+      );
+    }
+  }, DISCOVERY_TIMEOUT_MS);
   const onSignal = () => stop.abort();
   process.on("SIGINT", onSignal);
   process.on("SIGTERM", onSignal);
@@ -58133,7 +58152,14 @@ async function runTui(tuiArgs) {
       err(`Failed to start TUI runtime (${runtime.cmd}): ${e.message}`);
       resolve(1);
     });
-    child.on("exit", (code) => resolve(code ?? 0));
+    child.on("exit", (code) => {
+      if (code !== null && code !== 0 && code !== 130) {
+        err(
+          "The TUI exited unexpectedly \u2014 this terminal may not support its native renderer (common on older Windows consoles and minimal terminal emulators). `lattice-talk serve` and the MCP tools still work on any terminal."
+        );
+      }
+      resolve(code ?? 0);
+    });
   });
 }
 function printMcpStatus() {