@getforgeai/cli 0.1.0-beta.1 → 0.1.0-beta.2

package/dist/mcp/mcp-probe.d.ts

@@ -1,3 +1,23 @@
+/**
+ * Resolve the ForgeAI CLI binary to spawn for the MCP probe.
+ *
+ * This must point at the CLI entry point (dist/bin/forgeai.js), which is the
+ * only script that parses an `mcp` subcommand. It used to use
+ * `process.argv[1]`, which is correct when the probe runs from the CLI itself
+ * but WRONG in the case that actually matters: the probe normally runs inside
+ * the daemon, where argv[1] is dist/lib/daemon-entry.js. That entry point
+ * parses no arguments, so `daemon-entry.js mcp ...` silently started another
+ * daemon instead of an MCP server — the probe then timed out every time,
+ * `mcpHealthy` stayed false, and the Cloud skipped this CLI for dispatch
+ * (task-dispatch-engine skips CLIs reporting mcpHealthy === false), while each
+ * re-probe leaked one more detached daemon process.
+ *
+ * Resolve it from this module's own location instead: dist/mcp/ -> dist/bin/.
+ */
+export declare function resolveForgeBinary(): {
+    command: string;
+    prefixArgs: string[];
+};
 /**
  * Probe the MCP server to verify it can start and respond to JSON-RPC initialize.
  *

package/dist/mcp/mcp-probe.js

@@ -1,13 +1,33 @@
 import { spawn } from "node:child_process";
+import { existsSync } from "node:fs";
+import { join } from "node:path";
 import chalk from "chalk";
 const PROBE_TIMEOUT_MS = 10_000;
 /**
- * Resolve the ForgeAI CLI binary for MCP probe.
- * Same logic as agent-spawner's resolveForgeBinary.
+ * Resolve the ForgeAI CLI binary to spawn for the MCP probe.
+ *
+ * This must point at the CLI entry point (dist/bin/forgeai.js), which is the
+ * only script that parses an `mcp` subcommand. It used to use
+ * `process.argv[1]`, which is correct when the probe runs from the CLI itself
+ * but WRONG in the case that actually matters: the probe normally runs inside
+ * the daemon, where argv[1] is dist/lib/daemon-entry.js. That entry point
+ * parses no arguments, so `daemon-entry.js mcp ...` silently started another
+ * daemon instead of an MCP server — the probe then timed out every time,
+ * `mcpHealthy` stayed false, and the Cloud skipped this CLI for dispatch
+ * (task-dispatch-engine skips CLIs reporting mcpHealthy === false), while each
+ * re-probe leaked one more detached daemon process.
+ *
+ * Resolve it from this module's own location instead: dist/mcp/ -> dist/bin/.
  */
-function resolveForgeBinary() {
+export function resolveForgeBinary() {
+    const binPath = join(import.meta.dirname, "..", "bin", "forgeai.js");
+    if (existsSync(binPath)) {
+        return { command: process.execPath, prefixArgs: [binPath] };
+    }
+    // Fallback for unusual layouts: use argv[1] only when it really is the CLI
+    // entry point, never the daemon entry.
     const scriptPath = process.argv[1];
-    if (scriptPath) {
+    if (scriptPath?.includes(join("bin", "forgeai"))) {
         return { command: process.execPath, prefixArgs: [scriptPath] };
     }
     return { command: "forgeai", prefixArgs: [] };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@getforgeai/cli",
-  "version": "0.1.0-beta.1",
+  "version": "0.1.0-beta.2",
   "description": "ForgeAI CLI — runs AI coding agents in local Docker containers with your own AI tokens, and connects them to the ForgeAI cockpit.",
   "license": "Apache-2.0",
   "type": "module",