-
-
Notifications
You must be signed in to change notification settings - Fork 52.6k
Closed
Labels
bugSomething isn't workingSomething isn't working
Description
Summary
Slack DM threading is not working in Clawdbot. Neither the replyToMode: "all" config option nor the [[reply_to_current]] tag cause the bot to reply in a thread within DMs.
Steps to Reproduce
- Configure Slack with DM threading enabled:
{
"slack": {
"dm": {
"enabled": true,
"replyToMode": "all"
}
}
}- Send a message to the bot in a Slack DM
- Observe that the bot's reply does not create/use a thread
Alternatively:
- Try using the
[[reply_to_current]]tag in the bot's response - Observe that it still doesn't thread the reply
Expected Behavior
- With
replyToMode: "all", bot replies should automatically thread under the triggering message in DMs - The
[[reply_to_current]]tag should force threading regardless of config
Actual Behavior
Bot replies appear as top-level messages in the DM, not as threaded replies. Threading config/tags are silently ignored.
Environment
- Clawdbot version: 2026.1.16-2+ (likely current)
- OS: macOS
- Channel: Slack (Socket Mode)
- Context: Direct Messages (DMs)
Notes
- Issue Slack: Tool notifications leak to main channel when replyToMode=all #1388 fixed threading for channels with
replyToMode=all, but DMs still don't work - Issue [Bug]: Slack response duplicated in both thread and in channel #1163 reports the opposite problem (duplicate threading in channels)
- This appears to be specific to DM contexts
Related Issues
- Slack: Tool notifications leak to main channel when replyToMode=all #1388 (fixed threading in channels)
- [Bug]: Slack response duplicated in both thread and in channel #1163 (duplicate threading issue)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working