Summary

On Windows, Telegram-triggered execs still fail in OpenClaw's allowlist/command-rebuild path before approval can help. The gateway restarts cleanly, but a simple PowerShell command is rebuilt into an invalid PowerShell invocation and/or denied with exec denied: allowlist miss.

Environment

• OpenClaw package: 2026.3.13
• Windows host
• Gateway on loopback port 18889
• Telegram approver configured for 6518873123

What I tested

1. Updated Telegram exec approvals in C:\Users\ocdev\.openclaw\openclaw.json and restarted the gateway.
2. Retried a simple Telegram command to list a workspace directory.
3. Observed a rebuilt PowerShell command like:
   ...powershell.exe' '-NoLogo' '-NoProfile' '-Command' 'Get-ChildItem ...'
   PowerShell rejected it with parser errors such as Unexpected token ''-NoLogo'' in expression or statement.
4. Retried the direct command:
   Get-ChildItem -LiteralPath C:\Users\ocdev\.openclaw\workspace
   and got exec denied: allowlist miss.
5. I also tested a local bundle patch to canonicalize bare powershell to C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe and to relax the Windows token scan, but it did not fix the issue. I reverted those edits.

Relevant logs

• C:\Users\ocdev\AppData\Local\Temp\openclaw\openclaw-2026-03-23.log
  • 14:44:55 Runtime: running ...
  • 14:47:10 / 14:47:19 exec denied: allowlist miss
• Session transcript:
  • C:\Users\ocdev\.openclaw\agents\main\sessions\573231c4-5164-4f01-afcd-a8138904b29d.jsonl

Notes

• C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe exists on this machine.
• Get-Command powershell resolves to that path.
• This looks like an OpenClaw Windows exec allowlist / command-rewrite bug, not a missing PowerShell install or Telegram approval routing issue.