switchroom 0.19.11 → 0.19.13

package/dist/cli/switchroom.js

@@ -2120,7 +2120,7 @@ var init_esm = __esm(() => {
 });
 
 // src/build-info.ts
-var VERSION = "0.19.11", COMMIT_SHA = "cd60a0c0";
+var VERSION = "0.19.13", COMMIT_SHA = "fda10488";
 
 // src/cli/resolve-version.ts
 import { existsSync, readFileSync } from "node:fs";

package/dist/host-control/main.js

@@ -26664,7 +26664,7 @@ import { existsSync as existsSync9, readFileSync as readFileSync7 } from "node:f
 import { dirname as dirname5, join as join7 } from "node:path";
 
 // src/build-info.ts
-var VERSION = "0.19.11";
+var VERSION = "0.19.13";
 
 // src/cli/resolve-version.ts
 function readPackageVersion() {

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "switchroom",
   "//version": "NOT the release version — source of truth is the git tag, resolved by scripts/build.mjs:resolveVersion() (see CLAUDE.md > Standard release process). This field is stale by design and only the Layer-4 dev/non-tag fallback for build.mjs + src/cli/resolve-version.ts; do NOT bump it expecting a release to pick it up. npm-pack tarball naming needs a real version — do that as an UNCOMMITTED pack-time bump (see release step 6), never a committed one.",
-  "version": "0.19.11",
+  "version": "0.19.13",
   "description": "Run Claude Code 24/7 on your Claude Pro/Max subscription over Telegram. Open-source alternative to OpenClaw and NanoClaw — no API keys.",
   "type": "module",
   "bin": {

package/profiles/_base/cron-session.sh.hbs

@@ -69,6 +69,11 @@ fi
 export SWITCHROOM_AGENT_NAME="$CRON_NAME"
 export CLAUDE_CONFIG_DIR="$CRON_CONFIG_DIR"
 
+# Preserve pre-2.1.217 nested sub-agent behaviour for cron-fired sessions too.
+# Normally inherited from start.sh's env; set here as a belt-and-braces default
+# (honouring any value already in the env). See start.sh.hbs for rationale.
+export CLAUDE_CODE_MAX_SUBAGENT_SPAWN_DEPTH="${CLAUDE_CODE_MAX_SUBAGENT_SPAWN_DEPTH:-2}"
+
 # Defer the (now full) MCP schema set via tool-search so the cron session keeps
 # its low-context cost — the heavy servers load on demand; switchroom-telegram
 # + hindsight stay alwaysLoad. Normally inherited from start.sh's env; set here

package/profiles/_base/start.sh.hbs

@@ -532,6 +532,17 @@ export CLAUDE_CONFIG_DIR="{{agentDir}}/.claude"
 # Claude reads .credentials.json directly; the broker is the sole writer
 # of that file and updates it before claude's own refresh window opens.
 unset CLAUDE_CODE_OAUTH_TOKEN
+# Claude Code 2.1.217 turned NESTED sub-agent spawning OFF by default: a
+# sub-agent can no longer spawn its own sub-agent unless this env is set.
+# The fleet relies on multi-level worker delegation (the main session
+# dispatches @worker/@researcher, and a dispatched worker may in turn fan
+# out its own sub-agents), so we restore the pre-2.1.217 behaviour. Depth 2
+# = main → sub-agent → grandchild, which covers the one extra level the
+# fleet actually uses; there is no evidence of deeper nesting, so we don't
+# raise it further. (The companion 2.1.217 change — CLAUDE_CODE_MAX_
+# CONCURRENT_SUBAGENTS defaulting to 20 — is already compatible: our fleet
+# self-caps at 15 parallel sub-agents, so the 20 default is left untouched.)
+export CLAUDE_CODE_MAX_SUBAGENT_SPAWN_DEPTH="${CLAUDE_CODE_MAX_SUBAGENT_SPAWN_DEPTH:-2}"
 export TELEGRAM_STATE_DIR="{{agentDir}}/telegram"
 # SWITCHROOM_AGENT_NAME is the canonical "which agent am I" identifier the
 # telegram-plugin reads to detect self-restart commands. We can't rely on