tidal vessel
What happens:
Every subagent auto-announce to Telegram silently fails. The error is "Outbound not configured for channel: telegram" thrown in createChannelHandler() because loadChannelOutboundAdapter("telegram") returns undefined in the announce delivery code path. It hits PERMANENT_ANNOUNCE_DELIVERY_ERROR_PATTERNS, exhausts 3 retries, and drops the message. 150+ failures observed in a single day.
Root cause:
The Telegram outbound adapter isn't loaded in the plugin registry context used by sendSubagentAnnounceDirectly() → agentCommandFromIngress(). Same class of bug as the WhatsApp "active-listener" fix (global singleton pattern). Telegram's outbound adapter needs to be pinned/shared across registry contexts the same way.
Regular Telegram delivery works fine — only the announce pipeline is affected.
Workaround: Subagents manually call the message tool at task completion to send directly to Telegram.
Config fix applied (partial): announceTimeoutMs was 10s (too low for the LLM rephrase step) — bumped to 90s. Helps with timeouts but doesn't resolve the adapter issue.