openclaw - 💡(How to fix) Fix [Bug]: tools.exec.ask=off and exec-approvals.json defaults ignored — approval popups cannot be disabled [5 comments, 5 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#58881Fetched 2026-04-08 02:31:34
View on GitHub
Comments
5
Participants
5
Timeline
14
Reactions
0
Author
Timeline (top)
cross-referenced ×6commented ×4subscribed ×2closed ×1

Prior to recent updates, exec commands ran without approval popups for local single-user gateway setups. After updating, the approval popup system activates on every exec command and cannot be disabled despite setting `tools.exec.ask=off` globally and per-agent, and setting `defaults.ask=off` + `agents.*.ask=off` in `exec-approvals.json`.

The popup always shows `Security: allowlist` and `Ask: on-miss` regardless of config, indicating the runtime is not reading the configured values.

Root Cause

Prior to recent updates, exec commands ran without approval popups for local single-user gateway setups. After updating, the approval popup system activates on every exec command and cannot be disabled despite setting `tools.exec.ask=off` globally and per-agent, and setting `defaults.ask=off` + `agents.*.ask=off` in `exec-approvals.json`.

The popup always shows `Security: allowlist` and `Ask: on-miss` regardless of config, indicating the runtime is not reading the configured values.

RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (regression from recent updates)

Summary

Prior to recent updates, exec commands ran without approval popups for local single-user gateway setups. After updating, the approval popup system activates on every exec command and cannot be disabled despite setting `tools.exec.ask=off` globally and per-agent, and setting `defaults.ask=off` + `agents.*.ask=off` in `exec-approvals.json`.

The popup always shows `Security: allowlist` and `Ask: on-miss` regardless of config, indicating the runtime is not reading the configured values.

Steps to reproduce

  1. Single-user local gateway setup (macOS, LaunchAgent)
  2. Set `tools.exec.ask = "off"` via `openclaw config set tools.exec.ask off`
  3. Set per-agent `tools.exec.ask = "off"` and `tools.exec.host = "gateway"`
  4. Set `defaults.ask = "off"` and `agents.*.ask = "off"` in `~/.openclaw/exec-approvals.json`
  5. Restart gateway
  6. Agent (Arthur, id: main) attempts any exec command (e.g. `/Users/greg/clawd/.venv/bin/python script.py`)
  7. Approval popup appears every time — never skipped

Expected behavior

With `ask=off` set at both global and per-agent level, exec commands should run without any approval prompt. This worked correctly before recent updates to the exec approval system.

Actual behavior

Every exec command triggers an approval popup. Clicking "Always allow" registers the entry but the popup reappears on the next gateway restart. Cron-triggered agents cannot self-approve, making all scheduled exec tasks completely broken.

The popup shows:

  • Security: `allowlist`
  • Ask: `on-miss`

...regardless of configuration.

Environment

  • Version: 2026.4.1
  • Platform: macOS (LaunchAgent gateway)
  • Agent sandbox: `workspaceRoot` + `workspaceAccess: rw`
  • `tools.exec.host = "gateway"` set globally and per-agent

Impact

This regression makes all cron-triggered exec commands non-functional in single-user private setups where approval popups are inappropriate. The feature worked before the exec approval system was introduced/changed.

extent analysis

TL;DR

The most likely fix is to review and adjust the configuration settings for tools.exec.ask and defaults.ask to ensure they are correctly applied and override the default approval popup behavior.

Guidance

  • Verify that the exec-approvals.json file is correctly formatted and that the defaults.ask and agents.*.ask settings are properly set to "off".
  • Check the gateway logs for any errors or warnings related to the exec-approvals.json file or the tools.exec.ask setting.
  • Try setting tools.exec.ask to "off" at the global level and then restart the gateway to see if the setting is being applied correctly.
  • Review the documentation for the exec-approvals.json file to ensure that the agents.*.ask setting is correctly configured to override the default behavior.

Example

No code snippet is provided as the issue seems to be related to configuration settings rather than code.

Notes

The issue may be related to a change in the exec approval system, and it's possible that the configuration settings need to be adjusted to accommodate this change. Additionally, the fact that the popup shows "Security: allowlist" and "Ask: on-miss" regardless of configuration suggests that there may be an issue with the way the configuration settings are being applied.

Recommendation

Apply workaround: Review and adjust the configuration settings for tools.exec.ask and defaults.ask to ensure they are correctly applied and override the default approval popup behavior. This is recommended because the issue seems to be related to a change in the exec approval system, and adjusting the configuration settings may be the most straightforward way to resolve the issue.

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…

FAQ

Expected behavior

With `ask=off` set at both global and per-agent level, exec commands should run without any approval prompt. This worked correctly before recent updates to the exec approval system.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING