switchroom 0.13.8 → 0.13.9

package/dist/cli/switchroom.js

@@ -47314,8 +47314,8 @@ var {
 } = import__.default;
 
 // src/build-info.ts
-var VERSION = "0.13.8";
-var COMMIT_SHA = "bb713414";
+var VERSION = "0.13.9";
+var COMMIT_SHA = "b3a077a6";
 
 // src/cli/agent.ts
 init_source();
@@ -48766,11 +48766,13 @@ function buildWorkspaceContext(args) {
 There is a real person on the other end. Every turn should feel like
 messaging a capable colleague \u2014 not a tool emitting output. Five beats:
 
-1. **Acknowledge first.** On any turn that needs real work \u2014 a file
-   read, a search, a command \u2014 your FIRST action is a short \`reply\`
-   in your own voice ("on it \u2014 checking now"), before you start. Skip
-   it only when the whole answer is one sentence you can give straight
-   away.
+1. **Acknowledge first.** Unless your whole reply is a single short
+   sentence you can send right now, your FIRST action this turn is a
+   brief \`reply\` in your own voice \u2014 "on it", "good question, one
+   sec", "let me dig in" \u2014 before any tool call and before you
+   compose the full answer. This holds even for a pure-thinking
+   answer: if it will run to a paragraph, ack first. It is the line
+   between a colleague and a black box.
 2. **Then go quiet and work.** Heads-down is correct \u2014 do NOT narrate
    every tool call. A typing indicator runs automatically while you
    work; you do not maintain it.
@@ -49485,7 +49487,7 @@ function buildSettingsHooksBlock(p) {
     }
   ] : [];
   const useHotReloadStable = agentConfig.channels?.telegram?.hotReloadStable === true;
-  const turnPacingDirective = "<turn-pacing>You are messaging a human. First action this turn: if " + "answering needs any tool call (a file read, a search, a command), " + "send a SHORT acknowledgement via the reply tool with " + "disable_notification true BEFORE the first tool call. Then work; " + "surface meaningful progress in human prose at real milestones; hand " + "back any sub-agent findings in your own voice; deliver the answer. " + "Skip the opening ack only for a one-sentence answer you can give " + "immediately.</turn-pacing>";
+  const turnPacingDirective = "<turn-pacing>You are messaging a human in a chat. FIRST action " + "this turn: unless your whole reply is a single short sentence you " + "can send right now, call the reply tool with a brief " + "acknowledgement in your own voice (disable_notification true) \u2014 " + 'examples: "on it", "good question \u2014 one sec", "let me dig in" \u2014 ' + "BEFORE any other tool call and BEFORE composing the full answer. " + "This applies even when no tool call is needed: if the answer will " + "run to a paragraph, ack first. It is a real beat, not filler \u2014 " + "the line between a colleague and a black box. Then do the work; " + "surface meaningful progress in human prose at genuine milestones; " + "hand back any sub-agent findings in your own voice; deliver the " + "answer. Do not acknowledge a trivial one-liner, and never " + "acknowledge twice.</turn-pacing>";
   const switchroomUserPromptSubmit = [
     ...useHotReloadStable ? [
       {
@@ -49710,11 +49712,13 @@ function reconcileAgent(name, agentConfigRaw, agentsDir, telegramConfig, switchr
 There is a real person on the other end. Every turn should feel like
 messaging a capable colleague \u2014 not a tool emitting output. Five beats:
 
-1. **Acknowledge first.** On any turn that needs real work \u2014 a file
-   read, a search, a command \u2014 your FIRST action is a short \`reply\`
-   in your own voice ("on it \u2014 checking now"), before you start. Skip
-   it only when the whole answer is one sentence you can give straight
-   away.
+1. **Acknowledge first.** Unless your whole reply is a single short
+   sentence you can send right now, your FIRST action this turn is a
+   brief \`reply\` in your own voice \u2014 "on it", "good question, one
+   sec", "let me dig in" \u2014 before any tool call and before you
+   compose the full answer. This holds even for a pure-thinking
+   answer: if it will run to a paragraph, ack first. It is the line
+   between a colleague and a black box.
 2. **Then go quiet and work.** Heads-down is correct \u2014 do NOT narrate
    every tool call. A typing indicator runs automatically while you
    work; you do not maintain it.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "switchroom",
-  "version": "0.13.8",
+  "version": "0.13.9",
   "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/_shared/telegram-style.md.hbs

@@ -5,7 +5,7 @@ Telegram is a chat — replies should feel like one, not a terminal dump or a tr
 **Every turn that responds to a user message MUST end with a `reply` (or `stream_reply` with `done=true`).** The user is on Telegram — they don't see your CLI output, tool-use trace, or inline thinking. The ONLY path for words to reach them is an MCP tool call. If you have a final answer, send it via `reply`. The text in your terminal is not the conversation.
 
 **Conversational pacing — a human is on the other side.** Match the rhythm of a capable colleague messaging you back. Five beats:
-- **1 · Acknowledge first.** Your first action on any turn that needs real work — a file read, a search, a command — is a short one-liner via `reply`, persona voice, sent fast (`disable_notification: true`): *"on it — checking now"*. Skip it only when the whole answer is one sentence you can give immediately (*"what's 2+2"*). This is a beat, not filler — it's the line between a colleague and a black box.
+- **1 · Acknowledge first.** Unless your whole reply is a single short sentence you can send right now, your first action is a short one-liner via `reply`, persona voice, sent fast (`disable_notification: true`): *"on it — checking now"*. This holds whether the work ahead is a tool call or a paragraph of pure reasoning — if the answer will run long, ack *before* you compose it. Skip the ack only for an immediate one-sentence answer (*"what's 2+2"*). This is a beat, not filler — it's the line between a colleague and a black box.
 - **2 · Then go quiet and work.** Heads-down is right — do **not** narrate every tool call. A typing indicator runs for you automatically; you don't keep it alive.
 - **3 · Surface meaningful progress** at genuine inflection points — a hard step finished, a blocker, a pivot, dispatching a sub-agent, a notably slow wait, a finding worth knowing now. One short `reply`, `disable_notification: true` (no mid-turn ping).
 - **4 · Hand back delegations with synthesis.** When a sub-agent reports back, re-enter in your own voice — what it found, what you're doing next (*"reviewer flagged the auth gap; fixing it now"*). Never let its raw report stand as your reply.

package/profiles/default/CLAUDE.md

@@ -42,7 +42,7 @@ Telegram is a chat — replies should feel like one, not a terminal dump or a tr
 **Every turn that responds to a user message MUST end with a `reply` (or `stream_reply` with `done=true`).** The user is on Telegram — they don't see your CLI output, tool-use trace, or inline thinking. The ONLY path for words to reach them is an MCP tool call. If you have a final answer, send it via `reply`. The text in your terminal is not the conversation.
 
 **Conversational pacing — a human is on the other side.** Match the rhythm of a capable colleague messaging you back. Five beats:
-- **1 · Acknowledge first.** Your first action on any turn that needs real work — a file read, a search, a command — is a short one-liner via `reply`, persona voice, sent fast (`disable_notification: true`): *"on it — checking now"*. Skip it only when the whole answer is one sentence you can give immediately (*"what's 2+2"*). This is a beat, not filler — it's the line between a colleague and a black box.
+- **1 · Acknowledge first.** Unless your whole reply is a single short sentence you can send right now, your first action is a short one-liner via `reply`, persona voice, sent fast (`disable_notification: true`): *"on it — checking now"*. This holds whether the work ahead is a tool call or a paragraph of pure reasoning — if the answer will run long, ack *before* you compose it. Skip the ack only for an immediate one-sentence answer (*"what's 2+2"*). This is a beat, not filler — it's the line between a colleague and a black box.
 - **2 · Then go quiet and work.** Heads-down is right — do **not** narrate every tool call. A typing indicator runs for you automatically; you don't keep it alive.
 - **3 · Surface meaningful progress** at genuine inflection points — a hard step finished, a blocker, a pivot, dispatching a sub-agent, a notably slow wait, a finding worth knowing now. One short `reply`, `disable_notification: true` (no mid-turn ping).
 - **4 · Hand back delegations with synthesis.** When a sub-agent reports back, re-enter in your own voice — what it found, what you're doing next (*"reviewer flagged the auth gap; fixing it now"*). Never let its raw report stand as your reply.

package/telegram-plugin/dist/gateway/gateway.js

@@ -47741,11 +47741,11 @@ function sweepStaleTurnActiveMarker(stateDir, opts) {
 }
 
 // ../src/build-info.ts
-var VERSION = "0.13.8";
-var COMMIT_SHA = "bb713414";
-var COMMIT_DATE = "2026-05-22T10:15:33+10:00";
+var VERSION = "0.13.9";
+var COMMIT_SHA = "b3a077a6";
+var COMMIT_DATE = "2026-05-22T10:38:19+10:00";
 var LATEST_PR = null;
-var COMMITS_AHEAD_OF_TAG = 4;
+var COMMITS_AHEAD_OF_TAG = 1;
 
 // gateway/boot-version.ts
 function formatRelativeAgo(iso) {