Web ui and telegram session knowledge | Friends of the Crustacean 🦞🤝 | Page 1

#Web ui and telegram session knowledge

1 messages · Page 1 of 1 (latest)

hot elm Apr 23, 2026, 10:05 PM

Is anyone using both web ui and telegram daily? I changed dmScope to per-peer and I’m still not getting the context to go between channels. Need some help

stable saffronBOT Apr 23, 2026, 10:05 PM

spice charmBOT Apr 23, 2026, 10:05 PM

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

forest topazBOT Apr 23, 2026, 10:09 PM

Yep, this is a common gotcha, and yes people run Web UI + Telegram together daily.

What’s likely happening:

Web UI defaults to the agent’s main session.
With session.dmScope: "per-peer", Telegram DMs use a per-user key like agent:<id>:direct:<telegramUserId>.
Different session keys, so context does not auto-share.

If you want automatic shared context across Web UI + Telegram, set:

openclaw config set session.dmScope main

If you want to keep per-peer isolation, use session.identityLinks and then switch Web UI to the linked DM session instead of main.

Can you run these on the gateway host and paste output?