Problem

The Windows platform page only covers WSL2 and implies native Windows is unsupported. In practice, OpenClaw runs well natively on Windows via Node.js + PowerShell with no WSL2 required.

Missing documentation

Auto-start options:

• Task Scheduler (logon trigger) - more reliable than NSSM on modern Windows
• Startup folder shortcut + watchdog script - good for crash recovery
• NSSM vs Task Scheduler tradeoffs and known conflict scenarios

PowerShell gotchas:

• && is invalid in PowerShell (use ; or separate calls) - causes silent failures in exec chains
• gateway.cmd idempotency guard pattern (check port before starting to prevent duplicate instances)
• MultipleInstances = IgnoreNew on the scheduled task

Auth on Windows:

• Token-based auth (sk-ant-oat01-*) works natively without special config
• type: token in auth-profiles.json vs type: api_key distinction matters

Proposed fix

1. Add a 'Native Windows (no WSL2)' section to platforms/windows.md
2. Update the framing - native Windows is a supported and working deployment target
3. Add a PowerShell syntax note to the troubleshooting guide