#Discord sessions and chat
1 messages · Page 1 of 1 (latest)
@fluid hamlet thoughts?
Short version: same session does not mean same reply transport.
What you’re seeing is expected:
discord:123...is the session/context key- opening that session in Control UI chat reuses the same history/state
- but the turn is being sent via WebChat / Control UI, and those replies go back to WebChat, not Discord
The docs say WebChat/Control UI uses the same sessions, but has deterministic routing, meaning replies go back to WebChat: https://docs.openclaw.ai/web/webchat
Session docs here too: https://docs.openclaw.ai/concepts/session
So, you’re not really doing anything wrong, it’s just not a mirrored “chat from anywhere, reply everywhere” model.
If you want the reply to appear in Discord, you need to either:
- send the message from Discord, or
- use an explicit delivery path, like
message/openclaw agent ... --deliver