openclaw - 💡(How to fix) Fix Discord exec approval card/buttons not delivered in v2026.4.26 (regression after #71804) [3 comments, 3 participants]

Summary

Discord exec approval requests are created and can be approved manually with /approve ..., but the native Discord approval card/buttons do not surface. This appears to be a regression or incomplete fix after #71804.

Environment

• OpenClaw version: 2026.4.26
• Channel: Discord embedded channel
• Gateway: local loopback, embedded Discord
• Approval surface expected: Discord native approval card/buttons
• Approval config: Discord exec approvals enabled for Xavier with approver restricted to operator Discord user ID

Observed Behavior

When an exec command requires approval:

1. OpenClaw creates an approval ID normally.
2. No native Discord approval card/button appears in Discord.
3. The agent/session prints an approval command like: approve c33c0f54 allow-once
4. If the operator manually types that slash command in the channel, the approval is accepted.
5. The command then proceeds successfully.

In the reproduced case, this installed a dependency successfully after manual approval:

npm install --no-package-lock --no-save sharp@^0.34.5

Expected Behavior

When Discord exec approvals are enabled and an approval is created, OpenClaw should send the native Discord approval card/message with approve/deny buttons to the configured Discord approval surface, as in prior versions.

The user should not have to manually type the approval command.

Additional Notes

Agent-to-agent relaying of the approval command does not consume approvals — each retry generated a fresh approval ID instead of resolving the prior one. That behavior may be expected, but it made the issue more confusing.

The core regression is:

• Approval creation works
• Manual approval command in Discord works
• Native Discord approval card/buttons do not appear

Logs / Evidence

Relevant log line after manual approval:

exec.approval.waitDecision ... 152813ms

This suggests the approval decision was eventually received, but the native Discord card was never delivered.

Follow-up dispatch timeout after approval:

exec approval followup dispatch failed (id=c33c0f54-...): Session followup failed: gateway timeout after 60000ms

This may be a separate delivery issue but the command itself completed.

Related Issues

• #71804 — closed as fixed/covered, but this reproduces on 2026.4.26
• #46708 — broader approval UX/routing issue
• #39978 — async exec/approval follow-up can persist internally but not deliver to Discord