Skip to content

[Bug]: Discord slash commands in thread hang on “thinking…” and crash with partial channel error #70447

Description

@Kalclavia

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Version: OpenClaw 2026.4.21
Channel: Discord
Scope: Slash commands (e.g. /models, /focus) when executed inside a Discord thread

Summary
After updating to 2026.4.21, when slash commands are run inside a Discord thread, the bot acknowledges the interaction but never returns a response. Discord UI stays on “ is thinking…”.

Steps to reproduce

Open a Discord thread.
Run /models (or /focus) in that thread.
Observe bot hangs on thinking state.

Expected behavior

Slash command returns normal response in thread context.

Actual behavior

Interaction is acknowledged, then handler crashes before response.

OpenClaw version

2026.4.21

Operating system

Ubuntu 24.04

Install method

npm

Model

ChatGPT Codex 5.3

Provider / routing chain

Discord UI → @openclaw/discord channel plugin → carbon interaction handler → dispatchDiscordCommandInteraction() → OpenClaw gateway session router → agent runtime (main) → provider=openai-codex → model gpt-5.3-codex → response back to Discord

Additional provider/model setup details

No response

Logs, screenshots, and evidence

 access rawData on partial Channel. Use fetch() to populate data.
Error: Cannot access rawData on partial Channel. Use fetch() to populate data.
    at GuildThreadChannel.get rawData [as rawData] (.../@buape/carbon/src/abstracts/BaseChannel.ts:65:10)
    at GuildThreadChannel.get parentId [as parentId] (.../@buape/carbon/src/abstracts/BaseGuildChannel.ts:44:13)
    at dispatchDiscordCommandInteraction (.../provider-CraktAkD.js:2451:47)

Notes

  • Commands work outside thread context (parent channel/DM), so issue appears thread-specific.
  • Looks like interaction handler reads parentId from a partial GuildThreadChannel without fetching/populating first.

Impact and severity

Frequency
Reproducible every attempt in thread context.

Severity
Affects all setups in Discord that route individual chats to seperate threads.

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingregressionBehavior that previously worked and now fails

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions