Summary

Windows nodes fail to create the exec-approvals socket/Named Pipe automatically on startup, causing all remote command executions to fail with timeout errors.

Environment

• OS: Windows 11 Pro Build 26200.7840
• OpenClaw Version: 2026.2.15 (confirmed still present in 2026.2.26)
• Hardware: Intel i5-13400F, NVIDIA RTX 3050 6GB
• Node Configuration: Running as paired node (not full Gateway)

Expected Behavior

When OpenClaw node starts on Windows, it should:

1. Create the exec-approvals socket at C:\Users\<user>\.openclaw\exec-approvals.sock
2. Start the socket server process automatically
3. Accept remote command execution requests from paired Gateway

Actual Behavior

1. Socket file/Named Pipe is never created
2. Socket server process does not start
3. All remote commands fail with: "exec denied: approval timed out"
4. Test-Path confirms socket does not exist
5. Named Pipes list shows no exec-approvals pipe

Steps to Reproduce

1. Install OpenClaw on Windows 11
2. Configure as node (not full Gateway)
3. Pair with a Gateway on another machine (e.g., macOS)
4. Attempt remote command execution via nodes invoke or nodes run
5. Observe timeout errors

Logs/Evidence

Socket defined: C:\Users\jose-\.openclaw\exec-approvals.sock
Socket doesn't exist: Test-Path returns False
All remote commands fail: "exec denied: approval timed out"

Workarounds Attempted (All Failed)

• Added "defaults": { "mode": "allow-all" } in config
• Killed duplicate processes, restarted with single process
• Multiple restarts and config reloads
• Manual socket creation attempts

Current Workaround

Running a full Gateway on the Windows PC instead of node mode. This works but:

• Requires separate channel configuration (Telegram bot)
• Loses the simplified remote execution model
• Adds unnecessary overhead for simple command delegation

Impact

• Windows machines cannot function as remote execution nodes
• Forces users to run full Gateway instances for simple remote commands
• Breaks the intended node architecture on Windows

Related

This appears to be Windows-specific. macOS and Linux nodes work correctly with socket creation.

Note: Reported after reviewing changelogs through 2026.2.26 with no mention of Windows socket fixes.