openclaw - 💡(How to fix) Fix tools.exec.ask=off not respected by gateway after 2026.3.31 update [3 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#59053Fetched 2026-04-08 02:29:20
View on GitHub
Comments
3
Participants
3
Timeline
5
Reactions
0
Timeline (top)
commented ×3closed ×1locked ×1
RAW_BUFFERClick to expand / collapse

tools.exec.ask is set to off in config (confirmed via openclaw config get), but the gateway still prompts for exec approval on every command. Updated from 2026.3.23-2 to 2026.3.31, macOS 26.2 arm64. Gateway restarted after config change. Possibly related to the auth hardening changes in this release (trusted-proxy, local-direct fallback requiring token).

extent analysis

TL;DR

The issue may be resolved by re-examining the configuration for tools.exec.ask and ensuring that the auth hardening changes are properly configured.

Guidance

  • Verify that the tools.exec.ask configuration is correctly set to off and that the change has been successfully applied to the gateway.
  • Check the documentation for the auth hardening changes, specifically the trusted-proxy and local-direct fallback configurations, to ensure that they are properly set up and compatible with the tools.exec.ask setting.
  • Review the release notes for version 2026.3.31 to see if there are any specific instructions or considerations for configuring tools.exec.ask with the new auth hardening features.
  • Test the configuration with a simple command to see if the exec approval prompt still appears.

Notes

The issue may be specific to the interaction between the tools.exec.ask configuration and the new auth hardening features introduced in version 2026.3.31. Further investigation and testing may be needed to determine the root cause and find a solution.

Recommendation

Apply workaround: The user should try to re-configure the tools.exec.ask setting and auth hardening features to see if it resolves the issue, as the problem may be due to a misconfiguration or incompatibility between the two features.

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