Skip to content

Slack DMs Misclassified as Channels - dmScope 'main' Not Working #8421

@TFITZ57

Description

@TFITZ57

Summary

Slack DMs (channel IDs starting with D) are being routed to a separate slack:channel:<id> session instead of merging with main, even with session.dmScope: "main".

Expected Behavior

Per docs: "DMs share the main session (like WhatsApp/Telegram)"
Slack DMs should route to agent:main:main.

Actual Behavior

Slack DM D0ACP6B1T8V is:

  • Classified as kind: "group"
  • Routed to agent:main:slack:channel:d0acp6b1t8v
  • NOT merging with main session

Inbound messages appear in context, but outbound replies don't auto-deliver to Slack.

Config

{
  "session": { "dmScope": "main" },
  "channels": {
    "slack": {
      "dm": { "policy": "open", "allowFrom": ["*"] },
      "groupPolicy": "open"
    }
  }
}

Session State (from sessions_list)

{
  "key": "agent:main:slack:channel:d0acp6b1t8v",
  "kind": "group",
  "channel": "slack",
  "displayName": "slack:g-d0acp6b1t8v"
}

Note: Channel ID D0ACP6B1T8V has the D prefix which should indicate a Slack DM, but it's being treated as a channel/group.

Workaround

Using explicit message tool sends works.

Environment

  • OpenClaw 2026.2.1
  • macOS 12 (Monterey), Node v22.22.0
  • Slack Socket Mode

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingstaleMarked as stale due to inactivity

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions