Slack DM 去线程噪音：`replyToMode=off` 下状态消息不再强制进 thread

问题/场景：Slack 私聊设置 `replyToModeByChatType.direct: off` 后，状态/打字提示仍被塞进 thread，造成大量碎片回复。前置条件：使用 Slack 渠道并能调整 replyTo 配置。实施步骤：升级到 PR #20406 修复版本→确认 DM replyToMode 配置→回归多工具链路。关键配置：`replyToModeByChatType.direct: off`。验证：DM 不再出现批量线程状态消息。风险：若团队依赖线程追踪状态，需改为显式日志渠道。

GITHUBDiscovered 2026-02-19Author QuinnYates

Prerequisites

Slack connector is active and direct-message workflows generate intermediate status/narration updates.
You can edit channel reply mode config and deploy updated gateway build.

Steps

Set or verify `replyToModeByChatType.direct: "off"` in Slack config for DM sessions.
Upgrade runtime to include PR #20406 where `statusThreadTs` follows `replyThreadTs` without fallback.
Restart gateway and run a DM scenario with multiple tool calls + narration to stress test message threading.
Compare before/after thread counts and ensure user-facing replies remain readable at top level.

Commands

openclaw gateway status

openclaw gateway restart

openclaw help

Verify

In DM with replyToMode off, no intermediate status messages are posted as threaded replies unless inbound message itself is in a thread.

Caveats

If your workflow depends on threaded audit visibility, disabling threading may require a separate audit sink/channel.
Behavior for non-DM chat types still depends on per-chat policy and should be validated separately（需验证）.

Source attribution

This tip is aggregated from community/public sources and preserved with attribution.

Open original source ↗

Visit original post