openclaw - 💡(How to fix) Fix Session key reflects origin channel, but agents may misinterpret it as current channel [1 pull requests]

Problem

Session keys (e.g. agent:main:discord:channel:1489550370136129537) reflect the channel where the session was originally created. When a user later continues that same session via webchat, the session key still contains discord:channel:.

Agents see channel: "webchat" in their inbound context but the session key says discord:channel:. This contradiction causes agents to misidentify their own session as "the wrong session," leading to context confusion, fetching the wrong session history, or overwriting existing conversation results.

Two different agents on a single instance hit this on the same day (2026-05-19).

Steps to Reproduce

1. Create an agent session via a Discord channel (session key becomes agent:main:discord:channel:XXX).
2. Later, continue that same session via webchat Control UI.
3. Agent sees discord:channel: in the session key but channel: "webchat" in inbound metadata.
4. Agent interprets these as contradictory and may get confused about which session it is in.

Expected Behavior

Agents should clearly understand that the session key indicates the origin channel, not the current channel. Alternatively, session_status / sessions_list output should include fields that distinguish the currently active channel from the origin channel.

Possible Solutions

1. Add an originChannel and activeChannel (or similar) field to session_status and sessions_list output so agents can distinguish current vs. origin channel.
2. Update documentation in session-tool.md to explicitly state that the session key reflects the origin channel and may not match the currently active channel.

Environment

• OpenClaw version: 2026.5.12
• Affected channels: webchat, Discord (any combination where channel switching occurs)