claude-threads 1.37.2 → 1.38.1

package/CHANGELOG.md

@@ -5,7 +5,20 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
-## [Unreleased]
+## [1.38.1] - 2026-09-24
+
+### Fixed
+- **Sessions start on Windows again** (#600). On Windows the bot spawned the Claude CLI with `shell: true`, which makes Node join the arguments into one cmd.exe command line without escaping them. The `|` in the session context passed as `--append-system-prompt` was read as a pipe, so every session exited with code 255 before Claude answered. Any other shell character in an argument had the same effect, including text from a user's message in the one-shot haiku calls, which made this a command-injection path too. Spawning now goes through the `cross-spawn` package: it runs a native `claude.exe` directly and escapes arguments for cmd.exe when the target is an npm `.cmd` shim. The auto-update installer (which spawned `npm.cmd` without a shell, rejected by Node since 20.12) and the self-respawn after an update use the same path. A new `windows-latest` CI job round-trips shell characters through a real `.cmd` shim, so this path is tested on Windows from now on.
+- **Auto-restart on Windows no longer picks the WSL `bash.exe`** (#600). `bash` on PATH is often the WSL launcher, which runs the daemon script inside Linux, where the Windows paths it gets do not exist. The bot now looks for Git for Windows' bash and starts without auto-restart, with a notice, when there is none. The daemon script also stopped using `eval` to start the bot, which dropped the backslashes from a Windows path and split any path containing a space, on macOS and Linux too.
+
+## [1.38.0] - 2026-09-24
+
+### Added
+- **`mode: assistant` names the replies-only shape** (#590, building on #505). A platform entry already carried three fields deciding how much of the bot's scaffolding a channel sees (`sessionHeader`, `stickyMessage`, `lifecycle`), and two deployments described the same combination of all three in nearly the same words. `mode` names it: `full` (default) is the current behaviour, `assistant` hides all three so Claude's reply is the whole thread. A field set explicitly still wins, so `mode: assistant` with `sessionHeader: full` means "replies only, but keep the header". The preset expands when the config loads, so everything downstream reads the same concrete values as before and omitting `mode` behaves identically to today. `turnMarker` stays outside the preset: it is a signal for integrations reading the channel, not something a human sees. Startup warns when a preset is countermanded by an explicit field, because the setup wizard writes `sessionHeader` and `stickyMessage` whenever your answer differed from the default: adding `mode: assistant` to a wizard-made config would otherwise move `lifecycle` alone while looking like it moved everything.
+
+### Fixed
+- **A failed auto-update no longer retries every second forever** (#601). When the first scheduling check already met the restart condition (quiet or scheduled mode with idle sessions, ask mode with no threads), the countdown started before the 10-second check interval existed, so that interval survived and started a second countdown. The first countdown's interval was orphaned: at zero it cleared the new one instead of itself and kept firing "ready" once a second. A successful install exits the process, so this only showed when the install failed, as two posts per second (installing, failed) for as long as the bot ran. The check interval is now armed before the first check, a running countdown is never restarted, and a countdown clears its own interval at zero.
+- **Deferring, cancelling or forcing an update now controls a running countdown** (#601). `!update defer` during the 60-second countdown left the countdown running, so the update installed anyway, and afterwards nothing re-armed the scheduler: a one-hour deferral silently became "until the next release". A deferral now stops the countdown, holds off every trigger (including late ask votes) for the window, and resumes checking when the window ends, asking again in ask mode. `!update now` during a countdown no longer installs a second time when the countdown reaches zero, and cancelling the schedule stops the countdown too.
 
 ## [1.37.2] - 2026-09-18
 

package/README.md

@@ -59,7 +59,7 @@
 - **Files both ways** - Drop any file into the chat for Claude to read, with full multimodal for images and PDFs; Claude posts screenshots, plots, or PDFs back with `send_file` (100 MB cap)
 - **Voice notes** - With `transcription:` configured (ElevenLabs Scribe), an audio clip is transcribed before Claude sees it and the transcript is echoed into the thread; see [Configuration](docs/CONFIGURATION.md#transcription-transcription)
 - **Quiet mode and verbosity dials** - `!mentions on` makes a session respond only when mentioned; session headers and the channel sticky each have `full`/`minimal`/`hidden` modes
-- **Runs on macOS, Linux, and Windows** - Windows via Git Bash or WSL
+- **Runs on macOS, Linux, and Windows** - natively or inside WSL; on native Windows, auto-restart needs Git for Windows' bash
 - **Auto-update** - The bot watches npm for new versions; `!update now` applies one from chat
 
 ## What Claude can do in your chat

package/bin/claude-threads-daemon

@@ -52,12 +52,12 @@ if [ -n "$CLAUDE_THREADS_BIN" ]; then
             echo "[daemon] Error: node not found in PATH" >&2
             exit 1
         fi
-        CLAUDE_THREADS_CMD="node $CLAUDE_THREADS_BIN"
+        CLAUDE_THREADS_CMD=(node "$CLAUDE_THREADS_BIN")
     else
-        CLAUDE_THREADS_CMD="$CLAUDE_THREADS_BIN"
+        CLAUDE_THREADS_CMD=("$CLAUDE_THREADS_BIN")
     fi
 else
-    CLAUDE_THREADS_CMD="claude-threads"
+    CLAUDE_THREADS_CMD=(claude-threads)
 fi
 
 # Track restart count
@@ -115,7 +115,7 @@ log() {
 }
 
 log "Starting claude-threads daemon"
-log "Binary: $CLAUDE_THREADS_CMD"
+log "Binary: ${CLAUDE_THREADS_CMD[*]}"
 log "Max restarts: ${MAX_RESTARTS:-unlimited}"
 log "Restart delay: ${RESTART_DELAY}s"
 log "Restart on error: $RESTART_ON_ERROR"
@@ -140,9 +140,10 @@ while true; do
     log "Starting claude-threads (restart #$restart_count)..."
 
     # Run claude-threads with any remaining arguments
-    # Note: CLAUDE_THREADS_CMD may be "bun /path/to/file.js" so we use eval
+    # An array, not eval: eval re-parses the path, dropping the backslashes
+    # of a Windows path and splitting one that contains a space (#600).
     set +e
-    eval $CLAUDE_THREADS_CMD '"$@"' &
+    "${CLAUDE_THREADS_CMD[@]}" "$@" &
     child_pid=$!
     wait $child_pid
     exit_code=$?