@chatpanel/bridge 0.10.37 → 0.10.39

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@chatpanel/bridge",
-  "version": "0.10.37",
+  "version": "0.10.39",
   "type": "module",
   "description": "Local bridge that exposes the AI coding agents installed on your machine \u2014 Claude Code (CLI), Codex (CLI), and Antigravity CLI (formerly Gemini CLI, which remains available for business/enterprise) \u2014 to the ChatPanel Chrome extension over a localhost SSE endpoint. Bring your own agent.",
   "keywords": [

package/src/engines/custom.js

@@ -333,24 +333,43 @@ async function runStableMcpSetup(plan, cwd) {
     let child;
     try { child = spawn(bin, argv, opts); } catch (e) { return reject(new Error(`Failed to start ${plan.command}: ${e.message}`)); }
     let stderr = '';
+    // The CLI often reports WHY it couldn't register on stdout while still exiting 0 (Hermes
+    // prints "requires the 'mcp' Python SDK" and saves nothing). Capturing it is what lets
+    // the caller turn a silent no-op into an actionable message.
+    let stdout = '';
     const timer = setTimeout(() => {
       child.kill('SIGKILL');
       reject(new Error(`${plan.command} MCP setup timed out.`));
     }, 20_000);
     child.stderr.on('data', (d) => (stderr += d.toString()));
+    child.stdout?.on('data', (d) => (stdout += d.toString()));
     child.on('error', (e) => {
       clearTimeout(timer);
       reject(new Error(`Failed to start ${plan.command}: ${e.message}`));
     });
     child.on('close', (code) => {
       clearTimeout(timer);
-      if (code === 0) return resolve();
+      if (code === 0) return resolve(`${stdout}\n${stderr}`.trim());
       reject(new Error(`${plan.command} MCP setup exited ${code}: ${stderr.trim().split('\n').pop() || 'failed'}`));
     });
     try { child.stdin.end(); } catch { /* ignore */ }
   });
 }
 
+// Turn a browser-tool setup failure into something the user can act on. The CLI's own words
+// are the most accurate signal available, so we forward them — but when they name a missing
+// SDK we say the fix, rather than repeating an `mcp add` that will fail identically.
+export function mcpSetupHint(label, err) {
+  const msg = String(err?.message || err || '');
+  if (/mcp['" ]* Python SDK|No module named ['"]?mcp|MCP support/i.test(msg)) {
+    return `${label} has no MCP support installed. Run \`hermes setup\` (or install the \`mcp\` package in its environment), then retry.`;
+  }
+  if (/streamable_http|HTTP transport/i.test(msg)) {
+    return `${label}'s MCP client has no HTTP transport; ChatPanel registers a stdio server instead. Upgrade its \`mcp\` package if this persists.`;
+  }
+  return msg.slice(0, 200) || 'the CLI could not register the tools';
+}
+
 export async function ensureStableMcpConfig(spec, cwd, label, emit, deps = {}) {
   if (!spec.requiresStableMcp) return true;
   const hasConfig = deps.hasConfig || hasStableMcpConfig;
@@ -372,9 +391,15 @@ export async function ensureStableMcpConfig(spec, cwd, label, emit, deps = {}) {
   }
 
   emit({ type: 'status', text: `${label} is setting up one-time browser tools...` });
-  await runSetup(plan, cwd);
+  // Keep what the CLI said: it commonly exits 0 while refusing to register (no MCP SDK, no
+  // HTTP transport), and that sentence is the only accurate explanation available.
+  const setupOutput = String((await runSetup(plan, cwd)) || '').trim();
   if (await hasConfig(spec, cwd)) return true;
-  throw new Error(`${label} browser-tool setup completed, but the MCP server is still not visible. Run: ${setupCommand}`);
+  throw new Error(
+    `${label} browser-tool setup did not register the server.`
+    + (setupOutput ? ` ${setupOutput.split('\n').filter(Boolean).slice(-3).join(' ')}` : '')
+    + ` Run: ${setupCommand}`,
+  );
 }
 
 export async function chat({ messages, system, options, images }, emit, { signal } = {}) {
@@ -474,10 +499,25 @@ export async function runSpec(spec, { messages, system, options = {}, images },
       : [...tmpl.split(/\s+/).filter(Boolean), cfgFile];
     args = [...tokens, ...args];
   }
-  if (options.mcp?.url) args.push(...mcpTrustArgs(spec, options.mcp));
   // Some CLIs only load MCP from their persistent config, so ensure that stable
   // /mcp endpoint is present before letting the agent answer with no tools.
-  if (options.mcp?.url) await ensureStableMcpConfig(spec, cwd, label, emit);
+  //
+  // DEGRADE, DON'T FAIL. Browser tools are an ENHANCEMENT on top of a CLI that already has
+  // its own; a turn that could have been answered should not die because they couldn't be
+  // registered. (Hermes ships without the `mcp` Python SDK unless `hermes setup` installed
+  // it, so every tool-armed turn failed — and the error told the user to run a command that
+  // fails the same way.) We now say what happened, drop the browser tools, and answer.
+  if (options.mcp?.url) {
+    try {
+      await ensureStableMcpConfig(spec, cwd, label, emit);
+    } catch (e) {
+      emit({ type: 'status', text: `${label}: continuing without ChatPanel's browser tools — ${mcpSetupHint(label, e)}` });
+      options = { ...options, mcp: null };
+    }
+  }
+  // Trust flags only make sense once the server is actually registered — pushing them for
+  // tools we then dropped would widen the CLI's permissions for nothing.
+  if (options.mcp?.url) args.push(...mcpTrustArgs(spec, options.mcp));
 
   // Model via a CONFIG-PATCH FILE, for agents with no --model flag (dsh takes the
   // model as a Cordis config overlay: `--patch <file>` replacing one row by id).

package/src/server.js

@@ -67,7 +67,7 @@ import {
 // Hardcoded (not read from package.json) so it survives Bun's single-file
 // --compile, where package.json isn't on a readable FS. CI fails the publish if
 // this drifts from package.json, so the two can't silently diverge.
-const VERSION = '0.10.37';
+const VERSION = '0.10.39';
 const HOST = process.env.CHATPANEL_BRIDGE_HOST || '127.0.0.1';
 const PORT = Number(process.env.CHATPANEL_BRIDGE_PORT) || 4319;