openclaw - 💡(How to fix) Fix [bug] regression: discord groupPolicy "allowlist" with no guild.channels block now denies all channels (previously allowed via user filter) [1 comments, 2 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#75647Fetched 2026-05-02 05:32:21
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
2
Author
Timeline (top)
closed ×1commented ×1mentioned ×1subscribed ×1

A Discord guild config with groupPolicy: "allowlist" and no channels field under the guild block previously allowed the bot to operate in any channel of that guild (filtering only by users and requireMention). On 2026.4.27 the same config silently denies every channel in that guild — the bot receives messages but never replies. Adding an explicit channels allowlist restores behavior.

Error Message

by the allowlist — there is no warn/info that the channel was filtered.

Root Cause

A Discord guild config with groupPolicy: "allowlist" and no channels field under the guild block previously allowed the bot to operate in any channel of that guild (filtering only by users and requireMention). On 2026.4.27 the same config silently denies every channel in that guild — the bot receives messages but never replies. Adding an explicit channels allowlist restores behavior.

Fix Action

Workaround

Explicitly enumerate every channel under `guilds.<id>.channels` as `{ "<channel_id>": {} }`. Brittle for guilds with many channels and breaks when channels are added.

RAW_BUFFERClick to expand / collapse

Summary

A Discord guild config with groupPolicy: "allowlist" and no channels field under the guild block previously allowed the bot to operate in any channel of that guild (filtering only by users and requireMention). On 2026.4.27 the same config silently denies every channel in that guild — the bot receives messages but never replies. Adding an explicit channels allowlist restores behavior.

Environment

  • OpenClaw: 2026.4.27 (cbc2ba0), upgraded from 2026.4.24
  • macOS: 26.4.1 (arm64), Node v25.4.0
  • Gateway only; LaunchAgent install via npm global

Repro

  1. Configure a Discord guild with the following block (no channels key): ```json "channels": { "discord": { "groupPolicy": "allowlist", "guilds": { "<guild_id>": { "requireMention": false, "users": ["<user_id>"] } } } } ```
  2. From the allowlisted user, send a message in any channel of that guild.
  3. Observe channels status: in:Xm ago, out:13h ago. Inbound is recorded, no outbound reply happens. No log line indicates the message was rejected by the allowlist — there is no warn/info that the channel was filtered.

Evidence the prior behavior was real (not misremembered)

`~/.openclaw/logs/commands.log` shows continuous `agent:main` and `agent:cron-lite` sessions in this channel for months prior to the upgrade, under the same config. The discord guild block content is byte-identical across all `openclaw.json.bak.` and `openclaw.json.clobbered.` snapshots going back to 2026.4.22 — `channels` field never present in any of them.

Expected

Either:

  1. Restore prior behavior: when `channels` is omitted under `groupPolicy: "allowlist"`, treat all channels in the guild as allowed (filter only by `users` / `requireMention`). Allow when omitted; require explicit empty object to deny.
  2. Or, on first startup after upgrade where this pattern is detected, either log a clear warning (`guild X has groupPolicy:allowlist with no channels — all channels denied; add channels:{} or change groupPolicy`) or surface it via `openclaw channels status` and `doctor`. Right now the regression is silent — bot status reads "connected, running" with no indication anything is filtered out.

Workaround

Explicitly enumerate every channel under `guilds.<id>.channels` as `{ "<channel_id>": {} }`. Brittle for guilds with many channels and breaks when channels are added.

extent analysis

TL;DR

Add an explicit channels allowlist to the Discord guild configuration to restore the previous behavior.

Guidance

  • Verify that the groupPolicy is set to "allowlist" and there is no channels field under the guild block in the configuration.
  • Check the openclaw.json file for any changes or updates that may have caused the regression.
  • Consider adding a clear warning or log message when the channels field is omitted under groupPolicy: "allowlist" to prevent silent denial of all channels.
  • Explicitly enumerate every channel under guilds.<id>.channels as { "<channel_id>": {} } as a temporary workaround.

Example

"channels": {
  "discord": {
    "groupPolicy": "allowlist",
    "guilds": {
      "<guild_id>": {
        "requireMention": false,
        "users": ["<user_id>"],
        "channels": {
          "<channel_id>": {}
        }
      }
    }
  }
}

Notes

The issue seems to be related to a change in the behavior of the groupPolicy: "allowlist" configuration in OpenClaw version 2026.4.27. The previous behavior allowed the bot to operate in any channel of the guild when the channels field was omitted, but now it silently denies all channels.

Recommendation

Apply the workaround by explicitly enumerating every channel under guilds.<id>.channels as { "<channel_id>": {} } until a fix is available. This will restore the previous behavior, but it may be brittle for guilds with many channels and breaks when channels are added.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [bug] regression: discord groupPolicy "allowlist" with no guild.channels block now denies all channels (previously allowed via user filter) [1 comments, 2 participants]