@chatpanel/bridge 0.10.34 → 0.10.36

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@chatpanel/bridge",
-  "version": "0.10.34",
+  "version": "0.10.36",
   "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/cli-agents.js

@@ -6,6 +6,7 @@
 //   pi       — pi -p "<prompt>"        · --model · @{path} images · --list-models
 //   opencode — opencode run "<prompt>" · -m provider/model · -f {path} images · models
 //   kiro     — kiro-cli chat --no-interactive "<prompt>" · --model · --list-models
+//   hermes   — hermes -z "<prompt>"      · -m model · config get model (no list command)
 
 import { runSpec, listSpecModels, runForStdout } from './custom.js';
 import { findAgentBin } from '../env.js';
@@ -248,3 +249,48 @@ export async function listDshModels(command = 'dsh', workingDir) {
   }
   return [...DSH_KNOWN_MODELS];
 }
+
+// Hermes Agent (Nous Research). `-z/--oneshot` prints ONLY the final response text — no
+// banner, no spinner, no tool previews — which is exactly the contract the shared runner
+// wants, and it auto-bypasses approvals so a headless turn never blocks on a prompt.
+//
+// Its own tools and skills (82 of them here) stay ACTIVE: Hermes loads them itself, and the
+// bridge's browser tools arrive over the stable /mcp endpoint like opencode and kiro, since
+// Hermes only reads MCP servers from its own config rather than a per-run file.
+//
+// `hermes model` is interactive with no --list flag, so model discovery goes through
+// `hermes config get model`, which prints the resolved default + provider as `key: value`
+// lines. That yields the one model the user has actually configured — honest, if short.
+export const hermes = makeCliAgent(
+  'hermes',
+  {
+    // `-z {prompt}`, NOT a bare `-z`: Hermes takes the prompt as the VALUE of -z (Python
+    // argparse), and the runner appends a trailing prompt only when no {prompt} placeholder
+    // exists — after the model flag. That produced `hermes -z -m <model> "<prompt>"`, where
+    // argparse saw -z followed by another flag: "expected one argument". The placeholder
+    // binds the prompt to the flag, so the model flag can sit anywhere after it.
+    args: '-z {prompt}',
+    promptVia: 'arg',
+    modelArg: '-m {model}',
+    requiresStableMcp: true,
+    autoSetupStableMcp: true,
+    stableMcpConfigCheck: 'hermes',
+    stableMcpSetupArgs: ['mcp', 'add', 'chatpanel_browser', '--url', 'http://127.0.0.1:4319/mcp'],
+    stableMcpSetupCommand: 'hermes mcp add chatpanel_browser --url http://127.0.0.1:4319/mcp',
+    label: 'Hermes',
+  },
+  'hermes not found on PATH. Install Hermes Agent, then run `hermes setup` to sign in.',
+  {
+    // `config get model` prints resolved settings as `key: value`; we want the default model
+    // id, not the provider or base_url lines around it.
+    listModels: async (command, options = {}) => {
+      try {
+        const out = await runForStdout(command, ['config', 'get', 'model'], options.workingDir);
+        const m = /^\s*default:\s*(\S+)/m.exec(out || '');
+        return m ? [m[1]] : [];
+      } catch {
+        return []; // not configured yet — the picker still accepts a typed id
+      }
+    },
+  },
+);

package/src/engines/custom.js

@@ -307,9 +307,17 @@ async function kiroHasStableMcpConfig(command, cwd) {
   return false;
 }
 
+// Hermes keeps MCP servers in its own config; `hermes mcp list` is the one honest way to ask
+// whether ours is already registered (no scopes, unlike kiro).
+async function hermesHasStableMcpConfig(command, cwd) {
+  const out = await commandOutput(command, ['mcp', 'list'], cwd);
+  return out.includes(CHATPANEL_STABLE_MCP_URL) || /chatpanel_browser/i.test(out);
+}
+
 async function hasStableMcpConfig(spec, cwd) {
   if (spec.stableMcpConfigCheck === 'kiro') return kiroHasStableMcpConfig(spec.command || 'kiro-cli', cwd);
   if (spec.stableMcpConfigCheck === 'opencode') return opencodeHasStableMcpConfig();
+  if (spec.stableMcpConfigCheck === 'hermes') return hermesHasStableMcpConfig(spec.command || 'hermes', cwd);
   return false;
 }
 

package/src/server.js

@@ -33,7 +33,7 @@ import { join } from 'node:path';
 import * as claude from './engines/claude.js';
 import * as codex from './engines/codex.js';
 import * as antigravity from './engines/antigravity.js';
-import { pi, opencode, kiro, copilot, deepseek } from './engines/cli-agents.js';
+import { pi, opencode, kiro, copilot, deepseek , hermes } from './engines/cli-agents.js';
 import { connectorsFor } from './connectors.js';
 import * as custom from './engines/custom.js';
 import { installService, uninstallService, serviceStatus, restartService } from './service.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.34';
+const VERSION = '0.10.36';
 const HOST = process.env.CHATPANEL_BRIDGE_HOST || '127.0.0.1';
 const PORT = Number(process.env.CHATPANEL_BRIDGE_PORT) || 4319;
 
@@ -77,6 +77,7 @@ const ENGINES = {
   antigravity: { engine: antigravity, label: 'Antigravity' },
   pi: { engine: pi, label: 'Pi' },
   opencode: { engine: opencode, label: 'OpenCode' },
+  hermes: { engine: hermes, label: 'Hermes' },
   kiro: { engine: kiro, label: 'Kiro' },
   copilot: { engine: copilot, label: 'GitHub Copilot' },
   deepseek: { engine: deepseek, label: 'DeepSeek Harness' },