Official issues about the Telegram integration. Sourced from the official GitHub repo; status derived from official labels; every entry links back to its source with a last-checked date.
send_message_tool's home-channel fallback only copies home.chat_id and drops home.thread_id, so bare `hermes send --to telegram` calls land in the DM root instead of the configured topic when Telegram DM topic mode is active.
The Telegram reconnect handler's updater.stop() call has no timeout, so when the underlying TCP socket is stuck in CLOSE-WAIT the polling task never wakes up, permanently blocking reconnect attempts and silently dropping messages for hours until a manual restart.
Duplicate report of the Telegram cron-job typing indicator persisting for the full subprocess lifetime instead of stopping at message delivery; closed as a duplicate.
A cron job's Telegram delivery keeps the typing indicator active for the entire lifetime of the job's subprocess rather than stopping once the delivery message is sent, which can last 30-60+ minutes for long-running jobs.
The Telegram gateway adapter hangs indefinitely at connect attempt 1/8 with the 30s asyncio.wait_for timeout never firing, but only under s6-overlay supervision per the reporter's diagnostics.
With a local Bot API server, Telegram video documents can fail caching with 'method not found', producing empty turns despite the file existing locally.
Since a prior fix (#22773), proactive cron deliveries to a Telegram threaded-DM forum topic land in the General topic instead due to a misclassification in cron/scheduler.py's DM-topic heuristic.
Cron deliveries targeting a Telegram private DM topic can fail to stay in that topic because the cron path only carries a generic thread_id, missing the metadata the adapter needs for private DM topics.
This issue proposes adding support for Telegram Bot API 10.1's new Rich Messages (headings, lists, tables, LaTeX, etc.) to the Telegram gateway, replacing the current plain/MarkdownV2 message streaming approach.
The gateway currently discards Telegram's native forwarded-message metadata (forward_origin, etc.), so the agent cannot distinguish typed text from forwarded messages; the issue proposes a platform-neutral annotation layer to preserve it.
This feature request proposes adopting several of Telegram's May 2026 bot platform updates, notably Guest AI Bots (usable via @mention without joining a chat) and Bot-to-Bot communication, to support Hermes multi-agent workflows.
Feature request for a generic, platform-agnostic API for attaching interactive action buttons (especially Telegram inline keyboards) to any message, instead of hardcoding button support per specific built-in feature.
OpenAI Codex OAuth works via CLI, but the Telegram gateway reports 'No Codex credentials stored' despite the same credentials being valid, in a Docker/Coolify deployment. This issue is now closed.
Feature request to let a single Telegram bot route messages from different forum topics/threads to different Hermes profiles (each with its own model, skills, and system prompt), instead of requiring one bot token and gateway process per profile.
Hermes sessions are isolated per platform (CLI, Telegram, iMessage) with no continuity, so work cannot be resumed across platforms; the issue proposes a built-in handoff mechanism to carry state between them.
Hermes currently only supports parallel background tasks via /background, which lacks mid-task interaction and runs sequentially; the issue requests allowing multiple Telegram bots on one account to connect to the same agent with independent sessions.
This issue reports that all Hermes gateway sessions across multiple Telegram groups or Discord servers currently share the same personality, prompt, and working directory, and proposes a topic_configs config section for per-chat overrides.
Back to curated issues . School solution cards . Troubleshooting