Bug Description

In OpenClaw 2026.5.20, Telegram DM replies are intermittently not delivered to Telegram, even though the session transcript shows the messages were processed and replied to. The replies appear in the webchat UI but never reach the Telegram user.

Steps to Reproduce

1. Have a Telegram bot with an active session shared between webchat and Telegram (via same session key)
2. Send several Telegram messages in quick succession
3. Observe that some replies appear in webchat but never reach Telegram

Expected Behavior

When a reply originates from a Telegram DM turn, it should be delivered back to that same Telegram DM chat.

Actual Behavior

• Telegram inbound messages are received by the gateway (confirmed in logs)
• Session transcript shows the messages were processed and assistant replies generated
• Telegram outbound send logs: no matching send row for the affected messages
• The replies are visible in webchat because webchat polls session history, but they are never pushed to Telegram

Evidence

Log analysis:

• Inbound logs show all messages received: 18:22, 18:23, 18:24, 18:26, 18:26 (all inbound logged)
• Session transcript (jsonl) shows assistant replies for all timestamps
• Telegram outbound send: zero sends for the 18:22-18:26 window
• Later messages (18:28+) that succeed have normal outbound send logs

Transcript timeline:

10:22:27 [user] → 10:22:38 [assistant] reply in transcript, NO outbound send
10:23:52 [user] → 10:23:57 [assistant] reply in transcript, NO outbound send
10:24:45 [user] → 10:24:53 [assistant] reply in transcript, NO outbound send
10:26:33 [user] → 10:26:41 [assistant] reply in transcript, NO outbound send
10:26:50 [user] → 10:26:56 [assistant] reply in transcript, NO outbound send

Key observation: Session processing was working normally (no long task running during 18:22 window), yet Telegram delivery was completely silent for multiple consecutive messages. Webchat continued to show correct conversation because it polls the session store.

Environment

• OpenClaw: 2026.5.20 (e510042)
• Platform: macOS, gateway via launchd
• Channel: Telegram DM
• Session sharing: webchat and Telegram share agent:main:main session
• Provider: minimax/MiniMax-M2.7

Related Issues

• Bug: Signal inbound final replies can remain on Codex/internal surface instead of returning to Signal #83393 — Signal replies stay on Codex/internal surface, not delivered to Signal
• Telegram-visible message tool sends are hidden as tool cards and elided from later Codex context #83797 — Telegram message tool sends show as tool cards, not normal replies
• [Bug] Telegram group replies sent to wrong chat_id (DM instead of group) in 2026.5.7 #79308 — Telegram group replies sent to wrong chat_id
• [Feature]: sendPolicy.peerEquals: "inboundPeer" — relational predicate to constrain outbound to the current turn's inbound peer #85175 — Feature: sendPolicy.peerEquals to constrain outbound to inbound peer