herdrchat 1.1.1 → 1.2.0

package/README.md

@@ -2,7 +2,7 @@
 
 # herdrchat
 
-Every terminal hc runs, in the chat app you already use. Feishu first.
+Every terminal hc runs, in the chat app you already use: Feishu or Telegram.
 
 [English](README.md) · [简体中文](README.zh.md)
 
@@ -16,13 +16,15 @@ herdr-app has official phone and desktop apps. But to use them away from your de
 phone has to reach the machine that runs hc, so you first need a VPN or a private network.
 And on a small phone screen, working with an agent is clumsy.
 
-Feishu is already on your phone. herdrchat connects out to Feishu by itself, so there is
-nothing to set up on your network: no public IP, no VPN. Each terminal becomes a Feishu
-group. You read what the agent says while it works, tap buttons to answer its questions,
-send and receive images, and see all terminals on one overview card. Your phone rings
-only when an agent needs you or is done. It works with any agent hc runs.
+Your chat app is already on your phone. herdrchat connects out to it by itself, so there
+is nothing to set up on your network: no public IP, no VPN. Each herdr-app tab becomes a
+Feishu group, or a topic in your private chat with the Telegram bot. You read what the
+agent says while it works, tap buttons to answer its questions, send and receive images,
+and see all terminals on one overview. A new room starts with the conversation so far.
+Your phone rings only when an agent needs you or is done. It works with any agent hc
+runs.
 
-Feishu comes first. When we have time, Slack, Discord and Telegram may follow.
+Use one app or both at once (a profile each). Slack and Discord may follow.
 
 ## Install
 
@@ -35,18 +37,22 @@ Then ask your agent:
 
 | Command | What it does |
 |---|---|
-| `/herdrchat setup` | Sets everything up with you: the Feishu app, the settings, the first start. |
+| `/herdrchat setup` | Sets everything up with you: the Feishu app or the Telegram bot, the settings, the first start. |
 | `/herdrchat status` | Says whether it runs, and what is wrong if anything is. |
 | `/herdrchat fix` | Finds the cause of a problem and fixes it. |
 | `/herdrchat config` | Changes a setting: which terminals, which groups stay quiet, tags. |
 | `/herdrchat feishu <task>` | Does a task in the Feishu developer console for you. |
+| `/herdrchat telegram <task>` | The Telegram bot, from @BotFather to the first topic. |
 
-On the command line, without an agent: `herdrchat init`, `start`, `stop`, `status`, `logs`.
+On the command line, without an agent: `herdrchat init`, `start`, `stop`, `status`, `logs`;
+`herdrchat install` runs it as a service that starts at login and comes back after a
+crash. Add `--profile <name>` for a second chat app.
 
 ## Where things are
 
-Settings in `~/.config/herdrchat/default/config.env`, everything the bot writes in
-`~/.local/state/herdrchat/default/`. Updating or reinstalling herdrchat never touches them.
+Settings in `~/.config/herdrchat/<profile>/config.env`, everything the bot writes in
+`~/.local/state/herdrchat/<profile>/` (the profile is `default` unless you name one).
+Updating or reinstalling herdrchat never touches them.
 
 How it works and every setting: [docs/guide.md](docs/guide.md).
 

package/README.zh.md

@@ -2,7 +2,7 @@
 
 # herdrchat
 
-hc 跑的每个终端，都能在你常用的聊天软件里看到和回复。先支持飞书。
+hc 跑的每个终端，都能在你常用的聊天软件里看到和回复：飞书或 Telegram。
 
 [English](README.md) · [简体中文](README.zh.md)
 
@@ -15,12 +15,13 @@ hc 跑的每个终端，都能在你常用的聊天软件里看到和回复。
 herdr-app 官方有手机端和电脑端。但想在外面用，手机得能连到跑 hc 的机器，
 所以要先折腾 VPN 或内网环境；而且在手机的小屏幕上和 agent 交互，体验并不好。
 
-飞书本来就在你手机上。herdrchat 自己主动连到飞书，网络上什么都不用配：不要公网 IP，也不要 VPN。
-每个终端就是一个飞书群：agent 干活时说的话实时可见，它问你的问题点按钮就能回答，
-图片双向都能传，所有终端汇总在一张总览卡片上。只有 agent 需要你、或者做完的时候手机才会响。
+聊天软件本来就在你手机上。herdrchat 自己主动连过去，网络上什么都不用配：不要公网 IP，也不要 VPN。
+herdr-app 的每个标签页，在飞书里是一个群，在 Telegram 里是和 bot 私聊中的一个话题：
+agent 干活时说的话实时可见，它问你的问题点按钮就能回答，图片双向都能传，所有终端汇总在一张总览里。
+新开的群或话题会先补上之前的对话。只有 agent 需要你、或者做完的时候手机才会响。
 hc 能跑的 agent 都能用，我们自己用下来非常顺畅。
 
-先支持飞书。后面有精力的话，也会考虑接入 Slack、Discord、Telegram 等其他聊天软件。
+可以只用一个，也可以两个同时用（各开一个 profile）。后面有精力的话，也会考虑接入 Slack、Discord。
 
 ## 安装
 
@@ -33,17 +34,19 @@ npm install -g herdrchat                   # skill 要用到的 herdrchat 命令
 
 | 命令 | 做什么 |
 |---|---|
-| `/herdrchat setup` | 和你一起从零配好：飞书应用、配置、第一次启动。 |
+| `/herdrchat setup` | 和你一起从零配好：飞书应用或 Telegram bot、配置、第一次启动。 |
 | `/herdrchat status` | 告诉你它在不在跑，有问题的话问题在哪。 |
 | `/herdrchat fix` | 找出问题的原因并修好。 |
 | `/herdrchat config` | 改配置：接哪些终端、哪些群保持安静、标签。 |
 | `/herdrchat feishu <任务>` | 替你在飞书开发者后台完成操作。 |
+| `/herdrchat telegram <任务>` | Telegram bot：从 @BotFather 一直到第一个话题。 |
 
-不用 agent 也可以直接在命令行里用：`herdrchat init`、`start`、`stop`、`status`、`logs`。
+不用 agent 也可以直接在命令行里用：`herdrchat init`、`start`、`stop`、`status`、`logs`；
+`herdrchat install` 把它装成系统服务，开机自动启动，崩溃后自动重启。第二个聊天软件加 `--profile <名字>`。
 
 ## 文件在哪
 
-配置在 `~/.config/herdrchat/default/config.env`，bot 写的东西都在 `~/.local/state/herdrchat/default/`。
+配置在 `~/.config/herdrchat/<profile>/config.env`，bot 写的东西都在 `~/.local/state/herdrchat/<profile>/`（没指定 profile 时就是 `default`）。
 更新或重装 herdrchat 都不会动它们。
 
 工作原理和全部配置：[docs/guide.md](docs/guide.md)（英文）。

package/bin/cli.mjs

@@ -2,12 +2,15 @@
 // herdrchat's command line: set up, start, stop and look at one profile.
 //
 //   herdrchat <command> [--profile <name>]
-//     init     make the profile's config.env from the example when it is missing
-//     start    start (or restart) it in its own hc terminal, kept running
-//     stop     stop it
-//     status   running or not, its folders, sessions, /auth, errors today
-//     logs     today's log (-n <lines>, --errors for ERROR and WARN only)
-//     run      run in the foreground (what start keeps running)
+//     init       make the profile's config.env from the example when it is missing
+//     install    run it as a service of the system (launchd, systemd): it starts at
+//                login and comes back after a crash; start, stop, status go through it
+//     uninstall  no service any more (it is stopped)
+//     start      start (or restart) it: the service, or else its own hc terminal
+//     stop       stop it
+//     status     how it runs, its folders, sessions, its chat app, errors today
+//     logs       today's log (-n <lines>, --errors for ERROR and WARN only)
+//     run        run in the foreground (what start keeps running)
 //
 // The profile is --profile or HERDRCHAT_PROFILE (default "default"); where its files are
 // is in lib/core/config.mjs.
@@ -18,12 +21,14 @@ import { fileURLToPath } from 'node:url';
 const ROOT = path.resolve(path.dirname(fileURLToPath(import.meta.url)), '..');
 const USAGE = `herdrchat <command> [--profile <name>]
 
-  init     make the profile's config.env from the example when it is missing
-  start    start (or restart) it in its own hc terminal, kept running
-  stop     stop it
-  status   running or not, its folders, sessions, /auth, errors today
-  logs     today's log (-n <lines>, --errors for ERROR and WARN only)
-  run      run in the foreground (what start keeps running)`;
+  init       make the profile's config.env from the example when it is missing
+  install    run it as a service of the system: starts at login, back after a crash
+  uninstall  no service any more (it is stopped)
+  start      start (or restart) it: the service, or else its own hc terminal
+  stop       stop it
+  status     how it runs, its folders, sessions, its chat app, errors today
+  logs       today's log (-n <lines>, --errors for ERROR and WARN only)
+  run        run in the foreground (what start keeps running)`;
 
 const argv = process.argv.slice(2);
 const flag = (name) => {
@@ -42,6 +47,7 @@ const command = argv.find((a) => !a.startsWith('-'));
 // after the profile is set: lib/core/config.mjs reads it when it loads
 const { CONFIG_FILE, STATE_DIR, loadConfig, makeDirs, placesOf } = await import('../lib/core/config.mjs');
 const { hc } = await import('../lib/core/hc.mjs');
+const { serviceOf } = await import('../lib/core/service.mjs');
 const places = placesOf();
 
 const shellQuote = (s) => `'${String(s).replace(/'/g, `'\\''`)}'`;
@@ -86,6 +92,26 @@ async function waitConnected(since) {
   return { ok: false, errors: [...new Set(errors.map((l) => l.slice(25)))].slice(-5) };
 }
 
+// What the bot needs wherever it runs (hc starts a program with the core's environment,
+// and a service with almost none): hc's full path, our PATH, the profile and the folders.
+// Nothing else, so no agent's variables come along.
+function botEnv() {
+  const hcPath = findHc();
+  if (!hcPath) throw new Error('hc is not on PATH: install herdr-core first (https://herdr.app)');
+  const env = { HERDRCHAT_HC: hcPath, HERDRCHAT_PROFILE: places.profile };
+  for (const k of ['PATH', 'HERDRCHAT_HOME', 'XDG_CONFIG_HOME', 'XDG_STATE_HOME']) if (process.env[k]) env[k] = process.env[k];
+  return env;
+}
+
+const service = () => serviceOf({ profile: places.profile, root: ROOT, node: process.execPath, env: botEnv(), stateDir: STATE_DIR });
+
+function failedToConnect(where, result) {
+  console.error(`${where} but did not reach its chat app within ${CONNECT_WAIT_MS / 1000} s.`);
+  if (result.errors.length) console.error(`Its errors:\n  ${result.errors.join('\n  ')}`);
+  console.error('It keeps retrying; `herdrchat logs --errors` shows more.');
+  process.exitCode = 1;
+}
+
 async function terminalState(session) {
   try {
     return JSON.parse(await hc(session, ['get', places.terminal, '--json'])).state;
@@ -106,53 +132,97 @@ const commands = {
     console.log(`Made ${CONFIG_FILE}: fill in the app id, the secret and HERDR_SESSIONS.`);
   },
 
+  // The service file is written again each time (a moved node or hc is picked up), and
+  // the bot in an hc terminal is stopped first: two bots would answer every message.
+  async install() {
+    const svc = service();
+    if (!svc) throw new Error(`no launchd or systemd on ${process.platform}: run \`herdrchat start\` instead`);
+    loadConfig(); // a config that cannot start the bot fails here, not in the service
+    await stopEverywhere();
+    svc.unload();
+    svc.write(svc.content);
+    const since = new Date().toISOString();
+    svc.load();
+    const result = await waitConnected(since);
+    if (!result.ok) return failedToConnect(`The ${svc.kind} service ${svc.name} is installed`, result);
+    console.log(`Installed the ${svc.kind} service ${svc.name} (${svc.file}); it is running, connected to its chat app, starts at login and comes back after a crash.`);
+    if (svc.kind === 'systemd') console.log('To keep it running after you log out: loginctl enable-linger');
+  },
+
+  async uninstall() {
+    const svc = service();
+    if (!svc?.installed()) {
+      console.log('No herdrchat service is installed for this profile.');
+      return;
+    }
+    svc.unload();
+    svc.remove();
+    console.log(`Removed the ${svc.kind} service ${svc.name}; the bot is stopped. \`herdrchat start\` runs it in an hc terminal again.`);
+  },
+
   async start() {
+    await stopEverywhere();
+    const svc = service();
+    const since = new Date().toISOString();
+    if (svc?.installed()) {
+      if (svc.loaded()) svc.restart();
+      else svc.load();
+      const result = await waitConnected(since);
+      if (!result.ok) return failedToConnect(`The ${svc.kind} service ${svc.name} started`, result);
+      console.log(`Started the ${svc.kind} service ${svc.name} (profile ${places.profile}); connected to its chat app.`);
+      return;
+    }
     const session = firstSession();
-    const hcPath = findHc();
-    if (!hcPath) throw new Error('hc is not on PATH: install herdr-core first (https://herdr.app)');
-    // hc starts a program with the core's environment, not ours, and a core started by a
-    // service may not have hc on its PATH: hc's full path, our PATH, the profile and the
-    // folders go along
-    const env = [['HERDRCHAT_HC', hcPath], ...['PATH', 'HERDRCHAT_PROFILE', 'HERDRCHAT_HOME', 'XDG_CONFIG_HOME', 'XDG_STATE_HOME'].map((k) => [k, process.env[k]])]
-      .filter(([, v]) => v)
-      .map(([k, v]) => `${k}=${shellQuote(v)}`)
-      .join(' ');
+    const env = Object.entries(botEnv()).map(([k, v]) => `${k}=${shellQuote(v)}`).join(' ');
     const run = `env ${env} ${shellQuote(process.execPath)} ${shellQuote(path.join(ROOT, 'bin', 'herdrchat.mjs'))}`;
     const loop = `while true; do ${run}; echo 'herdrchat exited, restarting in 3 s'; sleep 3; done`;
-    await stopEverywhere();
-    const since = new Date().toISOString();
     await hc(session, ['run', '--bg', '--no-parent', '--name', places.terminal, '--cwd', ROOT, '--', 'sh', '-c', loop]);
     const result = await waitConnected(since);
-    if (!result.ok) {
-      console.error(`${places.terminal} started in hc session ${session} but did not reach its chat app within ${CONNECT_WAIT_MS / 1000} s.`);
-      if (result.errors.length) console.error(`Its errors:\n  ${result.errors.join('\n  ')}`);
-      console.error('It keeps retrying; `herdrchat logs --errors` shows more.');
-      process.exitCode = 1;
-      return;
-    }
-    console.log(`Started ${places.terminal} (profile ${places.profile}) in hc session ${session}; connected to its chat app.`);
+    if (!result.ok) return failedToConnect(`${places.terminal} started in hc session ${session}`, result);
+    console.log(`Started ${places.terminal} (profile ${places.profile}) in hc session ${session}; connected to its chat app. \`herdrchat install\` makes it a service that starts at login and comes back after a crash.`);
   },
 
   async stop() {
     await stopEverywhere();
-    console.log(`Stopped ${places.terminal}. Until it starts again, nothing reaches Feishu.`);
+    const svc = service();
+    if (svc?.installed()) svc.unload(); // stays installed: \`herdrchat start\` loads it again; at login it starts again
+    console.log(`Stopped herdrchat (profile ${places.profile}). Until it starts again, nothing reaches its chat app.`);
   },
 
   async status() {
-    console.log(`profile   ${places.profile} (hc terminal ${places.terminal})`);
+    console.log(`profile   ${places.profile}`);
     console.log(`settings  ${CONFIG_FILE}${fs.existsSync(CONFIG_FILE) ? '' : '  (missing: run `herdrchat init`)'}`);
     console.log(`state     ${STATE_DIR}`);
     if (!fs.existsSync(CONFIG_FILE)) return;
     const cfg = loadConfig();
     console.log(`sessions  ${cfg.sessions.join(', ')}`);
-    console.log(`running   ${(await terminalState(cfg.sessions[0])) === 'live' ? 'yes' : 'no (`herdrchat start`)'}`);
-    let token = null;
-    try {
-      token = JSON.parse(fs.readFileSync(path.join(STATE_DIR, 'user-token.json'), 'utf8'));
-    } catch {
-      // no /auth yet
+    // how it runs: the service, an hc terminal, or not at all
+    const svc = service();
+    const inTerminal = (await terminalState(cfg.sessions[0])) === 'live';
+    if (svc?.installed()) {
+      const st = svc.state();
+      console.log(`running   ${st.running ? `yes, as the ${svc.kind} service ${svc.name}${st.pid ? ` (pid ${st.pid})` : ''}` : `no: the ${svc.kind} service ${svc.name} is stopped (\`herdrchat start\`)`}`);
+      const gone = svc.nodeGone();
+      if (gone) console.log(`          the service runs ${gone}, which is gone (node moved): \`herdrchat install\` again`);
+      if (inTerminal) console.log(`          also in hc terminal ${places.terminal}: two bots; \`herdrchat start\` keeps one`);
+    } else {
+      console.log(`running   ${inTerminal ? `yes, in hc terminal ${places.terminal} (session ${cfg.sessions[0]}); \`herdrchat install\` makes it a service` : 'no (`herdrchat start`, or `herdrchat install` for a service)'}`);
+    }
+    // what its chat app needs, without printing a secret
+    console.log(`chat      ${cfg.chat}`);
+    if (cfg.chat === 'feishu') {
+      let token = null;
+      try {
+        token = JSON.parse(fs.readFileSync(path.join(STATE_DIR, 'user-token.json'), 'utf8'));
+      } catch {
+        // no /auth yet
+      }
+      console.log(`owner     ${cfg.ownerOpenId ? 'set' : 'not set: message the bot, it says what to put in config.env'}`);
+      console.log(`/auth     ${!token ? 'not done (muting, labels and pins need it)' : (token.refreshUntil || 0) > Date.now() ? 'done' : 'expired: send /auth again'}`);
+    } else if (cfg.chat === 'telegram') {
+      console.log(`token     ${cfg.env.TELEGRAM_BOT_TOKEN ? 'set' : 'missing: TELEGRAM_BOT_TOKEN from @BotFather'}`);
+      console.log(`owner     ${cfg.env.TELEGRAM_OWNER_ID ? 'set' : 'not set: message the bot, it says what to put in config.env'}`);
     }
-    console.log(`/auth     ${!token ? 'not done' : (token.refreshUntil || 0) > Date.now() ? 'done' : 'expired: send /auth again'}`);
     const log = path.join(STATE_DIR, 'logs', `${new Date().toISOString().slice(0, 10)}.log`);
     if (fs.existsSync(log)) {
       const text = fs.readFileSync(log, 'utf8');

package/config.env.example

@@ -17,10 +17,11 @@ TELEGRAM_BOT_TOKEN=
 TELEGRAM_OWNER_ID=
 
 HERDR_SESSIONS=session-a,session-b
-# once /auth is done, spaces whose groups are muted (only an @ rings): `all` (default),
-# empty for none, or spaces, comma-separated
+# spaces whose rooms are quiet, so only "needs you" and "done" ring (Feishu: groups muted
+# once /auth is done; Telegram: silent posts): `all` (default), empty for none, or spaces,
+# comma-separated; elsewhere every post rings
 HERDR_MUTED_SPACES=all
-# spaces that do not even @-mention you (fully quiet): empty (default), `all`, or spaces
+# spaces where nothing rings, not even "needs you": empty (default), `all`, or spaces
 HERDR_SILENT_SPACES=
 # the bot's tags next to group names (tenant tags): on (default) or off
 HERDR_BOT_TAGS=on

package/lib/chats/telegram/index.mjs

@@ -1,9 +1,11 @@
 // herdrchat's Telegram side. A bot cannot make groups (no such Bot API method), so each
 // herdr-app tab is a topic in your private chat with the bot (topic mode must be on in
 // @BotFather; getMe says has_topics_enabled), and the chat's main thread is the direct
-// chat: the overview and the commands. Everything the bot posts is silent (a
-// notification without sound); `ring` sends a short reply that does sound, for "needs
-// you" and "done". The core (lib/core/engine.mjs) calls only what is returned here; the
+// chat: the overview and the commands. In a space of HERDR_MUTED_SPACES (all, by
+// default) the bot posts silently (a notification without sound) and `ring` sends a short
+// reply that sounds, for "needs you" and "done"; a bot cannot mute a chat for you, so
+// this stands in for Feishu's muted groups. Elsewhere every post sounds. A space of
+// HERDR_SILENT_SPACES never sounds. The core (lib/core/engine.mjs) calls only what is returned here; the
 // contract is lib/chats/contract.mjs.
 //
 // What Telegram does differently, and what stands in:
@@ -11,9 +13,10 @@
 //                 topic's name gets a 🔚 in front, taken off when it is live again
 //   images        a message cannot hold one, so each goes as its own photo after the text
 //   buttons       callback_data holds 64 bytes, so a button carries a short id and the
-//                 dialog it answers is kept here
+//                 dialog it answers is kept in state.json
 //   a free answer no text box on a message: you type the answer in the topic
 //   pin           a topic cannot be pinned; nothing is done
+import crypto from 'node:crypto';
 import fs from 'node:fs';
 import { createClient } from './client.mjs';
 import { escapeHtml, split, toHtml } from './format.mjs';
@@ -71,11 +74,18 @@ export function create({ cfg, store, log, logWarn, logError }) {
       const buffer = images.get(id);
       if (!buffer) continue;
       images.delete(id);
-      last = String((await tg.sendPhoto(owner, room, buffer)).message_id);
+      last = String((await tg.sendPhoto(owner, room, buffer, { silent: quiet(room) })).message_id);
     }
     return last;
   }
 
+  // Whether a room's posts go silently: its space is in HERDR_MUTED_SPACES.
+  const muted = cfg.muted || { all: true, spaces: [] };
+  function quiet(room) {
+    const c = Object.values(read().chats).find((x) => x.chat === room);
+    return !c || inSpaces(muted, spaceOfName(c.name));
+  }
+
   // HTML that Telegram refuses (an entity it cannot parse) goes again as plain text.
   async function sendText(chatId, threadId, html, plain, { silent = true, extra = {} } = {}) {
     const base = { chat_id: chatId, ...(threadId ? { message_thread_id: Number(threadId) } : {}), disable_notification: silent, link_preview_options: { is_disabled: true }, ...extra };
@@ -91,7 +101,7 @@ export function create({ cfg, store, log, logWarn, logError }) {
   async function post(room, markdown) {
     const { text, found } = takeImages(markdown);
     let last = null;
-    if (text) for (const piece of split(text)) last = String((await sendText(owner, room, toHtml(piece), piece)).message_id);
+    if (text) for (const piece of split(text)) last = String((await sendText(owner, room, toHtml(piece), piece, { silent: quiet(room) })).message_id);
     return (await sendImages(room, found)) || last;
   }
 
@@ -99,7 +109,7 @@ export function create({ cfg, store, log, logWarn, logError }) {
 
   async function postCard(room, look) {
     const { text, found } = takeImages(look.markdown);
-    const message = String((await sendText(owner, room, lookHtml({ ...look, markdown: text }), `${look.title}\n\n${text}`)).message_id);
+    const message = String((await sendText(owner, room, lookHtml({ ...look, markdown: text }), `${look.title}\n\n${text}`, { silent: quiet(room) })).message_id);
     await sendImages(room, found);
     return message;
   }
@@ -124,14 +134,17 @@ export function create({ cfg, store, log, logWarn, logError }) {
 
   // ---------- dialogs ----------
 
-  // A button carries "<id>:<pick>"; the id names the dialog's value, kept here (a click
-  // after a restart finds nothing and is told the dialog is gone).
-  const buttons = new Map();
-  let buttonN = 0;
+  // A button carries "<id>:<pick>"; the id names the dialog's value (the newest
+  // BUTTONS_KEPT; an older card is told its dialog is gone).
+  // They are kept in state.json (buttons), so a card still answers after a restart.
   function keyboard(dialog, value) {
-    const id = (buttonN += 1).toString(36);
-    buttons.set(id, { value, labels: Object.fromEntries(dialog.menu.options.map((o) => [o.n, o.label])) });
-    if (buttons.size > BUTTONS_KEPT) buttons.delete(buttons.keys().next().value);
+    const id = crypto.randomBytes(6).toString('base64url');
+    const state = read();
+    const kept = { ...(state.buttons || {}), [id]: { value, labels: Object.fromEntries(dialog.menu.options.map((o) => [o.n, o.label])) } };
+    const ids = Object.keys(kept);
+    for (const old of ids.slice(0, Math.max(0, ids.length - BUTTONS_KEPT))) delete kept[old];
+    state.buttons = kept;
+    write(state);
     const rows = [];
     for (const o of dialog.menu.options) {
       if (o === dialog.menu.free) continue;
@@ -146,7 +159,7 @@ export function create({ cfg, store, log, logWarn, logError }) {
   const doneHtml = (dialog, done) => `<b>${escapeHtml(dialog.doneTitle)}</b>\n\n${toHtml(dialog.markdown)}\n\n<b>${escapeHtml(done)}</b>`;
 
   async function postDialog(room, dialog, value) {
-    const res = await sendText(owner, room, dialogHtml(dialog), dialog.markdown, { extra: { reply_markup: keyboard(dialog, value) } });
+    const res = await sendText(owner, room, dialogHtml(dialog), dialog.markdown, { silent: quiet(room), extra: { reply_markup: keyboard(dialog, value) } });
     return String(res.message_id);
   }
 
@@ -195,10 +208,11 @@ export function create({ cfg, store, log, logWarn, logError }) {
   const pin = async (k) => { pins.add(k); };
   const unpin = async (k) => { pins.delete(k); };
 
-  // Posts are silent; this reply sounds. A space in HERDR_SILENT_SPACES never sounds.
+  // In a quiet room this reply is what sounds; in another the post sounded already. A
+  // space in HERDR_SILENT_SPACES never sounds.
   async function ring(k, message, text) {
     const c = read().chats[k];
-    if (!message || !c || inSpaces(cfg.silent, spaceOfName(c.name))) return;
+    if (!message || !c || !quiet(c.chat) || inSpaces(cfg.silent, spaceOfName(c.name))) return;
     await sendText(owner, c.chat, escapeHtml(text), text, { silent: false, extra: { reply_parameters: { message_id: Number(message), allow_sending_without_reply: true } } })
       .catch((err) => logError(`ring: ${err.message}`));
   }
@@ -316,10 +330,10 @@ export function create({ cfg, store, log, logWarn, logError }) {
     const answer = (text) => tg.call('answerCallbackQuery', { callback_query_id: q.id, text: (text || '').slice(0, 200) }).catch(() => {});
     if (String(q.from?.id) !== owner) return answer('Only the owner can answer.');
     const [id, pickRaw] = String(q.data || '').split(':');
-    const kept = buttons.get(id);
+    const kept = read().buttons?.[id];
     const message = String(q.message?.message_id || '');
     if (!kept) {
-      await edit(message, `${q.message?.text ? escapeHtml(q.message.text) : ''}\n\n<b>This dialog is gone (the bot restarted); see the newest card.</b>`, { reply_markup: { inline_keyboard: [] } }).catch(() => {});
+      await edit(message, `${q.message?.text ? escapeHtml(q.message.text) : ''}\n\n<b>This card is too old to answer; see the newest card.</b>`, { reply_markup: { inline_keyboard: [] } }).catch(() => {});
       return answer('This dialog is gone.');
     }
     const pick = /^\d+$/.test(pickRaw) ? Number(pickRaw) : pickRaw;

package/lib/core/config.mjs

@@ -12,10 +12,12 @@
 //   TELEGRAM_BOT_TOKEN               herdrchat's Telegram bot (topic mode on, in @BotFather)
 //   TELEGRAM_OWNER_ID                your Telegram user id; the only person it listens to
 //   HERDR_SESSIONS                   hc sessions to mirror, comma-separated
-//   HERDR_MUTED_SPACES               spaces whose groups are muted once /auth is done (only
-//                                    an @ rings there): `all` (default), empty for none, or
-//                                    spaces, comma-separated
-//   HERDR_SILENT_SPACES              spaces that do not even @-mention you (fully quiet):
+//   HERDR_MUTED_SPACES               spaces whose rooms are quiet, so only "needs you" and
+//                                    "done" ring (Feishu: groups muted, once /auth is done,
+//                                    and an @; Telegram: silent posts and a reply that
+//                                    rings): `all` (default), empty for none, or spaces,
+//                                    comma-separated; elsewhere every post rings
+//   HERDR_SILENT_SPACES              spaces where nothing rings, not even "needs you":
 //                                    empty (default) for none, `all`, or spaces
 //   HERDR_BOT_TAGS                   `on` (default) or `off`: the bot's tags next to group
 //                                    names (tenant tags: session or machine, and "ended")

package/lib/core/engine.mjs

@@ -248,7 +248,7 @@ export function createEngine({ cfg, chat, hc, readers, store, log, logWarn, logE
   function transcriptOf(items) {
     const parts = [];
     for (const it of items) {
-      if (it.role === 'you') parts.push(`**You** · ${clock(it.at)}\n${it.text.split('\n').map((l) => `> ${l}`).join('\n')}`);
+      if (it.role === 'you') parts.push(youOrOthers(it.text, ` · ${clock(it.at)}`));
       else if (it.role === 'ai') parts.push(it.text);
       else if (it.role === 'tool') parts.push(it.text);
       else if (it.role === 'image') parts.push(`_(an image ${it.from === 'you' ? 'you pasted' : 'it looked at'})_`);
@@ -357,6 +357,23 @@ export function createEngine({ cfg, chat, hc, readers, store, log, logWarn, logE
   // What you sent from the chat; its room shows it already, so it is not posted again.
   const fromChat = new Map();
 
+  // A message another terminal sent with `hc send` reaches the agent wrapped by hc as
+  // <hc from="t7 review" reach="...">...</hc> (any agent: hc adds it), so it is shown as
+  // from that terminal, not as yours; what is around such notes is yours.
+  const HC_NOTE = /<hc from="([^"]*)"(?:\s+reach="([^"]*)")?>([\s\S]*?)<\/hc>/g;
+  const quoted = (text) => text.split('\n').map((l) => `> ${l}`).join('\n');
+  function youOrOthers(text, at = '') {
+    const parts = [];
+    let rest = text;
+    for (const m of text.matchAll(HC_NOTE)) {
+      parts.push(`**From ${m[1]}**${at}${m[2] ? ` _(answer: ${m[2]})_` : ''}\n${quoted(m[3].trim())}`);
+      rest = rest.replace(m[0], '');
+    }
+    rest = rest.trim();
+    if (rest) parts.unshift(`**You:**${at ? ` ${at.replace(/^ · /, '')}` : ''}\n${quoted(rest)}`);
+    return parts.join('\n\n');
+  }
+
   function formatItems(k, items) {
     const sent = fromChat.get(k) || [];
     const parts = [];
@@ -380,7 +397,7 @@ export function createEngine({ cfg, chat, hc, readers, store, log, logWarn, logE
           sent.splice(i, 1);
           continue;
         }
-        parts.push(`**You:**\n${it.text.split('\n').map((l) => `> ${l}`).join('\n')}`);
+        parts.push(youOrOthers(it.text));
       } else {
         parts.push(it.text);
       }
@@ -595,6 +612,12 @@ export function createEngine({ cfg, chat, hc, readers, store, log, logWarn, logE
       if (steady) break;
     }
     const k = key(session, address);
+    // answered while its screen was being read: nothing waits, so no card
+    const nowStatus = (await hc.getTerminal(session, address).catch(() => null))?.status;
+    if (nowStatus && nowStatus.state !== 'blocked') {
+      log(`<- ${session}/${address}: no card, it no longer waits (${nowStatus.state})`);
+      return;
+    }
     if (!claimDialog(k, dialog, record.status) && !again) return;
     await closeCard(k, 'It moved on; see the next card.');
     if (!dialog.menu) {
@@ -618,9 +641,17 @@ export function createEngine({ cfg, chat, hc, readers, store, log, logWarn, logE
     log(`<- ${session}/${address}: blocked${dialog.menu ? ` (${dialog.menu.options.length} options)` : ''}`);
   }
 
+  // The keys that pick an option: its digit, or, in a question with previews (which takes
+  // no digit), the arrows from the cursor to it and Enter.
+  function pickKeys(menu, option) {
+    if (!menu.beside) return [String(option.n)];
+    const moves = option.n - (menu.cursor || 1);
+    return [...Array(Math.abs(moves)).fill(moves > 0 ? 'down' : 'up'), 'enter'];
+  }
+
   // "Type something": pick that option, then type the words.
   async function answerFree(session, address, menu, text) {
-    await hc.keys(session, address, [String(menu.free.n)]);
+    await hc.keys(session, address, pickKeys(menu, menu.free));
     await sleep(300);
     await hc.send(session, address, text, { force: true });
   }
@@ -683,7 +714,7 @@ export function createEngine({ cfg, chat, hc, readers, store, log, logWarn, logE
         await answerFree(v.s, v.a, menu, text);
         picked = text;
       } else {
-        await hc.keys(v.s, v.a, [String(option.n)]);
+        await hc.keys(v.s, v.a, pickKeys(menu, option));
         picked = `${option.n}. ${option.label}`;
       }
     }

package/lib/core/menu.mjs

@@ -13,12 +13,21 @@
 // above a multi-question dialog, which change as you answer: the same dialog keeps its key). A card click is pressed only when the
 // screen still shows the dialog with that key, so an old card can never answer a newer
 // dialog that looks alike (two permission prompts both offer "1. Yes").
+//
+// A question with previews draws a box beside its options, on the same lines, and the
+// box shows the preview of the option under the cursor: what is right of it is cut off
+// (three spaces or more, then a box line), so it is neither part of an option's label
+// nor of the key; a question's own left border (│) goes too.
 import crypto from 'node:crypto';
 
 const OPTION = /^\s*(?:❯\s*)?(\d{1,2})\.\s+(?:\[(.)\]\s+)?(.*\S)\s*$/;
 const RULE = /^[\s─╌━-]*$/;
 const BORDER = /^\s*─{10,}/;
 const FREE = /^Type something/i;
+const BESIDE = /\s{3,}[┌└│├┤┐┘╭╰─┬┴┼║╔╚].*$/u;
+const LEFT_BORDER = /^(\s*)│\s?/u;
+
+const ownPart = (line) => line.replace(BESIDE, '').replace(LEFT_BORDER, '$1');
 
 const TEXT_LINES = 15; // a dialog with no border found: this many lines above its options
 
@@ -36,7 +45,8 @@ function keyOf(lines, top, last) {
 }
 
 export function menuOf(screen) {
-  const lines = screen.split('\n');
+  const raw = screen.split('\n');
+  const lines = raw.map(ownPart);
   let run = null;
   let menu = null;
   lines.forEach((line, i) => {
@@ -54,7 +64,13 @@ export function menuOf(screen) {
   });
   if (!menu) return null;
   const top = topOf(lines, menu.first);
+  // A question with previews takes no digit (its keys say "↑/↓ to navigate"): an option
+  // is reached from the cursor (❯) with the arrows, then Enter.
+  const beside = raw.slice(menu.first, menu.last + 1).some((l) => BESIDE.test(l));
+  const cursor = menu.options.find((o, i) => raw.slice(menu.first, menu.last + 1).some((l) => /❯/.test(l) && new RegExp(`^\\s*❯\\s*${o.n}\\.`).test(l)))?.n || 1;
   return {
+    beside,
+    cursor,
     key: keyOf(lines, top, menu.last),
     framed: BORDER.test(lines[top]), // a dialog's top border; a numbered list in text has none
     text: lines.slice(top, menu.first).filter((l) => !RULE.test(l)).map((l) => l.trim()).join('\n'),

package/lib/core/service.mjs

@@ -0,0 +1,165 @@
+// herdrchat as a service of the system, so it starts at login and comes back by itself
+// after a crash, whatever happens to the hc cores: a launchd LaunchAgent on macOS, a
+// systemd user unit on Linux. `herdrchat install` makes it; start, stop and status then
+// go through it. Without it the bot runs in an hc terminal (`herdrchat start`), which
+// ends when that hc core stops.
+//
+// The service runs node and bin/herdrchat.mjs by their full paths, with only the
+// variables listed in `env` (no agent's variables come along): a node upgrade that moves
+// node needs `herdrchat install` again, which status says.
+import { execFileSync } from 'node:child_process';
+import fs from 'node:fs';
+import os from 'node:os';
+import path from 'node:path';
+
+const THROTTLE_S = 10; // launchd: at most one start in this many seconds
+const RESTART_S = 5; // systemd: wait before starting again
+
+const xml = (s) => String(s).replace(/&/g, '&amp;').replace(/</g, '&lt;').replace(/>/g, '&gt;');
+
+export function launchdPlist({ label, node, script, root, env, out }) {
+  const vars = Object.entries(env).map(([k, v]) => `      <key>${xml(k)}</key>\n      <string>${xml(v)}</string>`).join('\n');
+  return `<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
+<plist version="1.0">
+  <dict>
+    <key>Label</key>
+    <string>${xml(label)}</string>
+    <key>ProgramArguments</key>
+    <array>
+      <string>${xml(node)}</string>
+      <string>${xml(script)}</string>
+    </array>
+    <key>WorkingDirectory</key>
+    <string>${xml(root)}</string>
+    <key>EnvironmentVariables</key>
+    <dict>
+${vars}
+    </dict>
+    <key>RunAtLoad</key>
+    <true/>
+    <key>KeepAlive</key>
+    <true/>
+    <key>ThrottleInterval</key>
+    <integer>${THROTTLE_S}</integer>
+    <key>StandardOutPath</key>
+    <string>${xml(out)}</string>
+    <key>StandardErrorPath</key>
+    <string>${xml(out)}</string>
+  </dict>
+</plist>
+`;
+}
+
+const unitQuote = (s) => `"${String(s).replace(/\\/g, '\\\\').replace(/"/g, '\\"')}"`;
+
+export function systemdUnit({ profile, node, script, root, env, out }) {
+  return `[Unit]
+Description=herdrchat (profile ${profile}): herdr-app tabs in a chat app
+After=network-online.target
+
+[Service]
+ExecStart=${unitQuote(node)} ${unitQuote(script)}
+WorkingDirectory=${root}
+${Object.entries(env).map(([k, v]) => `Environment=${unitQuote(`${k}=${v}`)}`).join('\n')}
+Restart=always
+RestartSec=${RESTART_S}
+StandardOutput=append:${out}
+StandardError=append:${out}
+
+[Install]
+WantedBy=default.target
+`;
+}
+
+const run = (cmd, args) => execFileSync(cmd, args, { encoding: 'utf8', stdio: ['ignore', 'pipe', 'pipe'] });
+
+// {kind, name, file, content, write, remove, installed, load, unload, restart, state,
+// nodeGone}, or null on a system with neither launchd nor systemd.
+export function serviceOf({ profile, root, node, env, stateDir, platform = process.platform, home = os.homedir() }) {
+  const script = path.join(root, 'bin', 'herdrchat.mjs');
+  const out = path.join(stateDir, 'logs', 'service.out.log');
+  const common = { profile, node, script, root, env, out };
+  if (platform === 'darwin') {
+    const label = `app.herdrchat.${profile}`;
+    const file = path.join(home, 'Library', 'LaunchAgents', `${label}.plist`);
+    const target = `gui/${process.getuid()}/${label}`;
+    return {
+      kind: 'launchd',
+      name: label,
+      file,
+      content: launchdPlist({ ...common, label }),
+      loaded() {
+        try {
+          run('launchctl', ['print', target]);
+          return true;
+        } catch {
+          return false;
+        }
+      },
+      load() { run('launchctl', ['bootstrap', `gui/${process.getuid()}`, file]); },
+      unload() { try { run('launchctl', ['bootout', target]); } catch { /* not loaded */ } },
+      restart() { run('launchctl', ['kickstart', '-k', target]); },
+      // {running, pid}
+      state() {
+        try {
+          const text = run('launchctl', ['print', target]);
+          return { running: /\bstate = running\b/.test(text), pid: Number(text.match(/\bpid = (\d+)/)?.[1]) || null };
+        } catch {
+          return { running: false, pid: null };
+        }
+      },
+      ...files(file, out),
+    };
+  }
+  if (platform === 'linux') {
+    const unit = `herdrchat-${profile}.service`;
+    const file = path.join(process.env.XDG_CONFIG_HOME || path.join(home, '.config'), 'systemd', 'user', unit);
+    const ctl = (...a) => run('systemctl', ['--user', ...a]);
+    return {
+      kind: 'systemd',
+      name: unit,
+      file,
+      content: systemdUnit(common),
+      loaded() {
+        try {
+          return ctl('is-enabled', unit).trim() === 'enabled';
+        } catch {
+          return false;
+        }
+      },
+      load() { ctl('daemon-reload'); ctl('enable', '--now', unit); },
+      unload() { try { ctl('disable', '--now', unit); } catch { /* not loaded */ } },
+      restart() { ctl('restart', unit); },
+      state() {
+        try {
+          const pid = Number(ctl('show', '-p', 'MainPID', '--value', unit).trim()) || null;
+          return { running: ctl('is-active', unit).trim() === 'active', pid };
+        } catch {
+          return { running: false, pid: null };
+        }
+      },
+      ...files(file, out),
+    };
+  }
+  return null;
+}
+
+function files(file, out) {
+  return {
+    installed: () => fs.existsSync(file),
+    write(content) {
+      fs.mkdirSync(path.dirname(file), { recursive: true });
+      fs.mkdirSync(path.dirname(out), { recursive: true, mode: 0o700 });
+      fs.writeFileSync(file, content, { mode: 0o600 });
+    },
+    remove() { fs.rmSync(file, { force: true }); },
+    // the node the installed service runs, when it is gone (a node upgrade moved it)
+    nodeGone() {
+      if (!fs.existsSync(file)) return null;
+      const text = fs.readFileSync(file, 'utf8');
+      const node = text.match(/<string>([^<]*node[^<]*)<\/string>/)?.[1] || text.match(/^ExecStart="([^"]+)"/m)?.[1];
+      return node && !fs.existsSync(node) ? node : null;
+    },
+  };
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "herdrchat",
-  "version": "1.1.1",
+  "version": "1.2.0",
   "description": "Chat front-ends for hc: every terminal hc runs, in the chat app you use",
   "repository": {
     "type": "git",

package/skills/README.md

@@ -4,6 +4,6 @@
 it to set up, run and look after herdrchat. Its commands are `/herdrchat <command>`.
 
 Each part of the system has one reference under `herdrchat/references/`, named after the
-part: a chat app (`feishu.md`, later `slack.md`, `discord.md`, `telegram.md`) or a part of
+part: a chat app (`feishu.md`, `telegram.md`, later `slack.md`, `discord.md`) or a part of
 the core (`ops.md`, later `reader.md`). New work goes into the reference of its part, or
 a new one for a new part; `SKILL.md` only lists commands and points to references.

package/skills/herdrchat/SKILL.md

@@ -1,30 +1,35 @@
 ---
 name: herdrchat
-description: Set up, run and look after herdrchat, the chat front-end for hc that mirrors every hc terminal into Feishu (one group per terminal, dialog buttons, an overview, quiet phones) - first setup with the Feishu app, start and stop, status and logs, /auth, settings, fixing problems, and the Feishu developer console (with Ego, or guided click by click). Use for anything about herdrchat or its Feishu bot, even when the user only says "set up the Feishu bot", "is it running", "it doesn't post", "mute the workers" or "publish the bot". Trigger with "/herdrchat", "/herdrchat setup", "/herdrchat status", "/herdrchat fix".
+description: Set up, run and look after herdrchat, the chat front-end for hc that mirrors every herdr-app tab into a chat app - Feishu (one group per tab) or Telegram (one topic per tab in the bot's private chat), with dialog buttons, an overview and quiet phones - first setup of either app, running both side by side, start and stop, status and logs, /auth, settings, fixing problems, the Feishu developer console and @BotFather. Use for anything about herdrchat or its Feishu or Telegram bot, even when the user only says "set up the Telegram bot", "is it running", "it doesn't post", "mute the workers" or "publish the bot". Trigger with "/herdrchat", "/herdrchat setup", "/herdrchat status", "/herdrchat fix".
 ---
 
 # herdrchat
 
-herdrchat mirrors every terminal hc runs into a chat app, Feishu first: one group per
-terminal, the conversation as it happens, dialogs as buttons, an overview in the direct
-chat. Its command is `herdrchat` (`node bin/cli.mjs` in a clone): check with
-`command -v herdrchat`; when it is missing, ask before `npm install -g herdrchat`. A
-profile (`--profile`, default `default`) keeps its settings
-in `~/.config/herdrchat/<profile>/config.env` and its state in
+herdrchat mirrors every herdr-app tab into a chat app: a group per tab in Feishu, a topic
+per tab in the bot's private chat in Telegram; the conversation as it happens, dialogs as
+buttons, an overview in the direct chat. One profile is one chat app (`HERDRCHAT_CHAT`);
+to use both, run a profile each (`--profile telegram` beside the default Feishu one).
+
+Its command is `herdrchat` (`node bin/cli.mjs` in a clone): check with `command -v
+herdrchat`; when it is missing, ask before `npm install -g herdrchat`. A profile
+(`--profile`, default `default`) keeps its settings in
+`~/.config/herdrchat/<profile>/config.env` and its state in
 `~/.local/state/herdrchat/<profile>/`; `herdrchat status` prints both.
 
 ## Commands
 
 | Command | Do |
 |---|---|
-| `/herdrchat setup` | First time, in order: `herdrchat init`; make the Feishu app (`references/feishu.md`: create, bot, scopes, events and callbacks); fill `config.env` with the user (app id, secret, `HERDR_SESSIONS`: the hc sessions herdr-app shows on this machine); `herdrchat start`; publish a version; get the user's open_id (they message the bot, it answers with it) into `FEISHU_OWNER_OPEN_ID`; start again. Optional: `/herdrchat auth`. |
+| `/herdrchat setup` | First ask which chat app (Feishu, Telegram, or both: one profile each). Telegram: `/herdrchat telegram setup`. Feishu, in order: `herdrchat init`; make the Feishu app (`references/feishu.md`: create, bot, scopes, events and callbacks); fill `config.env` with the user (app id, secret, `HERDR_SESSIONS`: the hc sessions herdr-app shows on this machine); `herdrchat start`; publish a version; get the user's open_id (they message the bot, it answers with it) into `FEISHU_OWNER_OPEN_ID`; start again. Optional: `/herdrchat auth`. |
 | `/herdrchat status` | `herdrchat status`; explain each line; on errors, `/herdrchat fix`. |
-| `/herdrchat start`, `/herdrchat stop` | Read `config.env` (its `HERDR_SESSIONS`) in one step, then `herdrchat start` / `stop` in the next; never both at once. |
+| `/herdrchat start`, `/herdrchat stop` | Read `config.env` (its `HERDR_SESSIONS`) in one step, then `herdrchat start` / `stop` in the next; never both at once. With a service installed they go through it. |
+| `/herdrchat install`, `/herdrchat uninstall` | Run it as a service of the system (launchd on macOS, systemd on Linux): it starts at login and comes back after a crash, whatever happens to the hc cores. Recommended once it works. Read the config first; after a node upgrade, install again (`herdrchat status` says so). |
 | `/herdrchat logs` | `herdrchat logs --errors` (or `-n 100`); explain them with `references/ops.md` "Logs". |
 | `/herdrchat auth` | The user sends `/auth` to the bot and allows it on Feishu's page; the app needs the user scopes in `references/feishu.md`. Then groups are muted, labels and pins follow. |
 | `/herdrchat config` | Change a setting in `config.env` with the user (sessions, `HERDR_MUTED_SPACES`, `HERDR_SILENT_SPACES`, `HERDR_BOT_TAGS`, `HERDR_USER_TAGS`, `HERDR_HISTORY`, `HERDRCHAT_CHAT`; each is explained in `config.env.example`), read the file back, then restart. |
 | `/herdrchat fix` | Find the cause from `herdrchat status`, the logs and the live result, then fix it: `references/ops.md`. |
 | `/herdrchat feishu <task>` | Anything in the Feishu developer console: scopes, callbacks, publishing, the icon, deleting an app: `references/feishu.md`. |
+| `/herdrchat telegram <task>` | The Telegram bot, as its own profile: `setup` (@BotFather, topic mode, token, owner id, first start), checking the token, quiet and silent spaces, what Telegram cannot do and what stands in: `references/telegram.md`. |
 
 With no subcommand, run `herdrchat status` and suggest the next step from it.
 
@@ -32,7 +37,8 @@ With no subcommand, run `herdrchat status` and suggest the next step from it.
 
 - Ask before anything outward-facing: publishing a version, applying scopes, deleting or
   disbanding anything, sending to a real group. One yes covers one action.
-- Never print, screenshot or paste `FEISHU_APP_SECRET` or `user-token.json`.
+- Never print, screenshot or paste `FEISHU_APP_SECRET`, `TELEGRAM_BOT_TOKEN` or
+  `user-token.json`; ask the user to paste a token into `config.env` themselves.
 - A check that decides an action runs on its own first (read the config, then start;
   scan, then commit).
 - Say what was checked on the live bot and what was not.
@@ -41,5 +47,7 @@ With no subcommand, run `herdrchat status` and suggest the next step from it.
 
 - `references/feishu.md`: the bot's app in the Feishu developer console, with Ego or as a
   guided walk-through; the scopes this bot uses.
+- `references/telegram.md`: the Telegram bot, from @BotFather to the first topic; what
+  it does differently from Feishu.
 - `references/ops.md`: running and checking the bot, its logs and state, the usual
   problems, trying a Feishu API safely, committing without a leak.

package/skills/herdrchat/references/ops.md

@@ -17,7 +17,9 @@ Below, `S` is the first session in `HERDR_SESSIONS`.
 HC_SESSION=S hc get herdrchat --json      # state "live"
 HC_SESSION=S hc read herdrchat --lines 40 # its terminal: start lines, "[feishu] connected"
 herdrchat status                              # running, folders, /auth, errors today
-herdrchat start                               # restart: stops it in every session, waits until it reaches Feishu
+herdrchat start                               # restart: stops it in every session, waits until it reaches its chat app
+herdrchat install                             # run it as a service (launchd/systemd): starts at login, back after a crash
+launchctl print gui/$(id -u)/app.herdrchat.<profile>   # the service on macOS: state, pid, last exit
 ```
 
 A restart is needed after any code or `config.env` change. It is safe: what was posted
@@ -38,7 +40,7 @@ While the bot is down the user hears nothing, so:
 
 ## Logs
 
-`D/logs/<YYYY-MM-DD>.log`, one file a day, 14 kept, lines `<time> <LEVEL> <text>`:
+`D/logs/<YYYY-MM-DD>.log`, one file a day, 14 kept, lines `<time> <LEVEL> <text>`. Run as a service, what the process printed before its log was open (a crash at start) is in `D/logs/service.out.log`:
 
 ```sh
 grep -h ERROR D/logs/*.log | tail -20   # what went wrong
@@ -90,7 +92,7 @@ Say which checks were run and which were not; "the code is there" is not "it wor
 | nothing posts | bot down, or `FEISHU_OWNER_OPEN_ID` unset | check it runs; the log says "owner not set" |
 | a button gives error 200340 | the card callback is not set up | `references/feishu.md`: events and card callbacks |
 | a dialog had no card | answered in the terminal before the card; or no numbered menu on screen | log: `blocked`; the card says `/answer` when it saw no menu |
-| the phone rings too much | not `/auth`ed, or settings | `/auth`; `HERDR_MUTED_SPACES`, `HERDR_SILENT_SPACES` |
+| the phone rings too much | Feishu: not `/auth`ed; either app: settings | Feishu `/auth`; `HERDR_MUTED_SPACES` (quiet but for needs you and done), `HERDR_SILENT_SPACES` (nothing rings), per profile |
 | a ⚠️ warning in the direct chat about acting as you | the token could not be refreshed | send `/auth` again |
 | a group keeps an old name | its terminal is not live | it renames when the terminal is back |
 | a Feishu call fails with 400 in a burst | a rate limit (tags: 5 a second) | space the calls; the bot queues tag calls |

package/skills/herdrchat/references/telegram.md

@@ -1,23 +1,77 @@
-# Telegram: setting up the bot
-
-A Telegram bot cannot make groups, so herdrchat puts each herdr-app tab in a topic of
-your private chat with the bot; the chat's main thread is the overview and the commands
-(`/ls`, `/new`, `/kill`; in a topic `/screen`, `/answer`, `/esc`). Posts are silent;
-"needs you" and "done" ring.
-
-It runs as its own profile, beside a Feishu one:
-
-1. In Telegram, message **@BotFather**: `/newbot`, pick a name and a username, and keep
-   the token it gives. Never paste the token into a chat or a log.
-2. Turn on topics for the bot in @BotFather (its mini app, "Open": the bot's settings,
-   Threaded Mode). Check: `getMe` answers `has_topics_enabled: true`.
-3. Make the profile's config: `herdrchat init --profile telegram`, then in
-   `~/.config/herdrchat/telegram/config.env` set `HERDRCHAT_CHAT=telegram`, the token as
-   `TELEGRAM_BOT_TOKEN`, and `HERDR_SESSIONS`.
-4. `herdrchat start --profile telegram`, then message the bot once: it answers with your
-   `TELEGRAM_OWNER_ID=...`. Put that in the config and start it again. The topics appear,
-   one per tab (Telegram allows about one message a second, so many tabs take a moment).
-
-Check the token without printing it: read `TELEGRAM_BOT_TOKEN` from the config in a short
-`node -e`, call `https://api.telegram.org/bot<token>/getMe`, print only `username` and
-`has_topics_enabled`.
+# Telegram: the bot, from @BotFather to the first topic
+
+A Telegram bot cannot make groups (the Bot API has no such method), so herdrchat puts each
+herdr-app tab in a **topic** of your private chat with the bot: each has its own name,
+icon color (one per space), unread count, and can be muted on its own. The chat's main
+thread holds the overview and the commands. It runs as its **own profile**, beside a
+Feishu one; each bot follows the same hc terminals, so an answer in either reaches the
+terminal, and a dialog answered in one closes its card in the other.
+
+## Setup (`/herdrchat telegram setup`)
+
+Do these in order; the user does the Telegram steps, you check each one.
+
+1. **The bot.** The user messages **@BotFather**: `/newbot`, a name, a username ending in
+   `bot`. BotFather answers with a token. The user keeps it: never ask them to paste it
+   into the chat.
+2. **Topic mode.** It is not in BotFather's `/mybots` → Bot Settings list; it is in
+   BotFather's mini app (the **Open** button at the bottom left of the BotFather chat):
+   pick the bot, turn on Threaded Mode / topics. Check it (step 5): `has_topics_enabled`
+   must be `true`, or no topic can be made.
+3. **The profile's config.** Make `~/.config/herdrchat/telegram/config.env` (folder mode
+   700, file 600) with:
+   ```
+   HERDRCHAT_CHAT=telegram
+   TELEGRAM_BOT_TOKEN=
+   TELEGRAM_OWNER_ID=
+   HERDR_SESSIONS=<the same sessions as the Feishu profile>
+   ```
+   and ask the user to paste the token after `TELEGRAM_BOT_TOKEN=` themselves
+   (`open -e <file>` opens it), no quotes, no spaces.
+4. **First start, to learn the owner.** `herdrchat start --profile telegram`; the user
+   messages the bot anything; it answers `TELEGRAM_OWNER_ID=<digits>`. The user puts that
+   in the config. Until then the bot makes no topic.
+5. **Check, without printing secrets.** In a short `node -e`: read the token from the
+   config, call `https://api.telegram.org/bot<token>/getMe`, print only `username` and
+   `has_topics_enabled`; for the owner, print only whether `TELEGRAM_OWNER_ID` is digits.
+6. **Start again.** Read the config (secrets hidden) in one step, then
+   `herdrchat start --profile telegram` in the next. One topic per tab appears; Telegram
+   takes about one message a second in a chat, so twenty tabs take twenty seconds. A new
+   topic gets the conversation before it (`HERDR_HISTORY`); `/history` in a topic posts it
+   again.
+
+## What rings
+
+The same settings as Feishu, in the Telegram profile's own config.env:
+
+- `HERDR_MUTED_SPACES` (default `all`): in these spaces posts go silently (a notification
+  without sound) and only "⚠️ needs you" and "✅ done" ring, as a short reply. Elsewhere
+  every post rings.
+- `HERDR_SILENT_SPACES` (default none): nothing rings there, not even "needs you".
+
+A bot cannot mute a chat or a topic for the user. A topic the user mutes in Telegram is
+fully quiet, "needs you" included; `HERDR_SILENT_SPACES` does the same for a whole space
+without muting each topic by hand.
+
+## What Telegram does differently
+
+| Feishu | Telegram, and what stands in |
+|---|---|
+| a group per tab | a topic per tab, in the bot's private chat |
+| an ended group gets the "ended" tag | an ended topic's name starts with 🔚 (closing a topic is documented for supergroups only) |
+| an image inside a card | each image as its own photo after the text |
+| a text box on a dialog card | type the answer in the topic |
+| tags, labels, pins, `/auth` | none (a topic cannot be pinned; a bot cannot act as the user) |
+| the overview card | one message in the main thread, edited in place |
+| `/` commands: typed | `/` shows a menu: ls, new, kill, screen, answer, esc, history |
+
+## When something is off
+
+| Seen | Cause | Do |
+|---|---|---|
+| log: `topic mode is off for @<bot>` | step 2 not done | turn it on in BotFather's mini app, check `has_topics_enabled`, start again |
+| the bot answers `Owner is not set` | `TELEGRAM_OWNER_ID` empty | step 4 |
+| `herdrchat start` says it did not reach its chat app | wrong token, or no network | check with getMe (step 5) |
+| log: `telegram poll: ... 409` | another copy polls the same token | `herdrchat stop --profile telegram`, find the other one (another machine?), start once |
+| log: `too fast, waiting N s` | Telegram's flood limit; the bot waits as told | nothing; it catches up |
+| a click answers "This dialog is gone" | the card is older than the last 300 dialog cards | answer the newest card, or in the terminal |