Slack `requireMention: true` Bypassed for Thread Replies After Prior Bot Participation

Symptom When a Slack channel is configured with requireMention: true, OpenClaw still responds to untagged messages in a thread after it has previously participated in that thread. This behavior violates the expected mention gating logic. Steps to reproduce: Configure OpenClaw with Slack and set requireMention: true for a channel. Add the OpenClaw Bot user to that Slack channel. Start a thread and explicitly mention the bot in the first message (or any thread reply) so OpenClaw replies once. After OpenClaw has replied in that thread, send another reply in the same thread without mentioning the bot. Observe that OpenClaw still replies, even though requireMention: true is set. Expected behavior: OpenClaw should only reply when explicitly mentioned. Prior participation in the thread should not count as a mention. ...

April 1, 2026 · 4 min · 710 words · FixClaw

CLI Slack JSON Manifest Contains Invalidating Pipe Characters

Symptom When using the OpenClaw CLI to add a Slack channel via openclaw channels add, the generated JSON manifest is displayed with decorative pipe characters framing the output. The manifest appears as follows: │ { │ │ “key”: “value” │ │ } │ These pipe characters make the JSON invalid when copied and pasted, forcing users to manually remove all the pipe characters before the JSON can be used. Root Cause Analysis The CLI code renders the JSON manifest using ASCII box-drawing characters for visual presentation in the terminal. While this makes the output look “pretty” in the CLI interface, it includes pipe (|) characters as part of the actual output string. ...

March 15, 2026 · 2 min · 367 words · FixClaw