Bug

System-generated messages (session reset notice after /new, echoTranscript echo) are not delivered to the correct forum topic in Telegram forum supergroups. Agent replies work fine — only system messages are affected.

Steps to reproduce

1. Create a Telegram supergroup with forum/topics enabled
2. Configure OpenClaw bot with requireMention: false
3. Send /new in the General topic
4. Observe: agent greeting arrives in the topic ✅, but the reset notice does not ❌
5. Send a voice message in the General topic with echoTranscript: true
6. Observe: agent reply arrives ✅, but transcript echo does not ❌

Root cause

buildTelegramThreadParams() in pi-embedded-*.js intentionally returns undefined when the thread ID equals TELEGRAM_GENERAL_TOPIC_ID (1):

if (normalized === TELEGRAM_GENERAL_TOPIC_ID) return;

This means system messages sent to the General topic omit message_thread_id from the Telegram API call. The Telegram API returns 200 OK, but the message does not appear in the General topic — it gets lost at the group root level.

Agent replies work because they go through a different outbound path that carries the session thread context.

Expected behavior

System messages should appear in the same topic where the triggering command/message was sent.

Environment

• OpenClaw 2026.3.23-2
• Telegram Bot API
• Forum supergroup with General topic active

Related

• Slash commands silently ignored in Telegram forum group topics #28201 (slash commands in forum topics)
• Telegram forum topic responses not delivered to chat #727 (forum topic responses not delivered)
• [Bug]: OpenClaw Telegram Topic/Thread Support Broken for Skills and Message Tool #14032 (topic/thread support for skills)