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

Wed, 25 Mar 2026 00:00:00 +0000

Symptom

When OpenClaw is configured with requireMention: true for a Slack channel, the bot still responds to messages in a thread that do not mention the bot, after the bot has previously participated in that same thread.

Reproduction Steps:

Configure a Slack channel with requireMention: true
Start a thread and explicitly mention the OpenClaw bot in the first message (or any reply)
Observe OpenClaw replies as expected
Send another reply in the same thread without mentioning the bot
Unexpected behavior: OpenClaw may still reply, despite requireMention: true being set

Impact:

Bot generates unnecessary noise in Slack threads
Responds on behalf of others without being explicitly requested
Breaks user expectation that the bot only responds when tagged

Root Cause Analysis

The issue stems from how OpenClaw’s Slack integration handles implicit mentions in threaded conversations.

Technical Flow

Thread Participation Tracking: When OpenClaw delivers a reply in a thread, it records the thread participation: if (anyReplyDelivered && participationThreadTs) recordSlackThreadParticipation(account.accountId, message.channel, participationThreadTs);
Implicit Mention Calculation: For subsequent messages in that thread, OpenClaw checks if the bot has participated: const implicitMention = Boolean( !isDirectMessage && ctx.botUserId && message.thread_ts && ( message.parent_user_id === ctx.botUserId || hasSlackThreadParticipation(account.accountId, message.channel, message.thread_ts) ) );
Mention Gating Logic: The implicitMention flag is passed to the mention gating resolver: const mentionGate = resolveMentionGatingWithBypass({ isGroup: isRoom, requireMention: Boolean(shouldRequireMention), canDetectMention, wasMentioned, implicitMention, … });
Effective Mention Decision: The gating function treats implicitMention as equivalent to being mentioned: function resolveMentionGating(params) { const implicit = params.implicitMention === true; const bypass = params.shouldBypassMention === true; const effectiveWasMentioned = params.wasMentioned || implicit || bypass; return { effectiveWasMentioned, shouldSkip: params.requireMention && params.canDetectMention && !effectiveWasMentioned }; }

Root Cause

The core problem is that prior thread participation is treated as an implicit mention, which effectively bypasses the requireMention: true configuration. Once OpenClaw has replied in a thread, subsequent messages in that thread will always trigger responses, regardless of whether the bot is mentioned.

Solution

Immediate Workaround

Until this bug is fixed in a future release, consider the following workarounds:

Use Separate Threads for Bot Interactions:
- Start a new thread when you want to interact with OpenClaw
- Avoid replying in threads where the bot has already participated
Temporarily Disable Thread Replies:
- If frequent in-thread discussions occur without wanting bot participation, manually archive or close threads
Adjust requireMention at the Cost of Usability:
- Setting requireMention: false globally will allow all messages to trigger responses (not recommended as a long-term solution)

Code-Level Fix (For Developers)

The fix should modify the Slack integration to respect requireMention: true regardless of thread participation. In the resolveMentionGating function, the logic should be updated so that when requireMention is explicitly true, only explicit mentions are accepted:

function resolveMentionGating(params) { const implicit = params.implicitMention === true; const bypass = params.shouldBypassMention === true;

// When requireMention is true, implicit mentions should not bypass the check
const effectiveWasMentioned = params.wasMentioned || (params.requireMention ? false : (implicit || bypass));

return {
    effectiveWasMentioned,
    shouldSkip: params.requireMention && params.canDetectMention && !effectiveWasMentioned
};

}

Alternatively, the implicitMention calculation could be modified to not consider thread participation when requireMention is enabled for the channel.

Prevention

To prevent unexpected behavior until this bug is fixed:

Review Thread Usage:
- Be aware that bot participation in a thread may cause unintended future replies
- Use direct messages for isolated bot interactions
Monitor Bot Responses:
- Keep an eye on channels with requireMention: true for unexpected bot behavior
- Report any instances of the bot responding to untagged messages
Stay Updated:
- Monitor the GitHub issue for fixes and updates
- Apply patches promptly when they become available
Documentation:
- Document this known limitation for team members using the Slack integration
- Include workarounds in internal runbooks

Additional Information

Affected Versions: OpenClaw 2026.3.23-2 (and likely earlier versions)
Platform: Amazon Linux 2023.10.20260302
Install Method: npm global
Model: openai/gpt-5.4

The bug is classified as a behavior bug rather than a crash, as it produces incorrect output without causing system failure. The severity is “Annoying” with frequency rated as “Each time.”

File	Purpose
`/runtime-api-BI9wNO54.js`	Main Slack integration runtime
`hasSlackThreadParticipation()`	Checks if bot participated in thread
`recordSlackThreadParticipation()`	Records bot participation in thread
`resolveMentionGating()`	Determines if bot should respond

Sources

GitHub Issue #64277

Slack on FixClaw