openclaw - 💡(How to fix) Fix Discord category allowlist entries do not apply to threads under child channels

Summary

Discord category allowlist entries appear to work for direct child channel messages, but they do not appear to apply to messages inside threads under those child channels.

In Discord, the structure is:

• category
  • text/forum channel
    • thread

For a thread message, the immediate parent is the child channel, and the category is the parent's parent. The current Discord allowlist behavior appears to check the current thread/channel and the immediate parent channel, but not the grandparent category.

Reproduction

1. Configure a Discord guild allowlist with only a category entry:

{
  channels: {
    discord: {
      groupPolicy: "allowlist",
      guilds: {
        "GUILD_ID": {
          channels: {
            "CATEGORY_ID": {
              enabled: true,
              requireMention: false
            }
          }
        }
      }
    }
  }
}

1. Create a text or forum channel under that category.
2. Create a thread under that child channel.
3. Send a message in the thread that should trigger the bot.

Expected behavior

The thread message should be allowed because its grandparent category is allowlisted.

The effective allowlist scope candidates for a thread should include:

• current thread ID
• parent channel ID
• grandparent category ID

Actual behavior

The category allowlist entry can allow the direct child channel, but the thread under that child channel is not allowed unless the child channel ID or thread ID is also added explicitly.

This makes category-based allowlisting inconvenient for Discord workflows that create multiple task channels and threads under one category.

Suggested fix

When resolving Discord channel allowlist scope for a thread, carry the parent channel's parent/category ID into the allowlist matching context.

Suggested matching order:

1. current thread/channel
2. immediate parent channel
3. grandparent category
4. wildcard fallback

Local validation

A local patch that added the grandparent category as an additional allowlist candidate fixed the behavior in focused tests:

• category-only thread allowlist: allowed
• wrong category: blocked
• parent-channel allowlist: still allowed