Telegram Notify
Remote Telegram lifecycle notifications for the main Hermes agent: turn start, completion with a bounded final answer, interruption/failure, and user-facing approval requests. Suppresses subagent, Telegram-origin lifecycle, and automatic/smart-approval noise. Outbound-only, no input channel.
Good to know before installing
Enabled by default once installed and reuses the core Telegram gateway's TELEGRAM_BOT_TOKEN and TELEGRAM_HOME_CHANNEL when present, so each main-agent turn's final answer (up to 3,200 chars) and approval-request command text (up to 700 chars) from CLI, Desktop and eligible gateway platforms are sent to api.telegram.org for delivery to that one chat; Telegram-origin lifecycle and approval-prompt copies (and, when notify_on_approval_response is enabled, Telegram-origin approval-response copies) are suppressed because the core Telegram gateway already delivers them in that chat; token and state are stored 0600 under HERMES_HOME/telegram-notify.
From the plugin's catalog listing.
How to install
- Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install telegram-notify - Said no? Turn it on later:
hermes plugins enable telegram-notify - Restart Hermes so it loads the plugin.
Some plugins also need a sign-in or settings: see Full setup & settings. Memory plugins ask whether to become your memory provider instead. Steps follow the official plugins guide (opens in a new tab).
- Category
- Automation & multi-agent
- Maintained by
- madpower2000 (Community)
- Needs
- No API keys declared
- Needs Hermes
- 0.21.5 or newer
- Version
- 1.1.3
- In the catalog
- 2026-09-26, updated 2026-09-27
Full setup & settings ↗Source code ↗
More in automation & multi-agent
All automation & multi-agent plugins
New Hermes Agent updates every day on X. Follow @HermesWatcher