Summary

Opção 1 (Direta):

[Windows] exec tool returns "(no output)" for all commands
Opção 2 (Técnica):

Tool "exec" fails to capture stdout/stderr on Windows
Opção 3 (Completa):

[Windows] exec commands execute but return empty output - stdout capture broken
Opção 4 (Se quiser em português):

[Bug Windows] Comandos exec retornam "(no output)" mesmo com saída esperada
Minha recomendação: Opção 1 — curta, clara, já dá pra entender o problema só lendo o título.

Steps to reproduce

1. Start an OpenClaw session on Windows
2. Use the exec tool with any command that should produce stdout
3. Example command: echo hello world
4. Expected: returns "hello world"
5. Actual: returns "(no output)"
6. Additional tests done:
   • PowerShell: Get-ChildItem → "(no output)"
   • CMD: cmd /c "echo test" → "(no output)"
   • Command still executes (file operations work) but no stdout captured

Expected behavior

markdown The exec tool should return the actual stdout/stderr output of the executed command. For example: - echo teste123 should return: teste123 - whoami should return the current username - Get-ChildItem should return the directory listing Ou em versão mais simples: markdown Commands should return their actual output (stdout), not "(no output)". Versão completa: markdown When executing a command via the exec tool, the response should contain the actual standard output (stdout) of that command. Example: - Command: echo hello → Expected output: hello - Command: whoami → Expected output: DESKTOP-IROPV48\\MJunior Currently all commands return "(no output)" despite executing successfully.

Actual behavior

markdown The exec tool always returns (no output) regardless of the command executed. Commands appear to execute (side effects like file creation work) but no stdout/stderr is captured or returned. Ou versão mais simples: markdown All commands return (no output) instead of their actual output. Versão completa: markdown - Every command executed via exec returns (no output) - Commands DO execute (file operations, script running work) - Stdout/stderr is not captured - No error messages are shown - Result is always (no output) even for commands that should produce visible output

OpenClaw version

2026.2.15

Operating system

Win 11

Install method

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response