# Web UI and Telegram share context, but replies appear in only one place

**URL:** <https://community.openclaw.ai/t/web-ui-and-telegram-share-context-but-replies-appear-in-only-one-place/31>\
**Category:** Troubleshooting\
**Tags:** channels, routing, sessions, threads, troubleshooting\
**Created:** [September 14, 2026, 5:36pm UTC](https://community.openclaw.ai/t/web-ui-and-telegram-share-context-but-replies-appear-in-only-one-place/31 "2026-09-14T17:36:30Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ArchivedMember](https://avatars.discourse-cdn.com/v4/letter/a/e56c9b/32.png) [@ArchivedMember](https://community.openclaw.ai/u/ArchivedMember)\
**Post date:** [September 14, 2026, 5:36pm UTC](https://community.openclaw.ai/t/web-ui-and-telegram-share-context-but-replies-appear-in-only-one-place/31/1 "2026-09-14T17:36:30Z")

</div>

> **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.

---

<div class="post-metadata">

**Author:** ![OpenClawSupport](https://avatars.discourse-cdn.com/v4/letter/o/49beb7/32.png) [@OpenClawSupport](https://community.openclaw.ai/u/OpenClawSupport)\
**Post date:** [September 14, 2026, 8:46pm UTC](https://community.openclaw.ai/t/web-ui-and-telegram-share-context-but-replies-appear-in-only-one-place/31/2 "2026-09-14T20:46:17Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![ArchivedMember](https://avatars.discourse-cdn.com/v4/letter/a/e56c9b/32.png) [@ArchivedMember](https://community.openclaw.ai/u/ArchivedMember)\
**Post date:** [September 14, 2026, 8:46pm UTC](https://community.openclaw.ai/t/web-ui-and-telegram-share-context-but-replies-appear-in-only-one-place/31/3 "2026-09-14T20:46:17Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![OpenClawSupport](https://avatars.discourse-cdn.com/v4/letter/o/49beb7/32.png) [@OpenClawSupport](https://community.openclaw.ai/u/OpenClawSupport)\
**Post date:** [September 14, 2026, 8:46pm UTC](https://community.openclaw.ai/t/web-ui-and-telegram-share-context-but-replies-appear-in-only-one-place/31/4 "2026-09-14T20:46:17Z")

</div>

Use an explicit message broadcast for the second delivery. Preview the destination and payload first:

```bash
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.
