Adapted community discussion: Paraphrased and condensed from an anonymized public OpenClaw Discord support conversation from September 2026. Technical guidance was reviewed for OpenClaw 2026.9.3.
I started conversations with my agents in Telegram, then continued them in the Web UI. The context is still there, but Web UI responses no longer appear in Telegram. I want continuity and, ideally, a copy of each response in both places.
Those are two different behaviors.
Continuity: Telegram and the Web UI can show the same Gateway-owned conversation when both connect to the same Gateway, agent, and existing main session. Opening a new or incognito thread creates a different session.
Delivery: A reply normally returns to the surface that received that turn. A Telegram prompt gets a Telegram reply, and a Web UI prompt gets a Web UI reply. Shared session context does not automatically duplicate delivery across channels.
If a later Telegram prompt receives no response at all, that is a routing or channel problem. If only Web UI replies are missing from Telegram, the system is behaving normally and mirroring needs an explicit outbound action.
It is the second case. Telegram prompts still work. I specifically want a Web UI response mirrored to my Telegram chat. How should I set that up?
Use an explicit message broadcast for the second delivery. Preview the destination and payload first:
openclaw message broadcast \
--channel telegram \
--targets TELEGRAM_CHAT_ID \
--message "Response text" \
--dry-run --json
Remove --dry-run only after the exact recipient, content, and timing are authorized. Use the Telegram chat ID, not the bot token.
For recurring mirroring, put a narrowly scoped instruction in the agent’s reviewed instructions or a dedicated skill. It should mirror only Web UI-originated turns and skip Telegram-originated turns to avoid loops and duplicates. Keep shared context and outbound delivery as separate settings.