@love-moon/conductor-cli 0.11.0 → 0.11.2

package/CHANGELOG.md

@@ -1,5 +1,102 @@
 # @love-moon/conductor-cli
 
+## 0.11.2
+
+### Patch Changes
+
+- 938efe7: Fix "New task from this" when the successor runs on a different daemon.
+
+  Picking another daemon in the dialog created the successor row and then killed
+  it one second later with `new task failed: Could not resolve resume cwd`. The
+  server intentionally drops the source machine's paths for a cross-daemon fork,
+  and the target daemon had nothing left to resolve: no launch-config `cwd`, no
+  worktree, no local project path (the default project has none, and a project
+  bound to another daemon is refused by design), and no source session in its own
+  session store.
+
+  Fork modes now fall back to a fresh `<workspace>/<date>/<run>` directory — the
+  same fallback `create_task` already uses — so the successor starts like a
+  brand-new task on that machine and picks up the conversation through the
+  resume-context URL. In-place restarts still fail loudly, because they must reuse
+  the original working directory.
+
+  - @love-moon/conductor-sdk@0.11.2
+  - @love-moon/ai-sdk@0.11.2
+
+## 0.11.1
+
+### Patch Changes
+
+- cd5e428: Add a built-in "Update daemon" action to the web settings Danger zone.
+
+  This replaces the hand-rolled `update` custom command people were keeping in
+  `custom_commands` (upgrade the CLI, then restart the daemon in tmux) with a
+  first-class button on any daemon advertising the new `update_daemon` capability.
+
+  The update is designed so that a failure never leaves the machine without a
+  daemon:
+
+  - It runs in a **detached** updater process, not inside the daemon, so the
+    daemon it replaces can exit without taking the update with it — and a
+    crashing update cannot take the daemon down either.
+  - Install and verification happen **first**. The running daemon is only stopped
+    once the new version is installed, reports the expected version, and passes
+    the node-pty native check. Anything failing before that aborts with the old
+    daemon still running and still serving tasks.
+  - A half-removed global install (the `ENOTEMPTY` case) is uninstalled, its
+    package directory removed, and the install retried once.
+  - Progress is journaled to `~/.conductor/state/daemon-update.json` (full output
+    in `~/.conductor/logs/daemon-update.log`), so the outcome survives the restart
+    and the web UI can poll for it across the daemon's reconnect.
+
+  Homebrew installs, non-global installs, and shared guest daemons refuse the
+  action up front with the reason shown in the UI.
+
+- 8ad51f3: Adopt the tmux-detached Fire processes a previous daemon left running, instead
+  of judging them stale and marking their tasks `killed`.
+
+  With `fire_tmux_mode`, daemon shutdown deliberately leaves Fires alive. But a
+  fresh daemon started with an empty `activeTaskProcesses` map, and both stale
+  sweeps — `recoverStaleTasks()` on startup and `reconcileAssignedTasks()` on
+  websocket reconnect — decided "this task is dead" from that map alone. Every
+  survivor of the hand-off was therefore PATCHed to `killed` seconds after the
+  new daemon connected, destroying the work the hand-off exists to preserve.
+  This regressed three times (2026-07-23, 2026-07-31, 2026-08-31).
+
+  The daemon now hands its Fires over to its successor:
+
+  - Each tmux spawn persists a hand-off record under
+    `$CONDUCTOR_HOME/daemon/fire-sessions/`. It carries the fields the liveness
+    reaper cannot recompute — most importantly `exitMarkerToken`, a per-spawn
+    nonce without which a successor could never read a Fire's exit code.
+  - Startup enumerates surviving `conductor-fire-*` sessions and re-registers
+    them, so they regain the same watcher a freshly spawned Fire has. Both stale
+    sweeps wait for that pass before judging anything, and also adopt in place
+    any live session they find without a record.
+  - A session that outlived the Fire inside it is detected via its exit marker,
+    killed, and reported — adopting it would strand the task at `running`.
+
+  Two failure modes that used to read as "nothing is running" are now handled
+  explicitly: `tmux list-sessions` failing (a wedged server, a timeout) is no
+  longer indistinguishable from "no sessions", and a `tmux -V` probe that fails
+  once at startup no longer makes the daemon blind to tmux for its whole life.
+  Neither authorizes a kill any more.
+
+  Also fixed along the way:
+
+  - `stop_task`, `restart_task`, `refresh_session_inplace` and duplicate
+    `create_task` gated on a record's child process, which an adopted record does
+    not have. Stopping an adopted task reported it killed while leaving the Fire
+    running; restarting one could spawn a second Fire into the same worktree.
+  - `Recovered N stale task(s) to killed` counted candidates rather than
+    successes, so it claimed recovery even after the PATCH returned 409 or 500.
+  - Tasks whose spawn is still in flight are no longer eligible for stale kills.
+
+  Behaviour outside `fire_tmux_mode` is unchanged.
+
+  - @love-moon/conductor-sdk@0.11.1
+  - @love-moon/ai-sdk@0.11.1
+
 ## 0.11.0
 
 ### Minor Changes

package/bin/conductor-config.js

@@ -415,8 +415,10 @@ async function main() {
     "# Optional features",
     "# ---------------------------------------------------------------------------",
     "",
-    "# Extra Codex auth.json files to switch between from the app's account",
-    "# picker. The file name (without .json) becomes the account name.",
+    "# Optional: extra Codex auth.json files to switch between from the app's",
+    "# account picker (shown only when more than one is listed). The file name",
+    "# (without .json) becomes the account name. Without this, quota comes from",
+    "# $CODEX_HOME/auth.json (default ~/.codex/auth.json).",
     "# ai_manager:",
     "#   codex:",
     "#     auth_json:",

package/bin/conductor-daemon-update.js

@@ -0,0 +1,55 @@
+#!/usr/bin/env node
+
+/**
+ * Internal entrypoint for the built-in "Update Daemon" action.
+ *
+ * The daemon spawns this file *detached* (see `createDaemonUpdateHandlers`) and
+ * then forgets about it: the updater has to outlive the very daemon it is about
+ * to replace. It is deliberately not registered as a `conductor` subcommand —
+ * users update interactively with `conductor update`.
+ *
+ * Usage: node bin/conductor-daemon-update.js '<params-json>'
+ */
+
+import process from "node:process";
+
+import { runDaemonUpdate, writeDaemonUpdateStatus } from "../src/daemon-update.js";
+
+const raw = process.argv[2];
+if (!raw) {
+  process.stderr.write("conductor-daemon-update: missing params JSON argument\n");
+  process.exit(2);
+}
+
+let params;
+try {
+  params = JSON.parse(raw);
+} catch (error) {
+  process.stderr.write(`conductor-daemon-update: invalid params JSON: ${error?.message || error}\n`);
+  process.exit(2);
+}
+
+let result;
+try {
+  result = await runDaemonUpdate(params, {
+    writeLine: (line) => process.stdout.write(`[${new Date().toISOString()}] ${line}\n`),
+  });
+} catch (error) {
+  // The status file is how the UI learns the outcome; an unexpected crash here
+  // must not leave it stuck on "running" forever.
+  const message = error?.stack || error?.message || String(error);
+  process.stderr.write(`conductor-daemon-update: ${message}\n`);
+  writeDaemonUpdateStatus(params.statusPath, {
+    runId: params.runId ?? null,
+    status: "failed",
+    phase: "done",
+    message: "Update failed",
+    error: message,
+    logPath: params.logPath ?? null,
+    daemonRestarted: false,
+    finishedAt: new Date().toISOString(),
+  });
+  process.exit(1);
+}
+
+process.exit(result.status === "completed" ? 0 : 1);

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@love-moon/conductor-cli",
-  "version": "0.11.0",
-  "gitCommitId": "7d57852",
+  "version": "0.11.2",
+  "gitCommitId": "067735d",
   "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.11.0",
-    "@love-moon/conductor-sdk": "0.11.0",
+    "@love-moon/ai-sdk": "0.11.2",
+    "@love-moon/conductor-sdk": "0.11.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.11.0"
+    "@love-moon/chat-web": "0.11.2"
   },
   "pnpm": {
     "onlyBuiltDependencies": [