openclaw - ✅(Solved) Fix Slash commands return "✅ Done." instead of actual output in Discord [1 pull requests, 3 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#58986Fetched 2026-04-08 02:30:17
View on GitHub
Comments
3
Participants
2
Timeline
4
Reactions
3
Participants
Timeline (top)
commented ×3cross-referenced ×1

PR fix notes

PR #62057: fix(discord): avoid silent native slash success fallback

Description (problem / solution / changelog)

Summary

  • unify native Discord builtin slash auth with shared command auth before dispatch
  • return an explicit unauthorized response for builtin native slash commands when shared auth denies
  • replace the generic native zero-output fallback with an explicit warning instead of ✅ Done.
  • add a regression test covering zero-visible-output native slash dispatch

Fixes #58986.

Why

Discord native slash commands could appear to succeed with ✅ Done. even when no visible reply was produced. One real path was auth drift: native preflight allowed the command, deeper shared auth denied it, builtin handlers returned no payload, dispatch returned zero outputs, and Discord emitted a misleading success ack.

This patch makes builtin native slash commands fail explicitly when shared auth denies, and makes the remaining zero-output fallback explicit instead of looking like success.

Testing

Passed

  • pnpm vitest run extensions/discord/src/monitor/native-command.plugin-dispatch.test.ts

Attempted but blocked by pre-existing checkout issues

  • pnpm test:extension discord
    • failed in unrelated existing Discord tests in this checkout, including exec-approvals.test.ts, monitor.test.ts, and thread-bindings.lifecycle.test.ts
  • pnpm test:contracts
    • not reached because pnpm test:extension discord was already red in this tree
  • pnpm build && pnpm check
    • build/check path hung in this checkout and did not complete cleanly

AI assistance

This PR was prepared with AI assistance, with changes reviewed and validation results reported transparently.

Changed files

  • extensions/discord/src/monitor/native-command.plugin-dispatch.test.ts (modified, +56/-0)
  • extensions/discord/src/monitor/native-command.ts (modified, +2/-2)
RAW_BUFFERClick to expand / collapse

After upgrading to v2026.3.31, Discord slash commands like /status, /help, /whoami etc. return only "✅ Done." as an ephemeral response instead of the actual command output.

Steps to reproduce:

  1. Use any slash command in Discord (e.g., /status)
  2. Bot responds with "✅ Done." (ephemeral)
  3. Expected: actual status/command output should be shown

Environment:

  • OpenClaw v2026.3.31
  • Discord channel
  • Commands affected: /status, /help, /whoami, etc.

Additional context:

  • This appears to be a regression in v2026.3.31
  • The commands work but show "Done." instead of actual output
  • Other slash commands are also affected
  • Screenshot: Commands return ephemeral "Done." confirmation instead of actual output

extent analysis

TL;DR

The issue with Discord slash commands returning "✅ Done." instead of actual output after upgrading to v2026.3.31 may be resolved by checking the command response handling in the OpenClaw version.

Guidance

  • Review the changes in v2026.3.31 to identify any updates that could be causing the commands to return "✅ Done." instead of the actual output.
  • Verify that the command execution logic is correct and that the output is being generated as expected, but not being returned to the user.
  • Check the ephemeral response configuration to ensure it's not overriding the actual command output.
  • Test other slash commands to confirm if the issue is consistent across all commands or specific to certain ones.

Example

No code snippet is provided as the issue does not include specific code details.

Notes

The exact cause of the issue is unclear without more information about the changes in v2026.3.31 or the command handling logic. It's possible that the issue is related to a regression in the new version.

Recommendation

Apply workaround: Temporarily downgrade to a previous version of OpenClaw where the commands were working as expected, until the issue is resolved in a future update. This is because the issue appears to be a regression in v2026.3.31, and downgrading may provide a temporary solution.

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