kiro-telegram-bot 1.5.1 → 1.6.0

package/.env.example

@@ -61,6 +61,13 @@ AGENT_IMAGES_MAX=8
 # so the chat isn't silent during delegated/parallel work. true/false
 SHOW_SUBAGENTS=true
 
+# When you control several sessions at once and switch between them, deliver a
+# session's "Done" summary even while that session is in the background (you're
+# viewing another one) — clearly marked "From other session" with a short
+# created/edited/deleted file count. Set false to keep background sessions
+# silent (their output still shows when you switch back). true/false
+NOTIFY_OTHER_SESSIONS=true
+
 # ── MCP servers (/mcp) ───────────────────────────────────────────────────────
 # /mcp lists configured MCP servers, toggles them on/off, and runs a live
 # health-check (a real MCP `initialize` handshake) against each enabled server.
@@ -69,6 +76,15 @@ SHOW_SUBAGENTS=true
 # MCP_PROBE_TIMEOUT_MS=8000
 # MCP_PROBE_CONCURRENCY=6
 
+# Auto-update (default on): once an hour, check npm for a newer version with one
+# tiny request. When a newer version exists AND the bot is fully idle (no turn or
+# task running, no other active Kiro session on this PC), it announces in chat,
+# runs `npm install -g kiro-telegram-bot@latest`, restarts, and posts the new
+# release notes (tagged #update). Only applies to a global npm install. true/false
+AUTO_UPDATE=true
+# How often to check for updates, in ms (default 3600000 = 1h).
+# UPDATE_CHECK_MS=3600000
+
 # Log level: debug | info | warn | error
 LOG_LEVEL=info
 
@@ -90,6 +106,20 @@ QUIET_NOTIFICATIONS=true
 # real error is shown on every attempt; a summary is shown after the last. 0 = off.
 # PROMPT_RETRY_ATTEMPTS=5
 
+# When the retries above are exhausted on a transient error (and nothing was
+# streamed yet), automatically "logically fork" the session: open a fresh
+# continuation in the same project primed with the recent transcript, drop the
+# stuck/throttled/exhausted session, and retry the same message once. true = on.
+# AUTO_FORK_ON_ERROR=true
+
+# When a prompt fails transiently AND this session's last-known context usage is
+# at/above this percentage, skip the retry backoff and fork immediately — a
+# context-exhausted session won't recover by retrying the same oversized prompt
+# (throttling on a near-full session shows up as "-32603 … throttled"). Forking
+# compacts it into a fresh continuation primed with the recent transcript.
+# Requires AUTO_FORK_ON_ERROR. 0 disables this %-trigger. Default 85.
+# AUTO_FORK_CONTEXT_PCT=85
+
 # Where to write the log file. Defaults to <project>/logs/kiro-telegram-bot.log
 # LOG_DIR=
 # LOG_FILE=

package/CHANGELOG.md

@@ -0,0 +1,310 @@
+# Changelog
+
+All notable changes to this project are documented here. The format is based on
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project
+adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+The latest section is published verbatim as the GitHub Release notes by
+`.github/workflows/release.yml` when a `vX.Y.Z` tag is pushed.
+
+## [1.6.0] - 2026-06-23
+
+The **"always-on & self-healing"** release — the bot keeps itself up to date,
+recovers context-full sessions on its own, threads every reply to your prompt,
+and keeps the chat tidy while you drive several sessions at once.
+
+### Added
+
+- **🔄 Auto-update (`AUTO_UPDATE`, on by default).** Once an hour the bot makes
+  one tiny npm request for the latest version. When a newer one exists **and the
+  bot is fully idle** — no chat turn or scheduled task running, and no other
+  active Kiro session on the PC — it announces in chat, runs
+  `npm install -g kiro-telegram-bot@latest`, restarts, and posts the new
+  release's features/fixes **tagged `#update`** so every upgrade is easy to find.
+  It never interrupts work, and only acts on a global npm install (a source
+  checkout is left to `git`). Tunable via `UPDATE_CHECK_MS`.
+- **🏷 Threaded replies + searchable hashtags.** **Every** message of a turn —
+  each response bubble, tool call, the retry/fork notices and the Done line — is
+  now sent as a **reply to your prompt** (not just the first one), so the whole
+  turn is visually threaded to what you asked (your prompt is left untouched).
+  **Every message bubble**, including the live thinking/streaming one, ends with
+  `#proj_… #sess_…`, so tapping a tag pulls up every message for that project or
+  session. (Model and reasoning tags were dropped — they were noisy and rarely
+  useful.) Works for text, voice and photo prompts.
+- **🔁 Instant fork on a context-full session (`AUTO_FORK_CONTEXT_PCT`, default
+  85).** Sending to a session whose context is exhausted used to fail with
+  `-32603 … The request was throttled by the service` and then burn the whole
+  retry backoff (6s → 12s → 24s → 48s → 60s ≈ 2½ min) before recovering — because
+  retrying the same oversized prompt can't succeed. Now, when a prompt fails
+  transiently **and** the session's last-known context usage is at/above
+  `AUTO_FORK_CONTEXT_PCT` (or the error explicitly names a context-window
+  overflow), the bot **skips the retries and forks immediately**: it compacts the
+  conversation into a fresh continuation primed with the recent transcript and
+  retries your message once. Requires `AUTO_FORK_ON_ERROR`; set the % to `0` to
+  disable the early trigger and keep the old retry-then-fork behavior.
+- **🗂 Open any folder / safer project creation (`/projects`).** `/projects <path>`
+  now opens a session in **any existing folder** — `C:\work\app`, `/home/me/app`,
+  `~/app`, even outside your `PROJECT_ROOTS` — and **errors if the path doesn't
+  exist** (it's never created). `/projects new <name>` now **errors if the
+  project already exists** instead of silently reusing it; otherwise it creates
+  the folder and starts a session there. `/project` works as an alias.
+
+### Changed
+
+- **📄 Paginated `/projects` and `/sessions` (10 per page).** Long lists no longer
+  flood the chat — the project picker pages in place with **◀ Prev / Next ▶** and
+  a `page x/y` indicator, and session cards are shown a page at a time with the
+  same nav. Selecting an item still works across pages (absolute indexing).
+
+- **✅ "Done" summaries from other running sessions.** When you drive several
+  sessions at once and switch between them, a background session that finishes
+  now pings you — clearly marked **`📨 From other session [project · id]`** with
+  a **short** file count (`📝 +2 created · ~3 edited · −1 deleted`, or
+  `📄 No files modified`). The session you're actively viewing still gets the
+  full completion message with the list of changed paths. Toggle with the new
+  **`NOTIFY_OTHER_SESSIONS`** env var (default `true`); set it `false` to keep
+  background sessions silent (their output still shows when you switch back).
+  File operations are tracked for background turns too, so the count is accurate
+  regardless of which session you were viewing. **Switching (back) into a
+  session also replays its last Done + file summary** at the end of the catch-up
+  view (so you see how it ended), and the completion line is now more compact
+  and professional — no `end_turn`/`Files:` noise, with project-relative paths.
+- **🏷 Clearer skill & MCP tool lines.** Loading a skill now shows
+  **`📚 Loaded skill: <name>`** instead of a cryptic `SKILL.md:1` read line, and
+  MCP/extension tool calls render as **`🧩 Call MCP <server>: <method>`** (or
+  `🧩 Call MCP: <tool>` when the call carries no server name). Built-in
+  file/shell tools are never mislabelled.
+- **📁 Projects sorted by most-recently-used.** The `/projects` picker now lists
+  folders **freshest first** — ranked by the latest of the directory's modified
+  time and the newest Kiro session opened in it — so the project you were just
+  working in is at the top instead of a fixed alphabetical order.
+- **🧭 Redesigned `/running` — one card per session.** Instead of a cramped
+  combined list, each controlled session is now its own **card** with
+  **🔀 Switch · 📜 History · ✖ Close** buttons, showing its project, status, how
+  long ago it was last active, unread count, and a short preview of its first
+  prompt (reasoning directive stripped) — so you can tell sessions apart and act
+  on each one directly. The foreground session shows ▶️ Current instead of Switch.
+- **🧹 Self-cleaning navigation — a tidy history.** Menus, session/project
+  cards, pickers and submenus are now **transient**: opening a new surface (or
+  acting on one) removes the previous one, and your command / menu-button
+  messages are deleted after they're handled. Boundary markers you actually want
+  to keep — **🔀 Switched / ✨ New session / 📁 Now working in…**, agent output,
+  Done summaries and the pinned status panel — always remain, so the chat reads
+  as a clean timeline of what happened, not a pile of menus.
+
+### Fixed
+
+- **👯 Duplicate session cards in `/running`.** Tapping a session twice (or in
+  quick succession) could create **two runtimes for the same session** — the
+  add-session paths checked "already controlled?" and then `await`ed before
+  reserving the runtime, so concurrent taps both passed the check. The runtime
+  is now reserved synchronously after the check; restores and persistence dedupe
+  by session id; and `/running` prunes any existing duplicate, so the list
+  self-heals.
+- **🔣 Stray “`” in streamed messages.** An unbalanced/partial code fence in an
+  agent message could leave an orphan lone-backtick line that rendered as a
+  broken-looking single backtick. Such orphan ` / `` lines are now dropped (real
+  triple-backtick fences and inline `code` are untouched).
+- **⚡ `/btw` now runs as soon as possible.** Previously `/btw <text>` only ever
+  parked the message in the queue — so when the bot was **idle** it sat there
+  doing nothing until `/flush` or another message. It now runs **immediately
+  when idle**, and when a turn is in flight it's queued and runs **automatically
+  the moment that turn finishes** (an in-flight agent turn can't be interrupted).
+
+## [1.5.1] - 2026-06-22
+
+### Added
+
+- **📦 Install from npm** — the bot is now a published package with a global
+  CLI: `npm install -g kiro-telegram-bot` gives you the **`kiro-tg`** command
+  (alias `kiro-telegram-bot`). Multiple startup options: `kiro-tg setup`
+  (writes `.env` + auto-detects `kiro-cli`), `kiro-tg run` (foreground), and the
+  full 24/7 **service** controls — `install · status · logs · stop · restart ·
+  uninstall` — auto-detected per platform. Each instance keeps its
+  `.env`/`logs/`/`data/` in the **folder you run it from** (resolved from the
+  `--instance` the service passes, the launcher's working dir, or the cwd), so a
+  global install never writes into `node_modules`. Cloned/zip checkouts behave
+  exactly as before. `tsx` moved to runtime deps (still no build step). npm is
+  now the **primary** install option in [docs/INSTALL.md](docs/INSTALL.md).
+
+### Fixed
+
+- **🧵 Long messages split by Telegram are now stitched back together** —
+  Telegram caps a message at 4096 characters, so a long paste arrives as several
+  back-to-back messages. The bot used to treat each part as its own prompt —
+  spamming **“Queued (position 1…4)”** and even replying **“Unknown command”**
+  when a split landed on a line starting with `/`. Rapid consecutive text
+  messages are now **coalesced within a short window into a single prompt** (one
+  submission, one confirmation, in order). Tunable via `MESSAGE_BATCH_MS`
+  (default `800`; `0` disables). A genuine lone `/typo` still gets the friendly
+  “Unknown command” hint, and a failed submit now reports an error instead of
+  silently vanishing.
+
+## [1.5.0] - 2026-06-22
+
+The **"mission control"** release — manage the agent's MCP servers and watch
+its subagents from Telegram, with quieter notifications and sturdier sessions.
+
+### Added
+
+- **🧩 MCP control (`/mcp`)** — inspect and manage the agent's MCP servers from
+  Telegram. Lists every configured server with its **enabled/disabled** state,
+  transport (stdio/http) and scope (global/workspace); a **🧪 Health-check**
+  runs a real MCP `initialize` handshake against each enabled server and reports
+  which **connected** and which **failed (and why)** — connection refused,
+  timeout, HTTP status, bad transport, etc. **🔧 Enable/Disable** toggles a
+  server's `disabled` flag in its `mcp.json` (other fields preserved) and a
+  **🔄 Restart agent** button applies the change immediately. Tunable via
+  `MCP_PROBE_TIMEOUT_MS` / `MCP_PROBE_CONCURRENCY`.
+- **👥 Subagent visibility** — when the main agent delegates to subagents
+  ("crew") and goes quiet while waiting on them, the chat now **shows each
+  subagent starting, working and finishing** (via Kiro's
+  `_kiro.dev/subagent/list_update`), and the pinned status panel + `/status`
+  show a live `🤖 N running · M pending` summary. No more wondering why the
+  agent "isn't responding" mid-delegation. Toggle with `SHOW_SUBAGENTS`.
+- **🔐 Subagent permission routing** — when permission delegation is active
+  (non-trust-all mode), a permission request raised by a **subagent** is now
+  routed to its **parent chat** and clearly labelled (`Subagent "X" needs
+  approval…`), instead of being auto-decided as unattended.
+- **🔕 Quiet notifications (on by default)** — the bot now sends messages
+  **silently** (no notification sound) so streaming output and tool/status
+  chatter no longer buzz your phone. Only messages that **finish a turn**
+  (✅ Done / ⏹ Stopped / ❌ Error), **scheduled-task results**, and **permission
+  prompts** ring. Toggle with `QUIET_NOTIFICATIONS` (default `true`).
+- **🔐 Session-aware permission prompts** — when a permission request belongs to
+  a *background* session, the prompt names it ("Session X needs approval…") and
+  adds a **🔀 Switch to it** button next to Allow/Deny (which approve in place,
+  without switching). Permission prompts always ring, even in quiet mode.
+
+### Fixed
+
+- **🧭 Session-switch project mismatch** — after switching between controlled
+  sessions in different projects, the pinned status panel could show one
+  session's **project** next to another's **session id**. The panel now reads
+  the project from the live foreground session, and the persisted restore fields
+  are kept in sync on every switch, so project and session always match.
+- **🔁 Duplicated output after switching to a busy session** — following a busy
+  session's in-flight turn live and then sending a new message could echo output
+  twice (live stream + tail watcher). The follow-watch is now stopped when a new
+  turn starts streaming, and when the followed turn ends.
+- **🧷 Lost session (and context) when the agent was waiting on a reply** — if
+  the agent ended a turn asking a clarifying question and the ACP process
+  restarted during the pause before you answered (it runs 24/7, so transient
+  restarts happen), your reply could land in a **brand-new empty session**,
+  discarding the whole conversation. Re-binding a session now **retries** the
+  flaky load (the agent is usually mid-restart on the first attempt), and if the
+  session truly can't be reopened the bot **forks a linked continuation primed
+  with the recent transcript** instead of silently starting fresh — and tells
+  you it did. Context (including the pending question) survives the restart.
+
+## [1.4.0] - 2026-06-21
+
+The **"work on many sessions at once"** release — drive several Kiro sessions
+from a single chat and switch between them, on a redesigned, compact menu.
+
+### Added
+
+- **🧭 Multi-session control & switching (`/running`)** — one chat can now control
+  **several Kiro sessions at once**. Start them with 📁 Project / 🆕 New, then tap
+  **🧭 Running** (or `/running`) to jump between them. Only the foreground session
+  streams live; the rest keep running **quietly** in the background. **Switching
+  to a session shows its recent context + every message that arrived while you
+  were away** (its "unread", recovered from the session's event log). Each entry
+  shows busy/unread badges, and you can close one with ✖ (it isn't killed). The
+  controlled set and foreground survive restarts.
+
+### Changed
+
+- **🎛 Redesigned menu — compact, organized, hideable.** The bulky multi-row
+  reply keyboard is replaced by a tiny persistent bar (**☰ Menu · 🧭 Running ·
+  ⏹ Stop**) plus a clean, grouped **inline menu** opened on demand. The inline
+  menu shows the **current agent, model and reasoning** right on their buttons and
+  reopens after a change. Hide it with 🙈 and restore with `/menu` or ⌨️ Show bar.
+  All live state (project / agent / model / reasoning / context % / controlled
+  count) lives in the pinned status panel, keeping the input area uncluttered.
+
+### Verified
+
+- Re-reviewed the transient-error auto-retry path end-to-end (error
+  classification, the `6s → 12s → 24s → 48s → 60s` backoff, the "only retry while
+  nothing has streamed" guard, and cancellable waits) — confirmed logically
+  complete. (Shipped in 1.3.0; carried into this release.)
+
+## [1.3.0] - 2026-06-21
+
+### Added
+
+- **🔁 Transient-error auto-retry with backoff** — when the agent returns a
+  transient error (e.g. "high volume of traffic" / `-32603` "Internal error")
+  before any output has streamed, the bot retries with an exponential backoff
+  (`6s → 12s → 24s → 48s → 60s`) instead of failing immediately. The **real**
+  error is shown on every attempt, and a clear summary is sent once retries are
+  exhausted. Configurable via `PROMPT_RETRY_ATTEMPTS` (`0` disables; default
+  `5`); waits are interruptible with `/cancel`.
+- **🪪 Session cards** — `/sessions` and `/active` now render each session as a
+  rich card (status dot, project name + full path, created/updated times,
+  history size, context-usage %, short id) with **Resume/Continue · History ·
+  Watch** buttons, replacing the cramped button grid.
+- **📖 Install guide** — new `docs/INSTALL.md`, linked from the README and from
+  every GitHub Release.
+
+### Changed
+
+- ACP JSON-RPC errors now surface their **code and data** (and are logged), so
+  failures are diagnosable instead of an opaque "Internal error".
+- The release workflow always attaches the clean source zip and appends a
+  **1-click install** footer (with a link to the install guide) to every
+  release's notes.
+
+## [1.2.0] - 2026-06-21
+
+### Added
+
+- **👥 Contributors** — a contrib.rocks avatar wall plus "How to Contribute" and
+  "Releasing a New Version" guidance in the README.
+- **⭐ Top Contributors** — a curated table highlighting the people who shape the
+  project.
+- **📊 Stars** — a live star-history chart in the README.
+- **🌍 StarMapper** — an interactive world map of the project's stargazers.
+- **📦 Release automation** — `.github/workflows/release.yml` builds a clean,
+  downloadable source zip and publishes a GitHub Release on every `v*.*.*` tag,
+  using this CHANGELOG section as the release notes (auto-generated notes as a
+  fallback).
+- **🤖 Agent instructions** — a new `AGENTS.md` documenting the architecture,
+  conventions, and the batched-PR → conflict-resolve → merge → release workflow.
+- **📋 Release checklist** — `docs/ops/RELEASE_CHECKLIST.md` codifies the
+  pre-release validation steps.
+
+### Changed
+
+- `CONTRIBUTING.md` now describes the feature-branch → pull-request → release
+  workflow and how versioned releases are cut.
+- README roadmap updated to mark community/release tooling as shipped.
+
+## [1.1.0] - 2026-06-20
+
+### Added
+
+- Inline approvals (`session/request_permission`): approve / approve-always /
+  deny risky tool calls from Telegram buttons.
+- Account & context usage via `/usage`, plus a context-usage indicator in the
+  status panel.
+- Voice messages transcribed to prompts (configurable STT endpoint).
+
+## [1.0.0] - 2026-06-20
+
+### Added
+
+- Initial release: Telegram ⇄ Kiro CLI bridge over the Agent Client Protocol
+  (ACP) with projects, resumable and live sessions, queued follow-ups, edit
+  diffs, MarkdownV2 rendering, scheduled tasks, multi-image prompts, and a
+  cross-platform 24/7 background service.
+
+[1.6.0]: https://github.com/artickc/kiro-telegram-bot/releases/tag/v1.6.0
+[1.5.1]: https://github.com/artickc/kiro-telegram-bot/releases/tag/v1.5.1
+[1.5.0]: https://github.com/artickc/kiro-telegram-bot/releases/tag/v1.5.0
+[1.4.0]: https://github.com/artickc/kiro-telegram-bot/releases/tag/v1.4.0
+[1.3.0]: https://github.com/artickc/kiro-telegram-bot/releases/tag/v1.3.0
+[1.2.0]: https://github.com/artickc/kiro-telegram-bot/releases/tag/v1.2.0
+[1.1.0]: https://github.com/artickc/kiro-telegram-bot/releases/tag/v1.1.0
+[1.0.0]: https://github.com/artickc/kiro-telegram-bot/releases/tag/v1.0.0

package/README.md

@@ -35,7 +35,7 @@ and extended into a full multi-session client.
 | 🧩 **MCP control** | `/mcp` lists MCP servers, **health-checks** them (which connected / failed and why), and **enables/disables** them — then restarts the agent to apply. |
 | 👥 **Subagent visibility** | When Kiro delegates to subagents and waits on them, you see each one **start / work / finish** plus a live `🤖 N running` summary — and subagent permission prompts route to your chat. |
 | ⌨️ **Typing indicator** | Stays on for the whole turn, even through long tool chains. |
-| 📥 **Queued follow-ups** | Message while Kiro is busy — it's queued and runs next. `/btw` queues explicitly; `/flush` runs now. |
+| 📥 **Queued follow-ups** | Message while Kiro is busy — it's queued and runs next. `/btw` runs it ASAP (now if idle, else right after the current task); `/flush` runs the queue now. |
 | ✏️ **Edit diffs** | File edits show as unified `diff` blocks with `+N -M` stats. |
 | 💬 **Quality markdown** | Converts agent markdown to Telegram **MarkdownV2** with safe escaping and code-fence-aware splitting. |
 | 🔁 **Self-healing** | Auto-restarts the Kiro agent with backoff and re-binds your session. |
@@ -162,7 +162,7 @@ Logs are written to `logs/kiro-telegram-bot.log` (rotated at 5 MB).
 
 ```
 /menu         Show the persistent menu keyboard
-/projects     List projects · /projects <q> search · /projects new <name>
+/projects     List · /projects <q> search · /projects <path> open any folder · /projects new <name>
 /sessions     List & resume sessions (active first) · /sessions <q> to filter
 /active       Sessions running now on the PC
 /running      Sessions this chat controls — switch between them
@@ -174,7 +174,7 @@ Logs are written to `logs/kiro-telegram-bot.log` (rotated at 5 MB).
 /new          Start a fresh session here
 /status       Current session, project & queue
 /usage        Account info & current context usage
-/btw <text>   Queue a follow-up to run after the current task
+/btw <text>   Run it now if idle, else queue to run right after the current task
 /flush        Send queued follow-ups now
 /queue        Show queued follow-ups
 /clearqueue   Clear the queue
@@ -283,10 +283,15 @@ Resuming an **idle** session loads it directly so you continue the exact thread.
 | `SHOW_EDIT_DIFFS` | no | `true` | Show unified diffs for edits. |
 | `DIFF_MAX_LINES` | no | `120` | Max diff lines shown inline. |
 | `SHOW_SUBAGENTS` | no | `true` | Stream subagent (crew) start/work/finish while the main agent waits. |
+| `NOTIFY_OTHER_SESSIONS` | no | `true` | Deliver a session's "Done" summary (with a short created/edited/deleted count) even when it's a background session, marked "From other session". `false` keeps background sessions silent. |
 | `MCP_PROBE_TIMEOUT_MS` | no | `8000` | Per-server timeout for the `/mcp` live health-check. |
 | `MCP_PROBE_CONCURRENCY` | no | `6` | How many MCP health probes run at once. |
 | `ACP_AUTO_RESTART` | no | `true` | Auto-restart the agent if it exits. |
+| `AUTO_UPDATE` | no | `true` | Hourly check npm and, when a newer version exists **and the bot is idle** (no turn/task running, no other active Kiro session), auto-update + restart + post the release notes (tagged `#update`). Global npm installs only. |
+| `UPDATE_CHECK_MS` | no | `3600000` | How often to check npm for updates (ms). |
 | `PROMPT_RETRY_ATTEMPTS` | no | `5` | Max retries for a transient agent error (e.g. high-traffic / `Internal error`) before any output streamed, with `6s → 12s → 24s → 48s → 60s` backoff. The real error shows each attempt; a summary after the last. `0` disables. |
+| `AUTO_FORK_ON_ERROR` | no | `true` | When the retries above are exhausted on a transient error (throttle / `Internal error` / exhausted context) and nothing streamed, **logically fork** the session — open a fresh continuation primed with the recent transcript, drop the stuck session, and retry the message once. |
+| `AUTO_FORK_CONTEXT_PCT` | no | `85` | When a prompt fails transiently **and** the session's last-known context usage is at/above this %, **skip the retry backoff and fork immediately** — a context-exhausted session won't recover by retrying the same oversized prompt (throttling on a near-full session shows up as `-32603 … throttled`). Forking compacts it into a fresh continuation primed with the recent transcript. Requires `AUTO_FORK_ON_ERROR`; `0` disables this trigger. |
 | `LOG_LEVEL` | no | `info` | `debug` \| `info` \| `warn` \| `error`. |
 | `LOG_DIR` / `LOG_FILE` | no | `<project>/logs/…` | Log location. |
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "kiro-telegram-bot",
-  "version": "1.5.1",
+  "version": "1.6.0",
   "description": "Control Kiro CLI from Telegram over the Agent Client Protocol (ACP). Switch projects, resume and attach to live coding sessions, stream responses with diffs, queue follow-ups, and run 24/7 as a cross-platform background service.",
   "type": "module",
   "main": "src/index.ts",
@@ -14,6 +14,7 @@
     "scripts",
     "tsconfig.json",
     ".env.example",
+    "CHANGELOG.md",
     "docs"
   ],
   "engines": {

package/src/acp/client.ts

@@ -50,6 +50,23 @@ export function isTransientAcpError(err: Error): boolean {
   return TRANSIENT_RE.test(err.message);
 }
 
+/** Patterns that specifically indicate the request exceeded the model's context
+ *  window (as opposed to a generic rate-limit/backend hiccup). */
+const CONTEXT_EXHAUSTED_RE =
+  /context (?:length|window|limit|size|overflow)|maximum context|input (?:is )?too long|prompt (?:is )?too long|too many (?:input )?tokens|token limit|exceeds? (?:the )?(?:maximum|context|token)|reduce the (?:length|size)|context.{0,24}exhaust/i;
+
+/**
+ * Heuristic: did this failure come from an exhausted context window? Unlike a
+ * generic transient error, this will NOT clear by retrying the same oversized
+ * prompt — the session must be compacted/forked into a fresh, smaller context.
+ * Note: throttling on a near-full session often surfaces as a plain "-32603 …
+ * throttled" with no context keywords, so callers should *also* consult the
+ * session's tracked context-usage % (see SessionRuntime.isContextRelatedFailure).
+ */
+export function isContextExhaustedError(err: Error): boolean {
+  return CONTEXT_EXHAUSTED_RE.test(err.message);
+}
+
 /** Compact, log/Telegram-safe stringification of an error's data payload. */
 function shortJson(v: unknown): string {
   try {
@@ -202,6 +219,13 @@ export class AcpClient extends EventEmitter {
     return Boolean(this.capabilities?.loadSession);
   }
 
+  /** True while any prompt (a chat turn or a scheduled task) awaits a response —
+   *  i.e. the agent is actively working. Used to gate idle-only auto-updates. */
+  hasInflightPrompt(): boolean {
+    for (const p of this.pending.values()) if (p.method === "session/prompt") return true;
+    return false;
+  }
+
   /** PID of the bot's own kiro-cli acp process (to avoid killing ourselves). */
   get pid(): number | undefined {
     return this.proc?.pid;

package/src/app/settings-store.ts

@@ -28,4 +28,11 @@ export class SettingsStore {
     });
     return next;
   }
+
+  /** All chat ids that have interacted (for broadcast announcements). */
+  chatIds(): number[] {
+    return Object.keys(this.store.get())
+      .map(Number)
+      .filter((n) => Number.isFinite(n));
+  }
 }

package/src/app/types.ts

@@ -41,8 +41,10 @@ export interface PromptImage {
 export interface PromptInput {
   text: string;
   images: PromptImage[];
+  /** Telegram message id of the prompt, so the reply threads to it. */
+  replyTo?: number;
 }
 
-export function textPrompt(text: string): PromptInput {
-  return { text, images: [] };
+export function textPrompt(text: string, replyTo?: number): PromptInput {
+  return { text, images: [], replyTo };
 }