openclaw - 💡(How to fix) Fix Bug: Discord slash commands crash in threads - Cannot access rawData on partial Channel [3 comments, 3 participants]

Bug Description

Discord slash commands (/ commands) triggered inside a thread cause an unhandled error. The GuildThreadChannel object from @buape/carbon is partial (missing full data), and accessing its parentId getter throws because rawData is not populated.

Error Log

Cannot access rawData on partial Channel. Use fetch() to populate data.
    at GuildThreadChannel.get rawData [as rawData] (BaseChannel.ts:65:10)
    at GuildThreadChannel.get parentId [as parentId] (BaseGuildChannel.ts:44:13)
    at dispatchDiscordCommandInteraction (provider-CraktAkD.js:2451:47)
    at Command.run (provider-CraktAkD.js:2367:4)
    at CommandHandler.handleCommandInteraction (CommandHandler.ts:173:19)
    at Client.handleInteraction (Client.ts:481:9)

Root Cause

In extensions/discord/provider-CraktAkD.js, the dispatchDiscordCommandInteraction function accesses channel.parentId without first fetching the full channel data:

// Line ~2451
parentId: "parentId" in channel ? channel.parentId ?? void 0 : void 0,

When channel is a GuildThreadChannel partial object (which is the case for thread interactions from the gateway), accessing channel.parentId triggers the rawData getter, which throws because the channel data was not fetched.

The same pattern appears at multiple locations:

• Line ~400
• Line ~1419
• Line ~2199
• Line ~2451

Steps to Reproduce

1. Have a Discord bot with slash commands configured
2. Create or enter a thread in any channel
3. Trigger any slash command (e.g., /status)
4. Observe the error - command fails silently

Expected Behavior

Slash commands should work in threads the same as in regular channels. The code should either:

1. Call channel.fetch() before accessing properties like parentId, or
2. Wrap the parentId access in a try-catch to gracefully handle partial channels, or
3. Use the channel_id from the interaction payload directly instead of relying on the channel object

Environment

• OpenClaw v2026.4.21
• This regression appeared after upgrading from a previous version (the @buape/carbon dependency was updated)
• macOS / Apple Silicon

Workaround

Use slash commands in the parent channel instead of inside threads.

Additional Context

This is a regression introduced by a @buape/carbon library update where GuildThreadChannel objects from gateway events are no longer fully populated. The OpenClaw code needs to be adapted to handle partial channel objects.