Issues configuring a discord bot like Krill

[quasi bison]

Issue: Discord bot cannot react to real-time mentions/events in Forum channels, but can read/reply when given a direct Thread ID.

Status:

Config: Message Content Intent is enabled in the Dev Portal.
Attempted: Gateway restart and re-inviting the bot.
Observation: Standard "Read/Write" works via ID, but "Hearing" (event stream) is dead for Forums.
Goal: Fix the event stream/intent routing for Forum threads so the bot can respond proactively to tags.

Seems to not always respond to a ping, not sure what the issue.

[open jetty]

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

[high robin]

First thing, can you paste openclaw --version?

This probably is not “forums are unsupported”. Current OpenClaw does handle Discord forum/public-thread messages, and forum threads inherit config from the parent forum channel.

If it can read/reply by direct thread ID but misses live pings, the usual causes are:

1. mention gating / allowlist drop
2. missing thread permissions
3. listener timeout

Please run these while pinging the bot from inside the forum thread:

openclaw channels status --probe
openclaw logs --follow

Look for log lines like:

• drop guild message (mention required → mention gate blocked it
• Blocked discord channel ... not in guild channel allowlist → forum parent not allowlisted
• Listener DiscordMessageListener timed out or discord inbound worker timed out → handler timing out

Important config nuance: allow the forum parent channel ID under channels.discord.guilds.<guildId>.channels, not just the thread ID. Forum threads inherit the parent config.

Also double check the bot has these perms on the forum parent:

• View Channels
• Read Message History
• Send Messages
• Send Messages in Threads

Docs:

• https://docs.openclaw.ai/help/faq

• https://docs.openclaw.ai/channels/discord
• https://docs.openclaw.ai/help/troubleshooting

If you paste:

1. openclaw --version
2. openclaw channels status --probe
3. 10 to 20 log lines around a missed ping

I can narrow it down pretty quickly.

[quasi bison]

OpenClaw 2026.4.11 @high robin

[high robin]

2026.4.11 is recent enough that I would not blame general forum-thread support.

What you’re seeing, “can read/reply by thread ID, but misses live pings”, usually means:

• REST send works
• but gateway ingress is getting dropped during preflight

So the important distinction is:

• message send/read by threadId proves outbound + lookup work
• it does not prove inbound forum-thread events are being accepted

The most likely culprit is this:

if groupPolicy: "allowlist" is on, make sure the forum parent channel ID is allowlisted under channels.discord.guilds.<guildId>.channels, not just the thread ID.

Forum threads inherit parent config.

Example shape:

{
  channels: {
    discord: {
      guilds: {
        "YOUR_GUILD_ID": {
          channels: {
            "YOUR_FORUM_PARENT_ID": {
              allow: true,
              requireMention: true,
            },
          },
        },
      },

    },
  },
}

Also, if you’re using channel names/slugs there, switch to numeric IDs for debugging.

Next check, please run:

openclaw channels status --probe
openclaw logs --follow

Then ping the bot in the forum thread and watch for:

• drop guild message (mention required
• Blocked discord channel ... not in guild channel allowlist
• Listener DiscordMessageListener timed out
• discord inbound worker timed out

Also verify the bot has these perms on the forum parent:

• View Channels
• Read Message History
• Send Messages
• Send Messages in Threads

If you paste your channels.discord.guilds... block plus the log lines from one missed ping, I can tell you pretty quickly which gate is killing it.

[quasi bison]

that worked thanks, now, how did you setup the welcome bot?

[high robin]

Nice, glad we caught it 🎉

If that fixed it, please right-click the solution message → Apps → ✅ Mark Solution so Answer Overflow can index it.

On the welcome bot part, I don’t think that’s a built-in one-click OpenClaw Discord feature right now. For Discord, the usual setup is:

1. simple welcome flow
   use Discord onboarding or a normal welcome bot for member-join messages

2. custom OpenClaw-style flow
   build a small Discord-side handler that listens for:

   • member join, or
   • new forum/help thread

   then sends a canned welcome message, or hands it to OpenClaw for a smarter reply

So if you mean “welcome people when they join the server”, that’s usually a custom bot/plugin.

If you mean “welcome people when they open a help thread/forum post”, that’s also custom, but pretty straightforward.

If you want, I can sketch the minimal setup for either:

• server join welcome
• new forum thread welcome

and I’ll keep it as small as possible.

[quasi bison]

thanks yes, mark as resolved.

[high robin]

I can’t mark forum solutions from my side, but you can do it in two clicks:

right-click the solution message → Apps → ✅ Mark Solution

That’ll mark the thread as resolved and help Answer Overflow index it.