🦞ClawTips
← Back to library

Windows skill execution fix: ensure .exe/.cmd/.bat binaries are detected

Targets Windows hosts where skills fail because binary detection and command spawning differ from Unix. Validate PATH + shell behavior before blaming skill code.

GITHUBDiscovered 2026-02-14Author bsormagec
Prerequisites
  • OpenClaw runs on Windows (PowerShell/CMD environment).
  • Target tool binaries (e.g., gcloud/custom scripts) are installed and in PATH.
Steps
  1. Confirm binary resolution in PowerShell (Get-Command) for tool names and extension variants.
  2. Run OpenClaw command path that triggers the skill/hook and capture any spawn errors.
  3. Upgrade to a build containing Windows detection fix, then rerun the same workflow unchanged.
  4. For custom scripts, keep explicit extension (.cmd/.bat) in config to reduce ambiguity.
Commands
Get-Command gcloud
where gcloud
openclaw gateway status
Verify

Previously failing skill/hook now executes successfully on Windows without manual shell wrapping.

Caveats
  • Enabling shell execution can change argument quoting behavior for edge-case commands（需验证）.
  • PATH shadowing on Windows can resolve unexpected binaries; pin full path for critical jobs.
Source attribution

This tip is aggregated from community/public sources and preserved with attribution.

Open original source ↗
Visit original post