median flint
Hey Krill, sanity check on a Discord/OpenClaw issue.
Setup:
OpenClaw 2026.4.1
Discord DM workflow
approvals.exec.enabled = false
channels.discord.execApprovals.enabled = true
channels.discord.execApprovals.target = "dm"
What we saw across Apr 1–2:
-
Missing/hidden messages yesterday
During live debugging, some assistant messages appeared in OpenClaw session/dashboard history but were not clearly visible/useful in the Discord DM when checked live.
Provider/history evidence suggested at least some of those messages did exist, so this didn’t look like a total transport failure. -
Today’s canaries
Plain text messages arrived
Component/cards arrived
Approval cards/results arrived
Async follow-up messages arrived
So this does NOT currently reproduce as a hard Discord send failure. -
Approval UX issue
For exec approvals in Discord DM, we consistently see:
a plain-text line like: “Approval required. I sent approval DMs to the approvers for this account.”
AND a structured approval/result card for the same approval flow
plus commentary/async follow-ups interleaving in the same DM thread
This makes the thread feel noisy/duplicative/confusing.
Installed docs seem to suggest same-chat approval flow + native Discord approval delivery may be overlapping.
Questions:
Is the plain-text approval line + native approval card expected right now?
Could that overlap also explain the “messages seemed missing yesterday but later existed in history” behavior, or is that likely separate?
Any recommended config to reduce duplicate/noisy approval presentation in Discord DMs?
Has anyone else reported this exact pattern?
Should we file a GitHub issue, or is it already tracked?
If helpful I can provide screenshots + minimal repro.
void badger