@love-moon/conductor-cli 0.17.1 → 0.17.2

package/CHANGELOG.md

@@ -1,5 +1,31 @@
 # @love-moon/conductor-cli
 
+## 0.17.2
+
+### Patch Changes
+
+- 0a9488e: Add Kimi website text conversations with persistent login, multi-turn context,
+  reply progress, new chats and browser diagnostics. Expose the provider through
+  ai-sdk's chat-web backend and the web-kimi Conductor configuration alias.
+
+  Explicit unknown chat-web providers now fail with a clear error instead of
+  silently opening ChatGPT. The existing kimi CLI backend is unchanged.
+
+- b16c1ae: Allow a shared daemon to run the AI side of a Global AI Backend task while code
+  stays on one of the user's own daemons. Advertise
+  `shared_ai_global_backend_v1` and forward the task id on remote exec, file, and
+  MCP requests so the backend can authorize only that task's remote binding.
+
+  Keep remote grants tied to active tasks: shared credentials cannot mint remote
+  bindings, renew them through restarts or persistent rounds, or reactivate ended
+  tasks through status updates. Check shared AI compatibility when restarting or
+  starting later rounds of an existing remote task too.
+
+- Updated dependencies [b124565]
+- Updated dependencies [0a9488e]
+  - @love-moon/ai-sdk@0.17.2
+  - @love-moon/conductor-sdk@0.17.2
+
 ## 0.17.1
 
 ### Patch Changes

package/bin/conductor-config.js

@@ -55,13 +55,19 @@ const DEFAULT_CLIs = {
   // chat-web is the runtime backend (an in-process Chromium driver, not a CLI
   // binary). It has multiple sub-providers selected via --model. Each user-
   // facing alias below resolves to the chat-web runtime; advertising the bare
-  // `chat-web` backend would be ambiguous, so we emit two explicit aliases.
+  // `chat-web` backend would be ambiguous, so we emit explicit aliases.
   "web-chatgpt": {
     command: "chat-web",
     execArgs: "--model chatgpt",
     description: "Chat web (ChatGPT) via @love-moon/chat-web",
     runtimeBackend: "chat-web"
   },
+  "web-kimi": {
+    command: "chat-web",
+    execArgs: "--model kimi",
+    description: "Chat web (Kimi) via @love-moon/chat-web",
+    runtimeBackend: "chat-web"
+  },
   "web-gemini": {
     command: "chat-web",
     execArgs: "--model gemini",
@@ -137,10 +143,10 @@ function buildConfigEntryLines(cli, info, { commented = false } = {}) {
     lines.push(`${commentPrefix}opencode runs via ai-sdk server mode with permission=allow`);
   }
   if (cli === "web-chatgpt") {
-    // web-chatgpt / web-gemini both resolve to the chat-web runtime backend
+    // web-chatgpt / web-gemini / web-kimi resolve to the chat-web runtime backend
     // (an in-process Chromium driver via @love-moon/chat-web). The command
     // line is not executed; CLI parses --model from it.
-    lines.push(`${commentPrefix}web-chatgpt / web-gemini drive a real Chromium browser via @love-moon/chat-web`);
+    lines.push(`${commentPrefix}web-chatgpt / web-gemini / web-kimi drive a real Chromium browser via @love-moon/chat-web`);
   }
 
   lines.push(`${entryPrefix}${cli}: ${fullCommand}`);

package/bin/conductor-fire.js

@@ -940,10 +940,10 @@ async function main() {
       env: process.env,
     });
 
-    // chat-web tasks drive a real Chromium browser that holds a per-profile
-    // singleton lock for as long as the task lives. A task that never ends
-    // pins that browser indefinitely (and blocks other chats for the same
-    // provider), so we cap its active lifetime and auto-stop it when exceeded.
+    // chat-web tasks retain a tab in the shared profile browser while alive.
+    // New runtimes schedule turns across tasks; older runtimes exclusively
+    // own the profile. Cap task lifetime so abandoned sessions release their
+    // browser resources in either runtime.
     // The conversation itself is preserved (it lives in the provider account
     // and the persisted profile; closing the browser does not delete it).
     const runtimeBackendToken = String(sessionCommandLine || "")

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@love-moon/conductor-cli",
-  "version": "0.17.1",
-  "gitCommitId": "e3dbbad",
+  "version": "0.17.2",
+  "gitCommitId": "1671ee1",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/lovemoon-ai/conductor.git"
@@ -24,8 +24,8 @@
     "test": "node --test test/*.test.js"
   },
   "dependencies": {
-    "@love-moon/ai-sdk": "0.17.1",
-    "@love-moon/conductor-sdk": "0.17.1",
+    "@love-moon/ai-sdk": "0.17.2",
+    "@love-moon/conductor-sdk": "0.17.2",
     "@github/copilot-sdk": "^0.3.0",
     "chrome-launcher": "^1.2.1",
     "chrome-remote-interface": "^0.33.0",
@@ -38,7 +38,7 @@
   },
   "optionalDependencies": {
     "@roamhq/wrtc": "^0.10.0",
-    "@love-moon/chat-web": "0.17.1"
+    "@love-moon/chat-web": "0.17.2"
   },
   "pnpm": {
     "onlyBuiltDependencies": [

package/src/daemon.js

@@ -3928,6 +3928,9 @@ export function startDaemon(config = {}, deps = {}) {
     // another daemon over `conductor remote` and binds the remote_* MCP tools
     // to a remoteWorkspace as well as a remoteWorktree.
     "global_backend_v1",
+    // A shared AI also sends CONDUCTOR_TASK_ID on every remote request so the
+    // backend can grant only that task's A → B remote permission.
+    "shared_ai_global_backend_v1",
     "backend_session_list",
     CUSTOM_COMMANDS_CAPABILITY,
     UPDATE_DAEMON_CAPABILITY,

package/src/remote/client.js

@@ -62,7 +62,11 @@ export function loadCliConfig(configFile, env = process.env) {
 }
 
 function authHeaders(config) {
-  return { Authorization: `Bearer ${config.agentToken}` };
+  const taskId = process.env.CONDUCTOR_TASK_ID?.trim();
+  return {
+    Authorization: `Bearer ${config.agentToken}`,
+    ...(taskId ? { "X-Conductor-Task-Id": taskId } : {}),
+  };
 }
 
 async function toApiError(response) {

package/src/remote/mcp-launch.js

@@ -19,6 +19,7 @@ export const REMOTE_WORKTREE_ENV = "CONDUCTOR_REMOTE_WORKTREE";
 const FORWARDED_ENV = [
   "CONDUCTOR_AGENT_TOKEN",
   "CONDUCTOR_BACKEND_URL",
+  "CONDUCTOR_TASK_ID",
   "CONDUCTOR_CONFIG",
   "CONDUCTOR_HOME",
   "CONDUCTOR_REMOTE_CHUNK_BYTES",

package/src/runtime-backends.js

@@ -19,9 +19,9 @@ const BUILT_IN_RUNTIME_BACKEND_SET = new Set(BUILT_IN_RUNTIME_BACKENDS);
 //
 // chat-web is intentionally NOT here even though it's also command-optional
 // (it drives a Chromium browser, not a CLI). The reason: chat-web has
-// configurable sub-providers (chatgpt / gemini / deepseek) selected via
+// configurable sub-providers (chatgpt / gemini / kimi) selected via
 // `--model`, and surfacing a bare `chat-web` backend alongside user
-// aliases like `web-chatgpt` / `web-gemini` is just confusing — the alias
+// aliases like `web-chatgpt` / `web-gemini` / `web-kimi` is just confusing — the alias
 // IS the sub-provider choice. Users who want chat-web must declare an
 // explicit allow_cli_list entry (which is also where `--model` lives).
 const COMMAND_OPTIONAL_BUILT_IN_RUNTIME_BACKENDS = ["copilot", "dsh"];