@launchchair/agent - npm Package Compare versions

Comparing version

+3

-2

AGENTS.md

		@@ -117,3 +117,3 @@ # LaunchChair Agent Bootstrap
		required = false
		startup_timeout_sec = 20
		startup_timeout_sec = 45
		tool_timeout_sec = 3600
		@@ -124,2 +124,3 @@ default_tools_approval_mode = "approve"
		LAUNCHCHAIR_BASE_URL = "https://www.launchchair.io"
		LAUNCHCHAIR_CONFIG_DIR = "/absolute/path/to/.launchchair"
		LAUNCHCHAIR_PROJECT_ID = ""
		@@ -134,3 +135,3 @@ LC_AGENT_ROUTER_GPT_TARGET = "codex"

		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.
		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, argument, and saved-config paths for this machine.

		@@ -137,0 +138,0 @@ ## What To Do First In A Fresh Chat

+4

-2

launchchair-cli.mjs

		@@ -18,3 +18,3 @@ #!/usr/bin/env node

		const VERSION = "0.4.6";
		const VERSION = "0.4.7";
		const SCRIPT_DIR = path.dirname(fileURLToPath(import.meta.url));
		@@ -733,2 +733,3 @@ const DEFAULT_BASE_URL = "https://www.launchchair.io";
		LAUNCHCHAIR_BASE_URL: baseUrl(),
		LAUNCHCHAIR_CONFIG_DIR: CONFIG_DIR,
		LAUNCHCHAIR_AGENT_TOKEN: token(),
		@@ -853,2 +854,3 @@ LAUNCHCHAIR_PROJECT_ID: projectId,
		LAUNCHCHAIR_BASE_URL: baseUrl(),
		LAUNCHCHAIR_CONFIG_DIR: CONFIG_DIR,
		...(token() \|\| !includeTokenPlaceholder ? {} : { LAUNCHCHAIR_AGENT_TOKEN: "<optional full lc_at token when launchchair login was not used>" }),
		@@ -894,3 +896,3 @@ ...(projectId ? { LAUNCHCHAIR_PROJECT_ID: projectId } : {}),
		required = false
		startup_timeout_sec = 20
		startup_timeout_sec = 45
		tool_timeout_sec = 3600
		@@ -897,0 +899,0 @@ default_tools_approval_mode = "approve"

+1

-1

local-bridge.mjs

		@@ -20,3 +20,3 @@ #!/usr/bin/env node

		const VERSION = "0.4.6";
		const VERSION = "0.4.7";
		const CLIENT_TYPES = ["codex", "chatgpt", "claude", "claude_code", "other"];
		@@ -23,0 +23,0 @@ const AGENT_SCRIPT_DIR = path.dirname(fileURLToPath(import.meta.url));

+1

-1

mcp-bridge-server.mjs

		@@ -22,3 +22,3 @@ #!/usr/bin/env node

		const VERSION = "0.4.6";
		const VERSION = "0.4.7";
		const SERVER_NAME = "launchchair-agent-mcp";
		@@ -25,0 +25,0 @@ const AGENT_SCRIPT_DIR = path.dirname(fileURLToPath(import.meta.url));

+1

-1

package.json

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

+1

-1

README.md

		@@ -148,3 +148,3 @@ # LaunchChair Agent

		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.
		The recommended config launches the MCP server through the exact Node executable and CLI file path generated by `launchchair setup` or `launchchair mcp-config`. It also pins `LAUNCHCHAIR_CONFIG_DIR` to the exact directory used by `launchchair login`, so Codex and Claude users do not need to paste tokens into MCP config after browser login—even when the desktop app starts with a different home or shell environment.

		@@ -151,0 +151,0 @@ 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.

New alerts