Summary

Exec tool returns empty output on Windows regardless of command - stdout/stderr not captured by Node.js child_process

Steps to reproduce

1. Send exec command: cmd.exe /c echo HELLO_EXEC
2. Tool runs and completes (~100-200ms)
3. Response: (no output)

Expected behavior

Command output is captured and returned (e.g., HELLO_EXEC for echo command)

Actual behavior

Tool returns (no output) - stdout/stderr is empty. Trace logs show tool start/end but no stdout/stderr content between them. This is a Windows child_process capture bug, not a Discord UI issue.

OpenClaw version

2026.2.14

Operating system

Windows 11 (Windows_NT 10.0.26200)

Install method

No response

Logs, screenshots, and evidence

Trace log (C:\tmp\openclaw\openclaw-2026-02-16.log):

Line 5718: {"subsystem":"agent/embedded","1":"embedded run tool start: runId=... tool=exec toolCallId=...",...,"time":"2026-02-16T11:44:54.230Z"}

Line 5720: {"subsystem":"agent/embedded","1":"embedded run tool end: runId=... tool=exec toolCallId=...",...,"time":"2026-02-16T11:44:54.394Z"}

~164ms execution, no stdout/stderr in logs. Same for PowerShell, cmd, echo - all return empty.

Config: exec.security: "full"
Node: v24.13.1

Impact and severity

Affected: All Windows users using exec tool
Severity: High (blocks critical functionality)
Frequency: 100% - always reproduces
Consequence: Cannot run shell commands, cron jobs fail, automation broken

Additional information

No response