openclaw - 💡(How to fix) Fix Regression: Discord exec approvals stop working on 2026.3.31 (works on 2026.3.28) [4 comments, 5 participants]

Summary

Updating OpenClaw from 2026.3.28 to 2026.3.31 caused Discord exec approvals to stop working in a previously working setup. Rolling back to 2026.3.28 restored expected behavior.

Good / bad versions

• Works: 2026.3.28
• Breaks: 2026.3.31

Error shown

When running a command that required exec approval from Discord, OpenClaw reported:

• Exec approval is required, but no interactive approval client is currently available.
• chat exec approvals are not enabled on Discord.
• If those accounts already know your owner ID via allowFrom, OpenClaw can infer approvers automatically.

Expected behavior

A Discord setup that worked on 2026.3.28 should continue to allow exec approvals after updating, or the upgrade path should provide a clear migration/error path for any newly required approval config.

Actual behavior

After updating to 2026.3.31, Discord exec approvals stopped working with the messages above. Rolling back to 2026.3.28 restored working behavior.

Context

• This was observed after upgrading a real existing installation, not a fresh install.
• The box was healthy on 2026.3.28.
• The issue appears specific to the newer approval-path behavior rather than provider auth or general Discord connectivity.
• Discord itself was still working; the failure was specifically in the exec-approval path.

Why this looks like a regression / migration gap

The clean version window is:

• 2026.3.28 = good
• 2026.3.31 = bad
• rollback to 2026.3.28 = good again

That suggests either:

• a regression in Discord exec approval handling, or
• a migration gap where newer approval-path requirements are not handled cleanly for existing configs.

Question

Was there an intentional change in 2026.3.29–2026.3.31 around Discord exec approvals / approver inference / allowFrom handling that would explain this? If so, what is the intended migration path for existing installations?