#Exec approval is required, but no interactive approval client is currently available.
1 messages Β· Page 1 of 1 (latest)
Yep β that error means: exec approval is required, but OpenClaw has nowhere to send/receive the approval (no active UI approver + no usable chat approval route).
First, paste this so we can pin version behavior:
openclaw --version
Then fix the approval route (Discord-native path):
{
commands: {
ownerAllowFrom: ["<your-discord-user-id>"]
},
channels: {
discord: {
execApprovals: {
enabled: "auto", // or true
// approvers: ["<your-discord-user-id>"], // optional; explicit override
target: "dm" // or "channel"/"both"
}
}
}
}
Restart + verify:
openclaw gateway restart
openclaw approvals get --gateway
If you want, I can also give you the no-prompt (YOLO) config, but thatβs only for trusted hosts.
Docs: https://docs.openclaw.ai/tools/exec-approvals Β· https://docs.openclaw.ai/channels/discord
- OpenClaw 2026.4.5 (3e72c03)
- Your first suggestions, do they fit this version?
- I'd also like the YOLO as my server is private
Yes β for 2026.4.5 those suggestions are valid (that version already includes Discord exec-approver inference from commands.ownerAllowFrom).
If you want YOLO on a private server, set both policy layers (Gateway config + host approvals file):
openclaw config set tools.exec.host gateway
openclaw config set tools.exec.security full
openclaw config set tools.exec.ask off
openclaw gateway restart
openclaw approvals set --gateway --stdin <<'EOF'
{
version: 1,
defaults: {
security: "full",
ask: "off",
askFallback: "full"
}
}
EOF
Then verify effective state:
openclaw approvals get --gateway
You should see effective security=full, ask=off.