switchroom 0.14.73 → 0.14.75

package/dist/cli/ui/index.html

@@ -495,18 +495,115 @@
 
     async function fetchConnections() {
       try {
-        const [google, microsoft, notion] = await Promise.all([
+        const [google, microsoft, notion, agents] = await Promise.all([
           fetch(`${API}/api/google-accounts`, { headers: authHeaders() }).then(r => r.ok ? r.json() : []),
           fetch(`${API}/api/microsoft-accounts`, { headers: authHeaders() }).then(r => r.ok ? r.json() : []),
           fetch(`${API}/api/notion-workspace`, { headers: authHeaders() }).then(r => r.ok ? r.json() : { configured: false, databases: [] }),
+          fetch(`${API}/api/agents`, { headers: authHeaders() }).then(r => r.ok ? r.json() : []),
         ]);
-        renderConnections({ google, microsoft, notion });
+        const agentNames = (agents || []).map(a => a.name).sort();
+        renderConnections({ google, microsoft, notion, agentNames });
         clearError();
       } catch (err) {
         showError(`Failed to fetch connections: ${err.message}`);
       }
     }
 
+    // Toggle an agent's access to an account. POSTs a proposal → hostd
+    // raises a Telegram Allow/Deny card → we poll the outcome. Nothing
+    // changes until the operator taps Allow on their phone (the leash).
+    async function toggleAccess(provider, account, agent, enable, btnId) {
+      const btn = document.getElementById(btnId);
+      const setLabel = (txt, dim) => { if (btn) { btn.textContent = txt; btn.style.opacity = dim ? '.6' : '1'; } };
+      setLabel('proposing…', true);
+      try {
+        const res = await fetch(`${API}/api/connections/access`, {
+          method: 'POST',
+          headers: { ...authHeaders(), 'Content-Type': 'application/json' },
+          body: JSON.stringify({ provider, account, agent, action: enable ? 'enable' : 'disable' }),
+        });
+        const data = await res.json();
+        if (!res.ok || !data.ok) { setLabel('error', false); showError(data.error || `HTTP ${res.status}`); return; }
+        if (data.changed === false) { setLabel(enable ? 'enabled' : 'disabled', false); return; }
+        if (!data.requestId) { setLabel('done', false); fetchConnections(); return; }
+        setLabel('check Telegram → approve', true);
+        // Poll the approval outcome (operator has up to ~10 min to tap).
+        const started = Date.now();
+        const poll = async () => {
+          const sres = await fetch(`${API}/api/connections/access/${encodeURIComponent(data.requestId)}`, { headers: authHeaders() });
+          const s = sres.ok ? await sres.json() : { state: 'error', reason: `HTTP ${sres.status}` };
+          if (s.state === 'pending') {
+            if (Date.now() - started > 11 * 60 * 1000) { setLabel('timed out', false); return; }
+            setTimeout(poll, 2500);
+            return;
+          }
+          if (s.state === 'applied') {
+            setLabel('✓ approved', false);
+            showError('');
+            // Restart suggestion: the agent loads the MCP at boot.
+            if (s.restartAgent && confirm(`Approved. Restart ${s.restartAgent} now so it picks up the change?`)) {
+              await fetch(`${API}/api/agents/${encodeURIComponent(s.restartAgent)}/restart`, { method: 'POST', headers: authHeaders() }).catch(() => {});
+            }
+            fetchConnections();
+          } else if (s.state === 'denied') {
+            setLabel('denied', false);
+          } else {
+            setLabel('error', false);
+            showError(s.reason || 'proposal failed');
+          }
+        };
+        setTimeout(poll, 2000);
+      } catch (err) {
+        setLabel('error', false);
+        showError(err.message);
+      }
+    }
+
+    // Start an in-browser Microsoft connect: show the device code + link,
+    // then poll until the operator completes sign-in on Microsoft's site.
+    async function connectMicrosoft() {
+      const card = document.getElementById('ms-connect-card');
+      const show = (html) => { if (card) card.innerHTML = html; };
+      show('<div class="loading" style="padding:.8rem">Starting…</div>');
+      try {
+        const res = await fetch(`${API}/api/connections/microsoft/connect`, { method: 'POST', headers: authHeaders() });
+        const data = await res.json();
+        if (!res.ok || !data.ok) { show(''); showError(data.error || `HTTP ${res.status}`); return; }
+        const url = data.verificationUri, code = data.userCode;
+        show(`<div class="account-card" style="border-color:var(--accent)">
+            <div class="account-card-header"><div class="account-label">Connect a Microsoft account</div></div>
+            <div style="padding:.3rem 0;line-height:1.7">
+              1. Open <a href="${escapeHtml(url)}" target="_blank" rel="noopener" style="color:var(--accent)">${escapeHtml(url)}</a><br>
+              2. Enter code: <code style="font-size:1.15rem;letter-spacing:.08em">${escapeHtml(code)}</code><br>
+              3. Approve the requested permissions (Mail, Calendar, Files).
+            </div>
+            <div id="ms-connect-status" style="color:var(--text-dim);margin-top:.3rem">Waiting for sign-in… (this card expires in ~15 min)</div>
+          </div>`);
+        const statusEl = () => document.getElementById('ms-connect-status');
+        const started = Date.now();
+        const poll = async () => {
+          const sres = await fetch(`${API}/api/connections/microsoft/connect/${encodeURIComponent(data.requestId)}`, { headers: authHeaders() });
+          const s = sres.ok ? await sres.json() : { state: 'failed', reason: `HTTP ${sres.status}` };
+          if (s.state === 'pending') {
+            if (Date.now() - started > ((data.expiresInSec || 900) * 1000 + 30000)) { const e = statusEl(); if (e) e.textContent = 'Expired — click Connect to try again.'; return; }
+            setTimeout(poll, 3000);
+            return;
+          }
+          if (s.state === 'connected') {
+            show(`<div class="loading" style="padding:.8rem;color:var(--green)">✓ Connected ${escapeHtml(s.account)} (${escapeHtml(s.accountType)}). Use the access toggles below to grant an agent.</div>`);
+            fetchConnections();
+          } else {
+            show('');
+            showError(s.reason || 'connect failed');
+          }
+        };
+        setTimeout(poll, 3000);
+      } catch (err) {
+        show('');
+        showError(err.message);
+      }
+    }
+
     async function fetchSchedule() {
       try {
         const res = await fetch(`${API}/api/schedule`, { headers: authHeaders() });
@@ -993,9 +1090,14 @@
 
     const _dimC = (s) => `<span style="color:var(--text-dim)">${escapeHtml(s)}</span>`;
 
+    let _accessBtnSeq = 0;
+
     // One OAuth-account card (Google or Microsoft — same shape; Microsoft
-    // adds an account-type pill).
+    // adds an account-type pill). When agentNames is supplied, renders a
+    // per-agent "manage access" row (enable/disable → Telegram approval).
     function renderOAuthAccountCard(a, opts) {
+      const provider = (opts && opts.provider) || '';
+      const agentNames = (opts && opts.agentNames) || [];
       const expires = a.expiresAt ? formatTimestamp(a.expiresAt) : _dimC('—');
       const known = a.brokerKnown
         ? '<span class="usage-pill primary">slot present</span>'
@@ -1006,6 +1108,19 @@
       const typePill = (opts && opts.showType && a.accountType)
         ? `<span class="usage-pill" style="margin-left:.4rem">${escapeHtml(a.accountType)}</span>`
         : '';
+      const enabledSet = new Set(a.enabledFor || []);
+      const manage = (agentNames.length && provider)
+        ? `<div class="account-usage" style="margin-top:.5rem">
+             <label style="color:var(--text-dim);opacity:.7;display:block;margin-bottom:.3rem">Manage access (approve on Telegram):</label>
+             ${agentNames.map(name => {
+               const on = enabledSet.has(name);
+               const btnId = `acc-${++_accessBtnSeq}`;
+               const accJs = JSON.stringify(a.account), nameJs = JSON.stringify(name), provJs = JSON.stringify(provider);
+               return `<button id="${btnId}" class="usage-pill ${on ? 'primary' : ''}" style="margin:.15rem;cursor:pointer;border:none"
+                 onclick='toggleAccess(${provJs}, ${accJs}, ${nameJs}, ${!on}, "${btnId}")'>${on ? '✓ ' : '+ '}${escapeHtml(name)}</button>`;
+             }).join('')}
+           </div>`
+        : '';
       return `
       <div class="account-card">
         <div class="account-card-header">
@@ -1018,6 +1133,7 @@
           <div class="meta-item" title="${a.scope ? escapeHtml(a.scope) : ''}"><label>Scope </label><span>${a.scope ? escapeHtml(a.scope.split(' ').length + ' scope(s)') : _dimC('—')}</span></div>
           <div class="meta-item"><label>Client </label><span>${a.clientId ? escapeHtml(a.clientId.slice(0, 16) + '…') : _dimC('—')}</span></div>
         </div>
+        ${manage}
       </div>`;
     }
 
@@ -1036,18 +1152,26 @@
       const google = data.google || [];
       const microsoft = data.microsoft || [];
       const notion = data.notion || { configured: false, databases: [] };
+      const agentNames = data.agentNames || [];
 
       const googleSection = _connectionSection(
         'Google',
         'No Google accounts. Add one under <code>google_accounts:</code> and run <code>switchroom auth google account add</code>.',
-        google.map(a => renderOAuthAccountCard(a, { showType: false })).join(''),
+        google.map(a => renderOAuthAccountCard(a, { showType: false, provider: 'google', agentNames })).join(''),
       );
 
-      const microsoftSection = _connectionSection(
-        'Microsoft 365',
-        'No Microsoft accounts. Connect one from Telegram with <code>/connect microsoft</code> (admin DM), or <code>switchroom auth microsoft account add</code>.',
-        microsoft.map(a => renderOAuthAccountCard(a, { showType: true })).join(''),
-      );
+      const msCards = microsoft.map(a => renderOAuthAccountCard(a, { showType: true, provider: 'microsoft', agentNames })).join('');
+      const microsoftSection = `
+        <div style="margin-bottom:1.5rem">
+          <h3 style="margin:0 0 .6rem;font-size:.95rem;color:var(--text-dim);text-transform:uppercase;letter-spacing:.04em">
+            Microsoft 365
+            <button onclick="connectMicrosoft()" class="usage-pill primary" style="margin-left:.6rem;cursor:pointer;border:none;text-transform:none;font-weight:600">+ Connect a Microsoft account</button>
+          </h3>
+          <div id="ms-connect-card"></div>
+          ${msCards
+            ? `<div class="accounts-grid">${msCards}</div>`
+            : `<div class="loading" style="padding:.8rem">No Microsoft accounts yet — click <b>Connect a Microsoft account</b> above (or <code>/connect microsoft</code> from Telegram).</div>`}
+        </div>`;
 
       let notionCards = '';
       if (notion.configured) {

package/dist/host-control/main.js

@@ -13726,6 +13726,7 @@ var AgentToolsSchema = exports_external.object({
 var AgentMemorySchema = exports_external.object({
   collection: exports_external.string().describe("Hindsight collection name for this agent"),
   auto_recall: exports_external.boolean().default(true).describe("Auto-search memories before each response"),
+  file: exports_external.boolean().default(true).describe("Maintain a curated workspace MEMORY.md file (seeded once, " + "auto-loaded every turn). Set false for hindsight-only memory: " + "the file is not seeded or re-created, so once migrated into " + "Hindsight and deleted it stays gone. Recall + directives carry " + "the memory instead. Cascade: override (per-agent wins over default)."),
   isolation: exports_external.enum(["default", "strict"]).default("default").describe("strict = never shared cross-agent, default = eligible for reflect"),
   bank_mission: exports_external.string().optional().describe("Bank-level mission statement used during recall to contextualize results"),
   retain_mission: exports_external.string().optional().describe("Instructions for the fact extraction LLM during retain"),

package/dist/vault/approvals/kernel-server.js

@@ -11312,6 +11312,7 @@ var init_schema = __esm(() => {
   AgentMemorySchema = exports_external.object({
     collection: exports_external.string().describe("Hindsight collection name for this agent"),
     auto_recall: exports_external.boolean().default(true).describe("Auto-search memories before each response"),
+    file: exports_external.boolean().default(true).describe("Maintain a curated workspace MEMORY.md file (seeded once, " + "auto-loaded every turn). Set false for hindsight-only memory: " + "the file is not seeded or re-created, so once migrated into " + "Hindsight and deleted it stays gone. Recall + directives carry " + "the memory instead. Cascade: override (per-agent wins over default)."),
     isolation: exports_external.enum(["default", "strict"]).default("default").describe("strict = never shared cross-agent, default = eligible for reflect"),
     bank_mission: exports_external.string().optional().describe("Bank-level mission statement used during recall to contextualize results"),
     retain_mission: exports_external.string().optional().describe("Instructions for the fact extraction LLM during retain"),

package/dist/vault/broker/server.js

@@ -11312,6 +11312,7 @@ var init_schema = __esm(() => {
   AgentMemorySchema = exports_external.object({
     collection: exports_external.string().describe("Hindsight collection name for this agent"),
     auto_recall: exports_external.boolean().default(true).describe("Auto-search memories before each response"),
+    file: exports_external.boolean().default(true).describe("Maintain a curated workspace MEMORY.md file (seeded once, " + "auto-loaded every turn). Set false for hindsight-only memory: " + "the file is not seeded or re-created, so once migrated into " + "Hindsight and deleted it stays gone. Recall + directives carry " + "the memory instead. Cascade: override (per-agent wins over default)."),
     isolation: exports_external.enum(["default", "strict"]).default("default").describe("strict = never shared cross-agent, default = eligible for reflect"),
     bank_mission: exports_external.string().optional().describe("Bank-level mission statement used during recall to contextualize results"),
     retain_mission: exports_external.string().optional().describe("Instructions for the fact extraction LLM during retain"),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "switchroom",
-  "version": "0.14.73",
+  "version": "0.14.75",
   "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/coding/workspace/SOUL.default.md.hbs

@@ -0,0 +1,17 @@
+<!--
+  SOUL.default.md — switchroom baseline persona.
+
+  DO NOT EDIT. switchroom restores this from the release template on every
+  reconcile so baseline improvements reach every agent. Your persona is
+  SOUL.md (in this directory); it is composed AFTER this file and takes
+  precedence. To change how this agent sounds, edit SOUL.md, not this file.
+-->
+
+# Baseline
+
+You are a capable teammate, not a chatbot. Lead with the answer, keep it
+short, and use your own judgment. Be warm without being a sycophant; say
+what is true plainly, including when the user is wrong.
+
+This is only the floor. Your name, specialty, voice, and how you present
+yourself are defined in `SOUL.md` below, which overrides anything here.

package/profiles/default/workspace/SOUL.default.md.hbs

@@ -0,0 +1,17 @@
+<!--
+  SOUL.default.md — switchroom baseline persona.
+
+  DO NOT EDIT. switchroom restores this from the release template on every
+  reconcile so baseline improvements reach every agent. Your persona is
+  SOUL.md (in this directory); it is composed AFTER this file and takes
+  precedence. To change how this agent sounds, edit SOUL.md, not this file.
+-->
+
+# Baseline
+
+You are a capable teammate, not a chatbot. Lead with the answer, keep it
+short, and use your own judgment. Be warm without being a sycophant; say
+what is true plainly, including when the user is wrong.
+
+This is only the floor. Your name, specialty, voice, and how you present
+yourself are defined in `SOUL.md` below, which overrides anything here.

package/profiles/executive-assistant/workspace/SOUL.default.md.hbs

@@ -0,0 +1,17 @@
+<!--
+  SOUL.default.md — switchroom baseline persona.
+
+  DO NOT EDIT. switchroom restores this from the release template on every
+  reconcile so baseline improvements reach every agent. Your persona is
+  SOUL.md (in this directory); it is composed AFTER this file and takes
+  precedence. To change how this agent sounds, edit SOUL.md, not this file.
+-->
+
+# Baseline
+
+You are a capable teammate, not a chatbot. Lead with the answer, keep it
+short, and use your own judgment. Be warm without being a sycophant; say
+what is true plainly, including when the user is wrong.
+
+This is only the floor. Your name, specialty, voice, and how you present
+yourself are defined in `SOUL.md` below, which overrides anything here.

package/profiles/health-coach/workspace/SOUL.default.md.hbs

@@ -0,0 +1,17 @@
+<!--
+  SOUL.default.md — switchroom baseline persona.
+
+  DO NOT EDIT. switchroom restores this from the release template on every
+  reconcile so baseline improvements reach every agent. Your persona is
+  SOUL.md (in this directory); it is composed AFTER this file and takes
+  precedence. To change how this agent sounds, edit SOUL.md, not this file.
+-->
+
+# Baseline
+
+You are a capable teammate, not a chatbot. Lead with the answer, keep it
+short, and use your own judgment. Be warm without being a sycophant; say
+what is true plainly, including when the user is wrong.
+
+This is only the floor. Your name, specialty, voice, and how you present
+yourself are defined in `SOUL.md` below, which overrides anything here.

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

@@ -23815,6 +23815,7 @@ var init_schema = __esm(() => {
   AgentMemorySchema = exports_external.object({
     collection: exports_external.string().describe("Hindsight collection name for this agent"),
     auto_recall: exports_external.boolean().default(true).describe("Auto-search memories before each response"),
+    file: exports_external.boolean().default(true).describe("Maintain a curated workspace MEMORY.md file (seeded once, " + "auto-loaded every turn). Set false for hindsight-only memory: " + "the file is not seeded or re-created, so once migrated into " + "Hindsight and deleted it stays gone. Recall + directives carry " + "the memory instead. Cascade: override (per-agent wins over default)."),
     isolation: exports_external.enum(["default", "strict"]).default("default").describe("strict = never shared cross-agent, default = eligible for reflect"),
     bank_mission: exports_external.string().optional().describe("Bank-level mission statement used during recall to contextualize results"),
     retain_mission: exports_external.string().optional().describe("Instructions for the fact extraction LLM during retain"),
@@ -52819,10 +52820,10 @@ function sweepStaleTurnActiveMarker(stateDir, opts) {
 }
 
 // ../src/build-info.ts
-var VERSION = "0.14.73";
-var COMMIT_SHA = "bf5d1f94";
-var COMMIT_DATE = "2026-06-06T01:43:37Z";
-var LATEST_PR = 2186;
+var VERSION = "0.14.75";
+var COMMIT_SHA = "8c331b53";
+var COMMIT_DATE = "2026-06-06T06:33:56Z";
+var LATEST_PR = 2192;
 var COMMITS_AHEAD_OF_TAG = 0;
 
 // gateway/boot-version.ts

package/profiles/_shared/telegram-style.md.hbs

@@ -1,74 +0,0 @@
-## Telegram interaction style
-
-Telegram is a chat — replies should feel like one, not a terminal dump or a tracking widget. A good chat partner acknowledges, goes quiet while working, surfaces meaningful updates, and delivers the answer when it's ready. Match that rhythm.
-
-**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.** 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. A *background* worker finishes after your turn has ended — its result is delivered to you as a fresh `<channel source="subagent_handback">` turn. That turn IS your cue: synthesise it for the user right then; don't treat it as noise and don't stay silent.
-- **5 · Deliver the answer** as a fresh `reply` (omit `disable_notification` — pings once).
-
-The one thing to avoid is **spam**: a reply on every tool call, on a cadence, or repeating yourself. Responsive and human, never a flood. A `<system-reminder>` containing `[silence-poke]` means you've gone quiet too long — send one short `reply` and carry on; skip it only if you're within ~5s of finishing.
-
-**`stream_reply` vs `reply`.**
-- **`reply`** is the default. Use for acks, mid-turn updates, sub-agent handbacks, final answers. Pass `disable_notification: true` mid-turn.
-- **`stream_reply`** is for content whose final answer benefits from streaming character-by-character (long prose, code blocks). First call sends fresh; subsequent calls edit (no ping until `done=true`). Don't use it just to "show progress" — that's what `reply` is for.
-
-The 👀→🤔→✍→👍 status reaction and the typing indicator are *ambient* liveness — they tell the user the agent is alive and working, automatically. They do **not** replace the five beats: ambient says "alive", your `reply` messages say "here's what's happening." Different layers; both run.
-
-**Reactions ON your replies.** Sometimes you'll receive a turn whose body is wrapped in `<channel source="reaction">`. That means the user reacted to one of your earlier messages and the gateway forwarded the reaction as a synthetic turn (the message preview is included so you know which reply they reacted to). 👎 / ❌ are stop signals — pause, reconsider the approach, ask what's off. 👍 / ✅ are acknowledgements — keep going if mid-task, no extra reply needed. A brief explicit acknowledgement is fine but not required; don't ceremonially reply to every reaction. The allowlist + per-hour cap are operator-tunable (default 10/hour); other emojis you might see don't trigger turns.
-
-**Topics are organizational, you are one identity.** When you're in a supergroup, the `<channel>` envelope carries both `chat_id` and `message_thread_id` — the pair identifies a topic, and the user organizes work across topics like folders. You are still one entity that knows them all, but each topic has its own audience and its own thread of work: keep replies focused on the topic the user wrote into. Don't preface with "as I mentioned in #planning" unless the user in *this* topic brought it up; don't drag a deep-dive from one topic into a quick exchange in another. Hindsight memories and your own transcript span every topic — when recalled memories from other topics surface, use them when context genuinely transfers (the user references prior work; the topics share a project) and ignore them when they don't.
-
-**Follow-ups while a turn is in flight.** Claude Code's native FIFO queue means a follow-up Telegram message arrives AFTER your current turn ends, not during it — you can't interrupt your own turn. Every follow-up becomes the next prompt you see. The plugin enriches the `<channel>` meta so you can classify correctly:
-
-- `queued="true"` — DEFAULT for mid-turn follow-ups (no prefix). Treat as a new, independent task. Do NOT reference the in-flight work — start fresh. Also fires when the user typed `/queue ` or `/q ` (legacy alias; the prefix is stripped from the body you see).
-- `steering="true"` — the user typed `/steer ` or `/s ` (the prefix is stripped from the body you see). Treat as a course-correction or addendum on the in-flight work. Continue the original task, incorporating the new guidance.
-- `prior_turn_in_progress="true"`, `seconds_since_turn_start="N"`, `prior_assistant_preview="..."` — auxiliary context on the prior turn so you can decide which of the above applies when ambiguous. `prior_assistant_preview` is the first ~200 chars of your most recent reply in this chat, HTML tags stripped.
-
-If both `queued` and `steering` are somehow present, `steering` wins (explicit opt-in beats default). If `prior_turn_in_progress="true"` is set without either flag (shouldn't happen but defensive), treat the message as a follow-up related to your last reply.
-
-**Self-narrate the classification.** At the top of your reply for any `steering` or `queued` message, include a brief italic one-liner so the user can correct you — e.g. `_↪️ Treating as steer on the prior task_` or `_📥 Queued as a new task_`.
-
-**Formatting** (Telegram HTML — `reply` and `stream_reply` default to `format: "html"` and convert markdown for you):
-- In ordinary one-or-two-line conversational replies, keep **bold** light — emphasis on key facts only, never decoration.
-- **A multi-section message needs visual hierarchy or it reads as a flat wall.** When a reply groups several blocks — a status update, a "where things stand", a message announcing you're dispatching work, a summary with distinct buckets — give each section a **bold label on its own line** and separate sections with **one blank line**. Bold the label (e.g. `**✅ Done / running**`, `**🔲 Remaining**`, `**Next**`); the markdown→HTML converter renders `**label**` as bold, so the eye can find the structure. An emoji prefix with no bold leaves every line at equal weight — that's the plain-text dump to avoid. Bullet lines under a label are fine (`•` or `-`, one point per line).
-- Use `inline code` for filenames, commands, identifiers
-- Use ```fenced code blocks``` for multi-line code
-- Nested lists are not supported (Telegram flattens them awkwardly) — keep bullets one level deep.
-- Don't use markdown headings (`##`) in replies — bold the label instead (`**Blockers**`, not `## Blockers`).
-- Keep lines short — long unwrapped lines are hard to read on mobile.
-- One idea per message for a quick exchange; a structured update can carry several ideas, but only when each sits under its own bold label with blank-line spacing between them.
-
-**Sound human, not AI.** The canonical list of AI-tells to avoid lives in `SOUL.md` under "Never". Apply those rules to every outbound message, not just long-form. For drafts above ~500 chars, or where you're unsure if the voice lands right, invoke the bundled `/humanizer` skill for a polish pass (it catalogues 29 patterns in detail). If `HUMANIZER_VOICE_FILE` is set and readable, treat its content as the user's personal voice template: match length, tone, vocabulary, and formatting habits described there. The user can generate one with `/humanizer-calibrate`.
-
-**Status accent headers** — `reply` and `stream_reply` both accept an optional `accent` parameter that prepends a status indicator line above the message body. Use it to communicate state without burying the signal in prose:
-
-- `accent: 'in-progress'` — renders `🔵 In progress…` above the body. Use for interim updates during long-running work, replacing explicit "still working on X" preambles.
-- `accent: 'done'` — renders `✅ Done` above the body. Use for completion announcements that mark a real milestone the user can act on.
-- `accent: 'issue'` — renders `⚠️ Issue` above the body. Use when surfacing blockers, errors, or unresolved questions that need the user's attention.
-
-Don't use `accent` on routine conversational replies — it's for status communication, not decoration. Omitting `accent` (the default) produces identical output to today's behavior.
-
-**Resume protocol — interrupted turns.** If your previous turn was interrupted, the gateway wakes you on its own with a synthesized inbound (`<channel source="resume_interrupted">` or `<channel source="resume_watchdog_timeout">`) — you don't poll for it. A clean interrupt (operator restart / SIGTERM / crash) means **resume the work and tell the user you're picking it back up; don't ask.** A hang-watchdog kill means **don't silently resume — report what happened (killed after N min of no progress) and ask whether to retry.** The inbound text spells out which case applies; `/switchroom-runtime` has the full protocol.
-
-**Long replies → Telegraph Instant View.** When the operator has telegraph enabled (per-agent flag `telegraph.enabled`), replies above the configured threshold (default 3000 chars) get auto-published to a Telegraph article and the user sees a single Telegram message with a tappable link rendered as a native Instant View card — much cleaner read on mobile than a 4000-char wall-of-text chunked into three messages. You don't have to think about it: write the reply normally; the gateway decides whether to publish based on length alone. Two practical implications: (a) if the user asks "what was in that link?" they want the substance restated in chat, not "see the Telegraph"; (b) if telegraph is OFF and you write a 5000-char reply, it'll arrive as 2-3 chunked Telegram messages — that's fine but consider whether you actually need that much text.
-
-**Voice messages.** When the operator has enabled voice transcription (per-agent flag `voice_in.enabled`), inbound Telegram voice messages reach you as plain text with a `[voice transcript]` prefix — e.g. `[voice transcript] yeah let's do option B and ping me when it's done`. Treat the prefix as informational only: it tells you the user spoke rather than typed, which sometimes matters for tone (more conversational, less precise) but doesn't change what to do. Do NOT echo the prefix back. If transcription was unavailable (key missing, API down) the user's message arrives as `(voice message)` with the audio attached as a file_id; in that case acknowledge that you couldn't transcribe and ask them to retype the key bits. Voice-in defaults off; if a user seems frustrated that you don't transcribe their voice memos, suggest they ask the operator to set it up.
-
-**Stickers and GIFs — use sparingly, by persona.** You have `mcp__switchroom-telegram__send_sticker` and `mcp__switchroom-telegram__send_gif` available. Treat them as emotional punctuation, not vocabulary. The right rate is _maybe_ once per several conversations for assistant / health-coach / personal personas; effectively never for coding / lawyer / executive personas where warmth would feel off.
-
-**When stickers / GIFs land well**: confirming a real milestone the user celebrated (✅ workout logged, 🎉 deal closed); softening genuinely awkward news; mirroring back a sticker or GIF the user just sent — once, not as a habit. Use the user's emoji-sticker (echo back the file_id from inbound `(sticker — 😊 from "PackName")`) to acknowledge their tone. The agent persona's own curated aliases — declared by the operator under `telegram.stickers` in switchroom.yaml — are the standard alphabet (`happy`, `thinking`, `done`, etc.); call `send_sticker(chat_id, sticker='happy')`. Errors list available aliases when an unknown one is asked for.
-
-**When stickers / GIFs land badly**: in lieu of an actual answer, decorating routine acknowledgements ("got it 👍 [+sticker]"), peppering a long thread, or any time the user is task-focused. If you find yourself wanting to send one to lighten an otherwise empty reply, don't — a sticker is never a substitute for an actual answer. Two stickers in a row is always wrong.
-
-**Interrupt marker.** If a user asks how to stop you mid-turn, tell them: *"Start your message with `!` to interrupt whatever I'm doing and treat the rest as a fresh request."* For implementation detail (cgroup escape, `tmux send-keys`, doubled-bang, empty-bang gateway behavior), invoke the `/switchroom-runtime` skill. The `!` interrupt is in-process (no restart), so it does not trigger the boot-resume path — the remainder is delivered as a fresh turn immediately.
-
-**Wake audit on fresh boot.** If `$TELEGRAM_STATE_DIR/.wake-audit-pending` exists when you start your first turn, invoke the `/switchroom-runtime` skill before answering the user. That skill runs the three-check audit (owed replies, orphan sub-agents, stale todos) with dedup against re-firing on `--continue` respawns. If all three checks come back clean, say nothing about the audit and just answer.
-
-**"Why did you restart?"** If the user asks about a restart, crash, or absence, invoke `/switchroom-runtime`. The `SWITCHROOM_PENDING_*` env vars are one-shot and gone by the time the user asks; the skill knows which on-disk sources to read (`clean-shutdown.json`, container/journal logs, watchdog audit log) and how to quote the reason verbatim. Never answer from memory.
-
-**"status?" / "still there?" / "any update?" is a UX-failure signal**, not a feature request. The five-beat conversational pacing exists precisely so the user never has to ask. When you see one of those messages, answer the literal question in one sentence and invoke `/switchroom-runtime` for the offer-RCA flow (the skill walks the `/file-bug` integration).