Environment

• OpenClaw version: 2026.2.3-1
• OS: macOS 26.2 (arm64)
• Node: v25.2.1

Configuration

{
  "session": {
    "dmScope": "per-channel-peer"
  }
}

Expected behavior

Feishu DM messages should route to:

agent:main:feishu:dm:ou_cba67b0c645b674a334c217eabcefffc

Actual behavior

Feishu DM messages route to:

agent:main:main

Despite dmScope: "per-channel-peer" being set.

Evidence

1. Session list shows the expected session key exists:

$ openclaw sessions list
...
agent:main:feishu:dm:ou_cba67b0c645b674a334c217eabcefffc
  sessionId: d72aa73b-cae8-41da-bf06-f75536df6d3c
  channel: unknown (should be feishu)

2. But the session history is empty:

$ openclaw sessions history agent:main:feishu:dm:ou_cba67b0c645b674a334c217eabcefffc
{
  "messages": []
}

3. All actual messages are in agent:main:main:

$ openclaw sessions history agent:main:main
{
  "messages": [
    # All Feishu DM messages are here
  ]
}

Question

Is this a bug or intentional behavior?

• If it's a bug: Which file contains the session routing logic for Feishu DM?
• If it's intentional: Is there a way to make Feishu DM respect dmScope configuration?

Impact

This makes it impossible to isolate Feishu DM sessions from other channels when using per-channel-peer mode.