openclaw - 💡(How to fix) Fix [Bug] dmScope: per-channel-peer does not work for webchat channel [1 participants]

Environment:

• OpenClaw v2026.4.26 (macOS, Node.js)
• Configured session.dmScope: per-channel-peer
• Channels: Feishu (websocket) + Web UI

Bug Summary:

Setting session.dmScope to per-channel-peer has no effect for the webchat channel. All webchat messages are routed to agent:main:main instead of creating a per-channel-peer session like agent:main:webchat:direct:<feishu_user_id>.

Root Cause:

File: dist/runtime-policy-session-key-D3idRY2M.js, function resolvePolicyChannel (line 9):

function resolvePolicyChannel(ctx) {
    const raw = normalizeOptionalString(ctx?.OriginatingChannel ?? ctx?.Provider ?? ctx?.Surface);
    if (!raw) return;
    const channel = normalizeLowercaseStringOrEmpty(raw);
    return channel && channel !== "webchat" ? channel : void 0; // ← BUG
}

The explicit && channel !== "webchat" check causes resolvePolicyChannel to return undefined for all webchat messages. This triggers an early return in resolveRuntimePolicySessionKey:

const channel = resolvePolicyChannel(params.ctx);
const peerId = resolvePolicyDirectPeerId(params.ctx);
if (!channel || !peerId) return sessionKey; // ← falls through to main session

Since channel is undefined, the function returns the main session key (agent:main:main) directly, bypassing the dmScope logic entirely.

Expected Behavior:

All channels (including webchat) should be routed according to dmScope. With dmScope: per-channel-peer, webchat messages should produce a session key like agent:main:webchat:direct:<feishu_user_id>.

Current Observations:

Sessions.json agent:main:main origin metadata confirms webchat is incorrectly tagged:

"origin": {
  "provider": "webchat",
  "from": "feishu:<feishu_user_id>"
}

Suggested Fix:

Remove the hardcoded && channel !== "webchat" exclusion from resolvePolicyChannel. Webchat should be treated the same as any other channel. If webchat was intentionally excluded for a reason, that rationale should be documented, and the proper solution would be to respect dmScope configuration or add an explicit webchat.dmScope option instead of hardcoding the exclusion.