Files
hermes-agent/plugin-catalog/telegram-notify.yaml
madpower2000 cb5fcb0cd5 catalog: bump telegram-notify to v1.1.2
Bumps the pinned sha to the v1.1.2 release and version to 1.1.2.
v1.1.2 fixes the codex-telegram-notify attribution/link and suppresses
duplicate lifecycle notifications for Telegram-origin sessions, while
preserving existing subagent/smart-approval filtering.
2026-09-26 17:59:01 -07:00

30 lines
1.3 KiB
YAML

name: telegram-notify
repo: https://github.com/madpower2000/hermes-telegram-notify
sha: 71d0af9d8916420e4089104fcbf0c513b7870b0c
description: >-
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. Disclosure — 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 any gateway platform are sent to api.telegram.org for
delivery to that one chat; token and state are stored 0600 under HERMES_HOME/telegram-notify.
maintainer: madpower2000
tier: community
category: automation
requires_hermes: ">=0.21.5"
docs_url: https://github.com/madpower2000/hermes-telegram-notify
version: "1.1.2"
platforms: []
capabilities:
provides_tools: []
provides_hooks:
- pre_llm_call
- post_llm_call
- on_session_end
- pre_approval_request
- post_approval_response
provides_middleware: []
requires_env: []