Releases: artickc/kiro-telegram-bot
Releases · artickc/kiro-telegram-bot
v1.4.0
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/menuor ⌨️ 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, the6s → 12s → 24s → 48s → 60sbackoff, the "only retry while
nothing has streamed" guard, and cancellable waits) — confirmed logically
complete. (Shipped in 1.3.0; carried into this release.)
📦 Install (1-click)
- Download the
kiro-telegram-bot-<version>.zipfrom the assets below and unzip it. - Windows: double-click
install.cmd· Linux/macOS:chmod +x install.sh && ./install.sh - Set
ALLOWED_USERSin.envto your Telegram user ID.
📖 Full install guide: https://github.com/artickc/kiro-telegram-bot/blob/main/docs/INSTALL.md
v1.3.0
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 viaPROMPT_RETRY_ATTEMPTS(0disables; default
5); waits are interruptible with/cancel. - 🪪 Session cards —
/sessionsand/activenow 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.
📦 Install (1-click)
- Download the
kiro-telegram-bot-<version>.zipfrom the assets below and unzip it. - Windows: double-click
install.cmd· Linux/macOS:chmod +x install.sh && ./install.sh - Set
ALLOWED_USERSin.envto your Telegram user ID.
📖 Full install guide: https://github.com/artickc/kiro-telegram-bot/blob/main/docs/INSTALL.md
v1.2.0
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.ymlbuilds a clean,
downloadable source zip and publishes a GitHub Release on everyv*.*.*tag,
using this CHANGELOG section as the release notes (auto-generated notes as a
fallback). - 🤖 Agent instructions — a new
AGENTS.mddocumenting the architecture,
conventions, and the batched-PR → conflict-resolve → merge → release workflow. - 📋 Release checklist —
docs/ops/RELEASE_CHECKLIST.mdcodifies the
pre-release validation steps.
Changed
CONTRIBUTING.mdnow describes the feature-branch → pull-request → release
workflow and how versioned releases are cut.- README roadmap updated to mark community/release tooling as shipped.