openclaw - 💡(How to fix) Fix Bot reacts to own messages when requireMention is false (no self-message filtering) [1 comments, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#62165Fetched 2026-04-08 03:08:12
View on GitHub
Comments
1
Participants
1
Timeline
2
Reactions
0
Participants
Timeline (top)
closed ×1commented ×1

When a Slack channel is configured with requireMention: false, the bot can react to its own messages, creating a feedback loop. There is no filtering of messages from the bot's own user ID.

Root Cause

When a Slack channel is configured with requireMention: false, the bot can react to its own messages, creating a feedback loop. There is no filtering of messages from the bot's own user ID.

RAW_BUFFERClick to expand / collapse

Summary

When a Slack channel is configured with requireMention: false, the bot can react to its own messages, creating a feedback loop. There is no filtering of messages from the bot's own user ID.

Reproduction

  1. Configure a Slack channel with requireMention: false
  2. Have any mechanism cause the bot to post a message to that channel (e.g., a cron job delivery, a placeholder stub, or a normal reply)
  3. The bot sees its own message as new inbound → processes it → posts a reply → sees that reply → repeats

Expected behavior

The bot should ignore messages from its own bot user ID regardless of requireMention setting. This is standard practice for chat bots — Slack's own documentation recommends checking bot_id or user fields to avoid self-triggering loops.

Environment

  • OpenClaw v2026.4.5
  • Slack socket mode

Related

  • #16555 — TTL/Expiry for delivery queue (describes message floods on restart that could trigger this loop)

extent analysis

TL;DR

Filtering messages by the bot's own user ID is necessary to prevent feedback loops when requireMention is set to false.

Guidance

  • Check the bot_id or user fields in incoming messages to identify and ignore messages sent by the bot itself.
  • Implement a mechanism to filter out messages from the bot's user ID before processing them.
  • Review the bot's message handling logic to ensure it adheres to Slack's recommended practices for avoiding self-triggering loops.
  • Consider implementing a rate limiting or exponential backoff mechanism to prevent message floods in case the feedback loop is not fully prevented.

Example

if message['user'] == bot_user_id:
    # Ignore message sent by the bot itself
    return

Notes

This solution assumes that the bot has access to its own user ID and can filter messages based on this ID. The exact implementation may vary depending on the programming language and framework used.

Recommendation

Apply workaround: Implement message filtering based on the bot's user ID to prevent feedback loops when requireMention is set to false, as this is a standard practice recommended by Slack's documentation.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

The bot should ignore messages from its own bot user ID regardless of requireMention setting. This is standard practice for chat bots — Slack's own documentation recommends checking bot_id or user fields to avoid self-triggering loops.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING