Bug

Verbose tool output messages (Read, Exec, etc.) are not delivered to Telegram forum topic sessions, even when verboseLevel is set to on or full. The same verbose output works correctly in Telegram DM sessions.

Environment

• OpenClaw: 2026.3.8
• Channel: Telegram (Bot API, long polling)
• Group type: Forum supergroup with topics

Reproduction

1. Configure a Telegram forum group with topics in openclaw.json:

{
  channels: {
    telegram: {
      groups: {
        "<group_id>": {
          requireMention: false,
          topics: {
            "1": {},
            "10": {}
          }
        }
      }
    }
  }
}

2. Send /verbose on (or /v full) in a forum topic — confirmed via /status that verbose is active
3. Send a message that triggers tool calls (e.g. "read today's memory notes")
4. Tool calls execute successfully (visible in session JSONL — toolCall entries with read, exec, etc.)
5. Only the final assistant reply is delivered to the topic — no verbose tool output messages appear

Expected

Verbose tool output messages should be sent to the forum topic, same as they are in DM sessions.

Observed

• Session state shows verboseLevel: "on" (confirmed in sessions.json)
• Tool calls are recorded in the session JSONL (e.g. read at 13:19:46)
• Gateway logs show only one sendMessage to the group (the final reply) — no verbose messages sent
• No errors in logs — the verbose messages are simply not dispatched, not failing
• DM sessions on the same gateway instance deliver verbose messages correctly

Possibly related

• message tool: message_thread_id not passed for Telegram forum topic delivery #27560 (message_thread_id not passed for forum topic delivery) — fixed in fix(outbound): unify resolved cfg threading across send paths #33987 (v2026.3.7+), but that fix covers the message tool send path. Verbose output may use a different delivery path that still lacks message_thread_id / topic routing.
• [Telegram] Streaming with verbose mode: text disappears on each tool call, reappears out of context #33631 (streaming + verbose text disappears on tool calls)

Workaround

None currently — verbose output only works in DM sessions.