62 replies

OpenClaw `exec` tool on Windows: PowerShell commands producing no output

✅Solved

I'm encountering a critical problem with my OpenClaw agent running on Windows (Windows_NT 10.0.19045 (x64), node v24.13.0, shell=powershell).

The Issue: The

exec

exec

tool is consistently failing to capture any output from PowerShell commands. Even the most basic commands like

ls

ls

pwd

pwd

Test-Path

Test-Path

, and

Get-ChildItem

Get-ChildItem

execute without returning any information. This prevents the agent from performing any file system operations (reading, writing, listing directories, or diagnosing code).

Symptoms observed:
*

exec(command="ls <path>")

exec(command="ls <path>")

{"exec_response": {"output": "(no output)"}}

{"exec_response": {"output": "(no output)"}}

exec(command="pwd")

exec(command="pwd")

{"exec_response": {"output": "(no output)"}}

{"exec_response": {"output": "(no output)"}}

* This behavior is consistent across all PowerShell commands attempted.

Context:
* Operating System: Windows_NT 10.0.19045 (x64)
* Node.js Version: v24.13.0
* Agent Model: google/gemini-2.5-flash
* Shell: PowerShell

What I've tried/investigated:
* Attempted various PowerShell commands for directory listing and path testing.
* Conducted a web search which surfaced GitHub issues related to

exec

exec

tool problems on Windows, including:
* CMD syntax conflicts in PowerShell (#10868)
* Requests for native PowerShell mode (#6443)
* Troubleshooting "no output / stuck" issues potentially linked to proxy environment / process inheritance (#8057)

Solution

Perfect — you’re now on 2026.2.17. That’s the version that includes the Windows fix for “empty exec output”.

Now the only thing left is to confirm the Scheduled Task was rewritten (so it’s actually running the 2026.2.17 bits) and then re-test

exec

exec

from the bot.

1) Reinstall the gateway task (quick + safe)

Even though it’s “running”, do this once to ensure the task entrypoint isn’t stale:

openclaw gateway install --force
openclaw gateway restart

openclaw gateway install --force
openclaw gateway restart

2) Re-test exec (from Discord, by asking the bot/agent)

In this Discord thread, ask the bot:

- “Use exec to run:

echo STDOUT_OK

echo STDOUT_OK

”
- “Use exec to run:

pwd

pwd

”

Jump to solution

FotC�

Friends of the Crustacean 🦞🤝•3w ago•

62 replies

ChaseDanger (ChaseDanger)

OpenClaw `exec` tool on Windows: PowerShell commands producing no output

✅Solved

I'm encountering a critical problem with my OpenClaw agent running on Windows (Windows_NT 10.0.19045 (x64), node v24.13.0, shell=powershell).

The Issue: The

exec

exec

tool is consistently failing to capture any output from PowerShell commands. Even the most basic commands like

ls

ls

pwd

pwd

Test-Path

Test-Path

, and

Get-ChildItem

Get-ChildItem

execute without returning any information. This prevents the agent from performing any file system operations (reading, writing, listing directories, or diagnosing code).

Symptoms observed:
*

exec(command="ls <path>")

exec(command="ls <path>")

{"exec_response": {"output": "(no output)"}}

{"exec_response": {"output": "(no output)"}}

exec(command="pwd")

exec(command="pwd")

{"exec_response": {"output": "(no output)"}}

{"exec_response": {"output": "(no output)"}}

exec

exec

Solution

exec

exec

from the bot.

1) Reinstall the gateway task (quick + safe)

Even though it’s “running”, do this once to ensure the task entrypoint isn’t stale:

openclaw gateway install --force
openclaw gateway restart

openclaw gateway install --force
openclaw gateway restart

2) Re-test exec (from Discord, by asking the bot/agent)

In this Discord thread, ask the bot:

- “Use exec to run:

echo STDOUT_OK

echo STDOUT_OK

”
- “Use exec to run:

pwd

pwd

”

Jump to solution

OpenClaw `exec` tool on Windows: PowerShell commands producing no output

1) Reinstall the gateway task (quick + safe)

2) Re-test exec (from Discord, by asking the bot/agent)

OpenClaw `exec` tool on Windows: PowerShell commands producing no output

1) Reinstall the gateway task (quick + safe)

2) Re-test exec (from Discord, by asking the bot/agent)

Similar Threads

Similar Threads

Similar Threads