@addai/node 0.24.0 → 0.24.1

package/dist/claude-print.d.ts

@@ -13,6 +13,20 @@ export interface ClaudePrintInput {
     /** Restrict to a specific set of tools (claude only). null/undefined = inherit. */
     allowedTools?: string[];
 }
+/**
+ * The text to emit for one flushed block, given what came before.
+ *
+ * The final reply is rebuilt with string_agg(delta, '') — an empty join,
+ * because deltas are partial TOKENS and any separator between them would
+ * corrupt words mid-word. Correct within a block, wrong between them: the
+ * entity narrates, calls a tool, narrates again, and the two blocks own no
+ * whitespace of their own, so they arrive glued as "the chat tool.Let me".
+ * The boundary is known here and nowhere else, so it is marked here.
+ */
+export declare function blockDelta(text: string, opts: {
+    afterTool: boolean;
+    hadTextBefore: boolean;
+}): string;
 export interface ClaudePrintHandle {
     pid: number | undefined;
     sessionId: string | null;

package/dist/claude-print.js

@@ -5,11 +5,29 @@
 // our normalised RuntimeEvent shape, and resolves when the process exits.
 // No PTY needed — Claude detects non-TTY and runs headless.
 Object.defineProperty(exports, "__esModule", { value: true });
+exports.blockDelta = blockDelta;
 exports.lineToEvents = lineToEvents;
 exports.spawnClaudePrint = spawnClaudePrint;
 const child_process_1 = require("child_process");
 const claude_binary_1 = require("./claude-binary");
 const win_1 = require("./win");
+/**
+ * The text to emit for one flushed block, given what came before.
+ *
+ * The final reply is rebuilt with string_agg(delta, '') — an empty join,
+ * because deltas are partial TOKENS and any separator between them would
+ * corrupt words mid-word. Correct within a block, wrong between them: the
+ * entity narrates, calls a tool, narrates again, and the two blocks own no
+ * whitespace of their own, so they arrive glued as "the chat tool.Let me".
+ * The boundary is known here and nowhere else, so it is marked here.
+ */
+function blockDelta(text, opts) {
+    if (!opts.afterTool || !opts.hadTextBefore || !text.trim())
+        return text;
+    // Drop leading whitespace the model may already have supplied so a break
+    // is exactly one blank line, never two.
+    return `\n\n${text.replace(/^\s+/, '')}`;
+}
 /**
  * Parse one stream-json line into 0+ RuntimeEvents.
  *
@@ -190,6 +208,16 @@ function spawnClaudePrint(input) {
     let textBuf = '';
     let flushTimer = null;
     let sawDeltaThisMsg = false;
+    // Has any answer text been emitted for this run yet? The final reply is
+    // rebuilt by string_agg(delta, '') — an empty join, because deltas are
+    // partial TOKENS and any separator between them would corrupt words. That
+    // is right within a block and wrong between them: the model narrates, calls
+    // a tool, narrates again, and the two blocks arrive as separate messages
+    // with no whitespace of their own. Glued together they read
+    // "load the chat tool.Let me confirm". So the boundary is marked here,
+    // where it is actually known, rather than guessed at in SQL.
+    let emittedAnyText = false;
+    let blockBreakPending = false;
     // Thinking deltas (extended thinking) — coalesced lazily into 'thinking'
     // events; the chat relay renders them as a collapsed section.
     const THINK_FLUSH_MS = 700;
@@ -212,8 +240,11 @@ function spawnClaudePrint(input) {
             flushTimer = null;
         }
         if (textBuf) {
-            const t = textBuf;
+            let t = textBuf;
             textBuf = '';
+            t = blockDelta(t, { afterTool: blockBreakPending, hadTextBefore: emittedAnyText });
+            blockBreakPending = false;
+            emittedAnyText = true;
             emit({ type: 'assistant_text', delta: t });
         }
     };
@@ -258,6 +289,11 @@ function spawnClaudePrint(input) {
         // was seen for this message, in which case we keep the block (never lose text).
         if (partialStream && (type === 'assistant' || type === 'user' || type === 'result'))
             flushText();
+        // A tool result means the entity stopped talking to go and do something.
+        // Whatever it says next is a new paragraph, not a continuation of the
+        // sentence it was halfway through.
+        if (type === 'user')
+            blockBreakPending = true;
         const suppressText = partialStream && sawDeltaThisMsg && type === 'assistant';
         for (const ev of lineToEvents(parsed, suppressText))
             emit(ev);

package/dist/grok-spawn.js

@@ -161,11 +161,24 @@ function writeProjectMcpConfig(workingDirectory, servers) {
     }
     const lines = [];
     for (const s of usable) {
-        // Remote MCP servers. xAI documents [mcp_servers.<name>] with `url` and a
-        // `headers` inline table, so grok now gets them properly instead of the
-        // skip this used to do — a skip that was safe (better than emitting
-        // `command = "http"`, which grok would try to exec) but meant an entity
-        // running on grok silently had none of its remote servers.
+        // Remote MCP servers are BRIDGED through mcp-remote, because grok cannot
+        // speak HTTP MCP itself.
+        //
+        // Its bundled README documents `url` + a `headers` inline table, and this
+        // code used to emit exactly that. Measured against grok 1.0.3, that entry
+        // is SILENTLY IGNORED: in one run grok loaded ten stdio servers and skipped
+        // both url-based ones — ours and a pre-existing third-party entry — with no
+        // error for either. The docs describe a transport the binary does not have.
+        //
+        // That is why entities on grok lost every Connection the moment the
+        // registry moved from `npx` to `http`: the servers were simply not there,
+        // and grok reported it to the model as "(auth required)".
+        //
+        // mcp-remote is the standard stdio<->HTTP shim (grok's own README reaches
+        // for it in its Linear example) and it is verified working here. The cost
+        // is an npx start per remote server on grok runs only — the very cost the
+        // HTTP move removed for every other agent. Revisit when grok ships real
+        // remote-MCP support.
         //
         // Folder trust still gates repo-local config.toml servers, so the --trust
         // launch flag remains load-bearing for these entries to start at all.
@@ -175,15 +188,16 @@ function writeProjectMcpConfig(workingDirectory, servers) {
                 console.error(`[grok] MCP ${s.slug}: ${s.command} server has no URL — skipped`);
                 continue;
             }
+            // The bridge itself is shared — see AGENTS_WITHOUT_HTTP_MCP for which
+            // agents need it and the evidence for each.
+            const bridge = (0, mcp_headers_1.remoteMcpBridge)(url, s.env);
+            const bridged = (0, win_1.wrapMcpCommandForPlatform)(bridge.command, bridge.args);
             lines.push(`[mcp_servers.${tomlStr(s.slug)}]`);
-            lines.push(`url = ${tomlStr(url)}`);
-            const headers = Object.entries((0, mcp_headers_1.remoteMcpHeaders)(s.env));
-            if (headers.length > 0) {
-                const kv = headers.map(([k, v]) => `${tomlStr(k)} = ${tomlStr(v)}`).join(', ');
-                lines.push(`headers = { ${kv} }`);
-            }
+            lines.push(`command = ${tomlStr(bridged.command)}`);
+            lines.push(`args = [${bridged.args.map(tomlStr).join(', ')}]`);
             lines.push('enabled = true');
-            lines.push('startup_timeout_sec = 30');
+            // The first run on a machine downloads mcp-remote, which 30s does not cover.
+            lines.push('startup_timeout_sec = 90');
             lines.push('');
             continue;
         }

package/dist/mcp-headers.d.ts

@@ -13,3 +13,44 @@ export declare function remoteMcpUrl(args?: string[] | null): string | null;
  * and must never be sent as a header.
  */
 export declare function remoteMcpHeaders(env?: Record<string, string> | null): Record<string, string>;
+/**
+ * Which agents can actually open an HTTP MCP connection, measured against the
+ * real binaries rather than their documentation.
+ *
+ *   claude  YES  — proven in production; entities use these every day.
+ *   codex   YES  — `codex mcp list` shows a `url` entry under Url, enabled.
+ *   kimi    YES  — `kimi mcp list` prints "<slug> (http): <url>".
+ *   gemini  ?    — UNVERIFIED. The CLI on hand cannot authenticate at all
+ *                  ("no longer supported for Gemini Code Assist for
+ *                  individuals"), so its httpUrl handling was never observed
+ *                  connecting. No entity runs gemini today. If one ever does,
+ *                  verify before trusting it — this exact assumption is what
+ *                  cost us grok.
+ *   grok    NO   — grok 1.0.3 SILENTLY IGNORES url-based entries. In one run it
+ *                  loaded ten stdio servers and skipped every remote one, ours
+ *                  and a third party's, with no error, while its own bundled
+ *                  README documents `url` + `headers`. The docs describe a
+ *                  transport the binary does not have.
+ *
+ * An agent listed here gets its remote servers bridged instead — see
+ * remoteMcpBridge. Add to this set only on evidence from the binary; the whole
+ * point is that "the docs say it works" is not evidence.
+ */
+export declare const AGENTS_WITHOUT_HTTP_MCP: Set<string>;
+export declare function agentNeedsMcpBridge(agent: string): boolean;
+/**
+ * Turn a remote MCP server into a STDIO command, for agents that cannot speak
+ * HTTP MCP themselves.
+ *
+ * mcp-remote is the standard stdio<->HTTP shim, and the one grok's own README
+ * reaches for in its Linear example. Verified end to end against grok 1.0.3:
+ * the bridged server's tools appear and are callable.
+ *
+ * The cost is an npx start per remote server — exactly the cost moving to HTTP
+ * removed — so this is a fallback for the agents that need it, never the
+ * default path.
+ */
+export declare function remoteMcpBridge(url: string, env?: Record<string, string> | null): {
+    command: string;
+    args: string[];
+};

package/dist/mcp-headers.js

@@ -8,9 +8,12 @@
 // inline in install.ts (the claude path) and the other four adapters each got
 // it wrong in their own way, so it lives here now and they all call it.
 Object.defineProperty(exports, "__esModule", { value: true });
+exports.AGENTS_WITHOUT_HTTP_MCP = void 0;
 exports.isRemoteMcp = isRemoteMcp;
 exports.remoteMcpUrl = remoteMcpUrl;
 exports.remoteMcpHeaders = remoteMcpHeaders;
+exports.agentNeedsMcpBridge = agentNeedsMcpBridge;
+exports.remoteMcpBridge = remoteMcpBridge;
 /** True when a registry row describes a remote MCP server rather than a
  *  local process to spawn. */
 function isRemoteMcp(command) {
@@ -47,3 +50,52 @@ function remoteMcpHeaders(env) {
     }
     return headers;
 }
+/**
+ * Which agents can actually open an HTTP MCP connection, measured against the
+ * real binaries rather than their documentation.
+ *
+ *   claude  YES  — proven in production; entities use these every day.
+ *   codex   YES  — `codex mcp list` shows a `url` entry under Url, enabled.
+ *   kimi    YES  — `kimi mcp list` prints "<slug> (http): <url>".
+ *   gemini  ?    — UNVERIFIED. The CLI on hand cannot authenticate at all
+ *                  ("no longer supported for Gemini Code Assist for
+ *                  individuals"), so its httpUrl handling was never observed
+ *                  connecting. No entity runs gemini today. If one ever does,
+ *                  verify before trusting it — this exact assumption is what
+ *                  cost us grok.
+ *   grok    NO   — grok 1.0.3 SILENTLY IGNORES url-based entries. In one run it
+ *                  loaded ten stdio servers and skipped every remote one, ours
+ *                  and a third party's, with no error, while its own bundled
+ *                  README documents `url` + `headers`. The docs describe a
+ *                  transport the binary does not have.
+ *
+ * An agent listed here gets its remote servers bridged instead — see
+ * remoteMcpBridge. Add to this set only on evidence from the binary; the whole
+ * point is that "the docs say it works" is not evidence.
+ */
+exports.AGENTS_WITHOUT_HTTP_MCP = new Set(['grok']);
+function agentNeedsMcpBridge(agent) {
+    return exports.AGENTS_WITHOUT_HTTP_MCP.has(agent);
+}
+/**
+ * Turn a remote MCP server into a STDIO command, for agents that cannot speak
+ * HTTP MCP themselves.
+ *
+ * mcp-remote is the standard stdio<->HTTP shim, and the one grok's own README
+ * reaches for in its Linear example. Verified end to end against grok 1.0.3:
+ * the bridged server's tools appear and are callable.
+ *
+ * The cost is an npx start per remote server — exactly the cost moving to HTTP
+ * removed — so this is a fallback for the agents that need it, never the
+ * default path.
+ */
+function remoteMcpBridge(url, env) {
+    const args = ['-y', 'mcp-remote', url];
+    for (const [key, value] of Object.entries(remoteMcpHeaders(env))) {
+        // Spawned without a shell, so "K:V" needs no quoting of its own.
+        args.push('--header', `${key}:${value}`);
+    }
+    // Our servers are streamable HTTP; skip the SSE fallback probing.
+    args.push('--transport', 'http-only');
+    return { command: 'npx', args };
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@addai/node",
-  "version": "0.24.0",
+  "version": "0.24.1",
   "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": [