OpenClaw Discord DM session routing bug: Discord direct messages are not being scoped to per-peer sessions even when `session.

OpenClaw Discord DM session routing bug: Discord direct messages are not being scoped to per-peer sessions even when session.dmScope: "per-peer" is set. They land in agent:main:main instead of agent:main:discord:direct:<user_id>, causing DM context bleed into the main webchat session. Concrete symptoms:

• User A uses the webchat (session agent:main:main)
• User B DMs the bot on Discord
• Both conversations interleave in the same session context window
• Agent confuses facts between the two users (e.g., mislabeling one user's identity fields with the other's)
• In sessions.json, a separate entry DOES exist for the DM channel (agent:main:discord:channel:<channel_id>), but messages are still physically written to the webchat session's jsonl instead of the DM session's jsonl
• Session metadata on agent:main:main gets polluted with DM sender labels (origin.label: "<dm_user> user id:...", lastTo: "channel:<dm_channel_id>")

OpenClaw version: 2026.3.24. Config has session.scope: "per-sender", session.dmScope: "per-peer", channels.discord.dm.policy: "allowlist", channels.discord.dm.allowFrom: [<user_ids>]. Set session.dmScope: "per-channel-peer" instead of "per-peer" for Discord.

Root cause investigation (read-only dive through ~/.local/share/fnm/node-versions/v22.22.0/installation/lib/node_modules/openclaw/dist/):

1. Session key construction happens in session-key-CYZxn_Kd.js::buildAgentPeerSessionKey(). The function branches on peerKind:

   • peerKind === "direct" with dmScope === "per-peer" → agent:<agentId>:direct:<peerId>
   • peerKind === "direct" with dmScope === "per-channel-peer" → agent:<agentId>:<channel>:direct:<peerId>
   • peerKind !== "direct" (e.g. "channel") → agent:<agentId>:<channel>:<peerKind>:<peerId> (dmScope is IGNORED for non-direct peers)

2. The Tlon plugin has explicit detection + owner-warning code for this exact bug pattern, with the message: "Multiple users sharing DM session. Configure 'session.dmScope: per-channel-peer' in OpenClaw config." (see channel.runtime-_q84dtRB.js around line 3298). This confirms per-channel-peer is the intended value for DM isolation.

3. The Discord plugin lacks the equivalent detection but has the same architectural issue — DMs fall through to the main session key when dmScope isn't appropriate for the peerKind being passed.

Config patch:

{
  "session": {
    "scope": "per-sender",
    "dmScope": "per-channel-peer"
  }
}

Additional recommendation (OpenClaw upstream bug report):

• Discord plugin should add the same "shared DM session" detection warning that Tlon has.
• The buildAgentPeerSessionKey function should honor dmScope: "per-peer" for non-direct peerKinds too, or document that per-peer only works for direct peers.
• session.dmScope schema hint should explicitly state that per-peer requires the inbound plugin to pass peerKind: "direct", and recommend per-channel-peer as the safer default for Discord/Slack/Teams where inbound peerKind varies.

Cross-references:

• dist/session-key-CYZxn_Kd.js::buildAgentPeerSessionKey (session key construction logic)
• dist/resolve-route-C5Xj9lGN.js::buildAgentSessionKey (entry point called by plugins)
• dist/channel.runtime-_q84dtRB.js ~line 3298 (Tlon warning for shared DM sessions, references session.dmScope: per-channel-peer)
• dist/channel.runtime-Dto237Iv.js ~line 1253 (WhatsApp broadcast session key construction using dmScope)

Validated against OpenClaw 2026.3.24. ["openclaw", "discord", "session", "routing", "bug"]