openclaw - 💡(How to fix) Fix [Slack] DM top-level messages incorrectly generate :thread: session keys with replyToMode != off [1 participants]

Bug Description

Top-level Slack DM (direct message) messages incorrectly receive a :thread: session key suffix when replyToMode is not "off", identical to the channel bug fixed in #32353 / PR #32320.

The channel fix only addressed channel messages. DMs with dmScope: "per-channel-peer" still exhibit the same behavior.

Environment

• Version: 2026.3.24
• Channel: Slack
• Configuration:

  {
    "session": { "dmScope": "per-channel-peer" },
    "channels": { "slack": { "replyToMode": "all" } }
  }

Reproduction

1. Configure dmScope: "per-channel-peer" and replyToMode: "all"
2. Send a top-level DM to the bot (not a thread reply)
3. Observe the generated session key

Expected

agent:romeo:slack:direct:u0710thrrnc

Actual

agent:romeo:slack:direct:u0710thrrnc:thread:1775027682.537589

The timestamp is the message's own ts, not a thread parent — indicating a top-level DM, not a reply.

Impact

• Every DM creates an isolated session → complete context loss between messages
• Delivery messages injected into the DM session cannot share context with user replies
• Parent DM session (agent:romeo:slack:direct:u0710thrrnc without :thread:) is never created

Workaround

Set accounts.<name>.dm.replyToMode: "off" for the DM account:

"accounts": {
  "default": {
    "dm": { "replyToMode": "off" }
  }
}

This prevents the :thread: suffix and creates a persistent parent DM session.

Related

• #32353 / #32285 / PR #32320 — same bug for channels, fixed in v2026.3.1
• Root cause was roomThreadId falling through to threadContext.messageTs when replyToMode != "off"