Windows 10 (build 19044): Node Sandbox blocks all commands with no way to disable

[naturedogdog]

Bug type: Feature gap / Compatibility

Windows version: Windows 10 21H2 (build 19044)

Companion version: v0.6.0-alpha.1 (OpenClawTray-Setup-x64.exe)

Summary:
After upgrading to v0.6.0-alpha.1, the Node Sandbox page shows "Node Sandbox unavailable — commands blocked" because MXC sandboxing requires build 26100+. There is no option to disable sandboxing or fall back to unsandboxed execution, so all remote exec commands are completely blocked on Windows 10.

Steps to reproduce:

1. Install OpenClawTray-Setup-x64.exe v0.6.0-alpha.1 on Windows 10 build 19044
2. Connect to remote gateway successfully
3. Try to execute any command via host=node → blocked

Expected behavior:
Either provide an "Unprotected" / disable-sandbox option for older Windows versions, or fall back to unsandboxed execution with a warning.

Actual behavior:
The Sandbox page shows the error with no workaround. The security level options (Locked Down / Recommended / Unprotected) are not clickable. All commands are blocked.

Previous version:
The previous version of the Windows node worked fine on this same machine without sandbox requirements.

[clawsweeper]

ClawSweeper status: review started.

I am starting a fresh review of this issue: Windows 10 (build 19044): Node Sandbox blocks all commands with no way to disable This is item 1/1 in the current shard. Shard 0/1.

This placeholder means the worker is alive and reading the current context. I will edit this same comment with the actual review when the claws are done clicking.

Crustacean status: shell secured, claws on keyboard, evidence pebbles being sorted.

[shanselman]

@naturedogdog yes Alpha is SUPER alpha...will fix this up ASAP