Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Exec approval system on Windows platform cannot be disabled, making remote usage completely impossible

Steps to reproduce

1. Install OpenClaw v2026.3.31 on Windows\n2. Try to execute any exec command via remote connection\n3. Every single exec command requires manual approval\n4. No configuration option can disable the approval requirement

Expected behavior

Windows platform should support exec approval bypass (e.g. ask:off) like Linux/Mac, OR there should be a config option to disable exec approval for remote users

Actual behavior

Every exec command triggers approval prompt: 'Approval required'. On Windows, the error message is 'allowlist execution plan unavailable (unsupported platform)' — meaning Windows cannot support the approval bypass mechanism at all. Remote users (not physically at the machine) cannot approve, making the system completely unusable remotely.

OpenClaw version

2026.3.31

Operating system

Windows

Install method

npm

Model

MiniMax-M2.7

Provider / routing chain

minimax-cn

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

CRITICAL — Remote users cannot use OpenClaw at all. This effectively locks out any user who accesses OpenClaw remotely (not physically at the machine). This is a complete UX disaster for remote workflows.

Additional information

No response