openclaw - 💡(How to fix) Fix [Bug]: Exec approval popups cannot be disabled — flood of popups with no way to turn them off [2 comments, 3 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#59010Fetched 2026-04-08 02:29:58
View on GitHub
Comments
2
Participants
3
Timeline
5
Reactions
0
Author
Timeline (top)
cross-referenced ×3commented ×2

After updating to 2026.4.1, the web UI is flooded with "Exec approval needed" popups that cannot be disabled. Setting tools.exec.ask = "off" has no effect on existing sessions. The popups show Ask: off but still appear. Clicking "Always allow" or "Deny" just clears that one popup — the next exec triggers another.

This is completely unusable for a single-operator private setup. There is no way to say "never ask me about exec again."

Root Cause

After updating to 2026.4.1, the web UI is flooded with "Exec approval needed" popups that cannot be disabled. Setting tools.exec.ask = "off" has no effect on existing sessions. The popups show Ask: off but still appear. Clicking "Always allow" or "Deny" just clears that one popup — the next exec triggers another.

This is completely unusable for a single-operator private setup. There is no way to say "never ask me about exec again."

RAW_BUFFERClick to expand / collapse

Summary

After updating to 2026.4.1, the web UI is flooded with "Exec approval needed" popups that cannot be disabled. Setting tools.exec.ask = "off" has no effect on existing sessions. The popups show Ask: off but still appear. Clicking "Always allow" or "Deny" just clears that one popup — the next exec triggers another.

This is completely unusable for a single-operator private setup. There is no way to say "never ask me about exec again."

Specific failure

  • Popup shows Ask: off AND Security: allowlist simultaneously — contradictory state
  • "Approval failed: GatewayRequestError: unknown or expired approval id" — clicking buttons fails
  • Stale approval requests persist across gateway restarts
  • 8+ pending approvals shown at once with no "dismiss all" option

What operators need

A single config option: "never show exec approval popups, just run commands." This should be the default for local single-user gateway setups. Instead, after this update, it is impossible to achieve this state.

Impact

Full day of work lost. An operator running a private local gateway should never have to approve their own agent's commands. This security model is designed for multi-user shared gateways — forcing it on single-user setups with no escape hatch is a critical UX regression.

Environment

  • Version: 2026.4.1
  • Platform: macOS, single-user LaunchAgent gateway
  • Related: #58881, #58885, #59003, #59006

extent analysis

TL;DR

Downgrade to a previous version or wait for a patch, as the current version has a critical UX regression causing unavoidable "Exec approval needed" popups.

Guidance

  • Review related issues (#58881, #58885, #59003, #59006) for potential workarounds or insights into the problem.
  • Consider configuring the gateway to run in a mode that minimizes the need for exec approvals, although the exact method to do this is not specified in the given information.
  • Reach out to the development team or community for a potential fix or temporary solution, as the current behavior is causing significant usability issues.
  • Evaluate the possibility of manually editing configuration files to override the exec approval behavior, but proceed with caution as this could introduce unintended consequences.

Notes

The provided information does not specify a direct fix for the issue, and the exact configuration options or code changes required to resolve the problem are not clear. The issue seems to be related to a change in the security model that is not suitable for single-user setups.

Recommendation

Apply workaround: Given the critical nature of the regression and the impact on usability, applying a workaround or downgrading until a fix is available seems to be the most practical approach. The reason is that the current version's behavior is unusable for single-operator private setups, and waiting for or seeking a patch is necessary to restore functionality.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING