Greptile Summary

This PR fixes the "triple window" bug on Windows by inserting a pre-flight schtasks /Query status check into the self-restart .cmd script, preventing it from launching a duplicate gateway process when the CLI has already restarted the scheduled task.

Key changes:

• Before each schtasks /Run attempt, the script now queries the task's current status and exits (goto cleanup) if the task is already in the Running state.
• The fix is zero-impact for config-watcher-initiated restarts (task won't be running when the script first checks) and self-cleaning (script still deletes itself on exit).

Notable concern:

• The findstr /I "Running" match against schtasks /Query /FO LIST output is locale-sensitive — on non-English Windows, the status string is localised (e.g. German, French), so the guard silently does nothing and the duplicate-window race can still occur for those users. Consider using (Get-ScheduledTask ...).State via PowerShell for a locale-agnostic check.

Confidence Score: 4/5

• Safe to merge for English Windows users; non-English users won't regress but also won't benefit from the fix.
• The fix is logically correct — the errorlevel semantics with the pipe are sound, the task names don't introduce false positives, and the failure mode on non-English Windows is benign (silent no-op, not a crash or new bug). The one actionable gap is locale sensitivity of the findstr "Running" check, which limits the fix's effectiveness to English Windows installations. That's worth addressing before this is considered fully resolved, but it doesn't break anything new.
• src/infra/windows-task-restart.ts — specifically the findstr /I "Running" status check on line 32.

This is a comment left during a code review.
Path: src/infra/windows-task-restart.ts
Line: 32-33

Comment:
**`findstr "Running"` is locale-sensitive**

`schtasks /Query /FO LIST` outputs localised status strings on non-English Windows installations (e.g. German "Wird ausgeführt", French "En cours d'exécution"). On those systems `findstr /I "Running"` will never match, so the early-exit guard silently does nothing and the script falls back to the original retry-12-times behaviour — leaving the duplicate-window bug present for non-English users.

A locale-independent alternative is to use PowerShell's `Get-ScheduledTask`, whose `.State` property is always an English enum value regardless of OS locale:

```
`powershell -Command "(Get-ScheduledTask -TaskName ${quotedTaskName} -ErrorAction SilentlyContinue).State" 2>nul | findstr /I "Running" >nul 2>&1`,
```

Or, if PowerShell is undesirable, check the exit code of `schtasks /Run` for the specific HRESULT `0x41301` ("task is already running") rather than querying status first — though that code isn't easily testable from a plain batch script.

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "fix(windows): prevent restart race from ..." | Re-trigger Greptile}

Addressed the locale-sensitivity feedback: replaced schtasks /Query /FO LIST | findstr /I Running with PowerShell's Get-ScheduledTask. The .State property returns an English enum (Running, Ready, etc.) regardless of OS locale, unlike schtasks which outputs localized status strings on non-English Windows.

CI: The only failure is security-fast which appears to be an infra flake (not related to this PR's changes). Could a maintainer re-run the failed job? All other 45/46 checks pass. Thanks!

Checked upstream main — no fixes landed for the failing \�xtension-signal\ / \�xtension-memory-core\ tests. These failures are pre-existing upstream flakes (Signal SSE stream timeout, memory module unexpected status) unrelated to the \Get-ScheduledTask\ change in this PR. The actual fix is solid. Could a maintainer re-run CI or confirm these are known flakes? Happy to rebase once upstream stabilises these tests.

Rebased onto current main and addressed the P2 review comment: task name single quotes are now escaped by doubling ('') for safe PowerShell string interpolation.

Friendly ping — CI is all green. Would appreciate a review when you get a chance. Thanks!

Another friendly ping — CI remains green and the fix is solid. Would appreciate a maintainer review when you get a chance. Thanks!

Codex review: needs real behavior proof before merge.

Summary
The PR adds a locale-stable PowerShell scheduled-task state probe before the Windows self-restart helper retries schtasks /Run, plus focused tests and a changelog entry.

Reproducibility: yes. Source inspection on current main shows the CLI restart path starts the scheduled task while the shutdown self-restart helper separately retries schtasks /Run, and the related report gives a concrete native Windows openclaw gateway restart path.

Real behavior proof
Needs real behavior proof before merge: Only tests/build/check output is described; no after-fix native Windows restart output, screenshot, recording, or redacted log demonstrates the real duplicate-window fix. After adding proof, update the PR body; ClawSweeper should re-review automatically. If it does not, ask a maintainer to comment @clawsweeper re-review.

Next step before merge
Human/contributor action is needed for after-fix native Windows behavior proof; there is no narrow code repair for ClawSweeper to make.

Security
Cleared: Security pass cleared the refreshed diff; the local PowerShell probe uses -NoProfile -NonInteractive and routes the command through the existing cmd quoting layer.

Maintainer refresh: rebased this onto current origin/main and kept the Windows scheduled-task restart fix aligned with the current restart-log/fallback helper.

Prepared head: 9a31bc85e7f8b12a8bc4cbd62b81e69f2c980eaf

Local verification passed:

• pnpm exec oxfmt --check --threads=1 src/infra/windows-task-restart.ts src/infra/windows-task-restart.test.ts CHANGELOG.md
• pnpm vitest run src/infra/windows-task-restart.test.ts
• pnpm build
• pnpm check

I also added focused coverage for the duplicate /Run guard and PowerShell task-name escaping, plus the changelog entry. Waiting on fresh GitHub CI before this can be merged.