Bug type

Regression (worked before, now fails)

Summary

Windows-native exec launcher wraps every token in single quotes and passes them to PowerShell as bare string expressions instead of invoking the command.

Steps to reproduce

1. On Windows-native install, run openclaw status via exec.
2. Observe ParserError: UnexpectedToken.
3. Try a zero-argument executable path.
4. Observe it is echoed instead of run.

Expected behavior

Commands should execute normally. PowerShell invocation should use & 'executable' 'arg1' 'arg2' so the executable is invoked instead of parsed as string literals.

Actual behavior

openclaw status fails with ParserError: UnexpectedToken because the launcher emits 'executable' 'arg1' 'arg2' without the PowerShell call operator. A zero-argument exec echoes C:\path\to\python.exe instead of launching it.

OpenClaw version

2026.3.13

Operating system

Windows 10 (x64, build 19045)

Install method

Windows-native (not Docker/WSL)

Model

NOT_ENOUGH_INFO

Provider / routing chain

NOT_ENOUGH_INFO

Additional provider/model setup details

NOT_ENOUGH_INFO

Logs, screenshots, and evidence

At line 1, PowerShell shows `'C:\Users\...\openclaw' 'status'` and errors with `Unexpected token ''status'' in expression or statement.` Zero-argument exec echoes the executable path instead of running it.

Impact and severity

Blocks all exec commands on Windows-native installs; .cmd wrappers and host exec commands do not run, making the Windows-native exec path unusable.

Additional information

Node v22.16.0; PowerShell default shell; reproducible on Windows-native only.