@launchchair/agent 0.4.5 → 0.4.6

package/AGENTS.md

@@ -111,8 +111,8 @@ The build folder can be an empty scratch folder until Stack Setup creates or rec
 
 ```toml
 [mcp_servers.launchchair]
-command = "launchchair"
-args = ["mcp-server"]
+command = "/absolute/path/to/node"
+args = ["/absolute/path/to/launchchair-cli.mjs", "mcp-server"]
 required = false
 startup_timeout_sec = 20
 tool_timeout_sec = 3600
@@ -129,7 +129,7 @@ LC_AGENT_CODEX_CWD = "/absolute/path/to/the-folder-codex-should-build-into"
 # LAUNCHCHAIR_AGENT_TOKEN = "<full lc_at token from Settings API Access>"
 ```
 
-If the desktop app cannot find `launchchair`, run `which launchchair` in Terminal and use that absolute path as the MCP command.
+Prefer `launchchair setup codex --cwd /absolute/path/to/build-folder --write-config` or `launchchair mcp-config codex --ui-fields` so the CLI prints exact local command and argument paths for this machine.
 
 ## What To Do First In A Fresh Chat
 

package/README.md

@@ -145,9 +145,9 @@ Print a Claude Desktop MCP config example:
 launchchair mcp-config claude
 ```
 
-The recommended config launches `launchchair mcp-server`. That process reads the token saved by `launchchair login`, so Codex and Claude users do not need to paste tokens into MCP config after browser login.
+The recommended config launches the MCP server through the exact Node executable and CLI file path generated by `launchchair setup` or `launchchair mcp-config`. That process reads the token saved by `launchchair login`, so Codex and Claude users do not need to paste tokens into MCP config after browser login.
 
-Use `LAUNCHCHAIR_AGENT_TOKEN` only as a manual fallback when you skip `launchchair login`, need a per-client token override, or your desktop app cannot read the saved CLI config. If a desktop app cannot find `launchchair`, run `which launchchair` and use that absolute path as the MCP command.
+Use `LAUNCHCHAIR_AGENT_TOKEN` only as a manual fallback when you skip `launchchair login`, need a per-client token override, or your desktop app cannot read the saved CLI config. If you use a desktop custom MCP form, run `launchchair mcp-config codex --ui-fields` or `launchchair mcp-config claude --ui-fields` and paste the printed command, each argument, env vars, and working directory exactly as shown.
 
 ## Local Bridge
 

package/launchchair-cli.mjs

@@ -15,7 +15,7 @@ import path from "node:path";
 import process from "node:process";
 import { fileURLToPath } from "node:url";
 
-const VERSION = "0.4.4";
+const VERSION = "0.4.6";
 const SCRIPT_DIR = path.dirname(fileURLToPath(import.meta.url));
 const DEFAULT_BASE_URL = "https://www.launchchair.io";
 const CONFIG_DIR = process.env.LAUNCHCHAIR_CONFIG_DIR?.trim()
@@ -858,9 +858,10 @@ function mcpEnvForTarget(target, options = {}) {
 }
 
 function mcpServerConfig(target, options = {}) {
+  const cliPath = path.join(SCRIPT_DIR, "launchchair-cli.mjs");
   return {
-    command: "launchchair",
-    args: ["mcp-server"],
+    command: process.execPath,
+    args: [cliPath, "mcp-server"],
     env: mcpEnvForTarget(target, options),
   };
 }
@@ -882,9 +883,10 @@ function renderMcpConfig(target, options = {}) {
   const envLines = Object.entries(server.env)
     .map(([key, value]) => `${key} = ${tomlString(value)}`)
     .join("\n");
+  const argsLine = server.args.map(tomlString).join(", ");
   return `[mcp_servers.launchchair]
-command = "launchchair"
-args = ["mcp-server"]
+command = ${tomlString(server.command)}
+args = [${argsLine}]
 required = false
 startup_timeout_sec = 20
 tool_timeout_sec = 3600
@@ -913,7 +915,7 @@ Command to launch
   ${server.command}
 
 Arguments
-  ${server.args.join(" ")}
+${server.args.map((arg) => `  ${arg}`).join("\n")}
 
 Environment variables
 ${envLines}
@@ -1219,7 +1221,7 @@ async function setup(args) {
       print(`1. Paste the MCP config above into ${details.label}.`);
       print(`2. Restart or reload ${details.label} so the MCP server is exposed to fresh chats.`);
     }
-    print("3. If the desktop app cannot find launchchair, run `which launchchair` and use that absolute path as the command.");
+    print("3. Use the generated command and argument fields exactly as printed; setup resolves the local Node and CLI paths for this machine.");
     print("4. Keep this bridge running when you want LaunchChair's Run with agent button to work:");
     print(`   ${paint("launchchair bridge", "cyan")}`);
     print("5. Start a fresh agent chat. The agent should discover the LaunchChair skill and MCP server instructions automatically.");

package/local-bridge.mjs

@@ -17,7 +17,7 @@ import process from "node:process";
 import { fileURLToPath } from "node:url";
 import { buildRunnerCommand, parseRunnerCommand } from "./runner-command.mjs";
 
-const VERSION = "0.4.4";
+const VERSION = "0.4.6";
 const CLIENT_TYPES = ["codex", "chatgpt", "claude", "claude_code", "other"];
 const AGENT_SCRIPT_DIR = path.dirname(fileURLToPath(import.meta.url));
 const CONFIG_DIR = process.env.LAUNCHCHAIR_CONFIG_DIR?.trim()

package/mcp-bridge-server.mjs

@@ -19,7 +19,7 @@ import process from "node:process";
 import { fileURLToPath } from "node:url";
 import { buildRunnerCommand, parseRunnerCommand } from "./runner-command.mjs";
 
-const VERSION = "0.4.4";
+const VERSION = "0.4.6";
 const SERVER_NAME = "launchchair-agent-mcp";
 const AGENT_SCRIPT_DIR = path.dirname(fileURLToPath(import.meta.url));
 const CONFIG_DIR = process.env.LAUNCHCHAIR_CONFIG_DIR?.trim()

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@launchchair/agent",
-  "version": "0.4.5",
+  "version": "0.4.6",
   "description": "LaunchChair Agent CLI, MCP bridge, local bridge, and runners for Codex, Claude Code, ChatGPT, Claude, and Hermes workflows.",
   "type": "module",
   "bin": {