消息渠道“旁白泄漏”治理：仅允许 message 工具外发的交付策略

场景：Slack/Telegram 中，工具调用前的过程性文本被提前发出，污染正式回复。技巧：采用“工具外发优先 + NO_REPLY 收尾 + 渠道回归测试”流程降低噪音泄漏。

GITHUBDiscovered 2026-02-14Author gandalf-the-engineer

Prerequisites

Agent replies are delivered to messaging channels (Slack/Telegram/Discord etc.).
`message` tool routing is available for explicit user-facing delivery.

Steps

Audit current channel transcripts and identify leaked narration patterns (e.g., 'let me check...').
Refactor operational flows so user-visible content is sent via `message` tool as the canonical output path.
Ensure final assistant text in the same turn returns `NO_REPLY` when message-tool send is used.
Run multi-case regression (normal reply / error path / subagent path) and verify no pre-send narration is emitted.

Commands

openclaw gateway status

openclaw logs --local-time

Verify

Channel transcript shows only explicit `message` tool outputs for tested flows, with no leaked intermediate narration.

Caveats

This is currently a feature request, not a guaranteed built-in config switch（需验证）.
If streaming UX is required, full suppression may reduce perceived responsiveness.

Source attribution

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