Summary

• Problem: On Windows, openclaw completion --install --shell powershell silently printed "not supported" and exited without writing anything. Additionally, the time-format detection always invoked PS 5.1 (powershell.exe) even when PS7 (pwsh.exe) was installed.
• Why it matters: PowerShell is the default shell on Windows — completion install was completely broken for the platform, and PS5.1 lacks features and is deprecated on modern Windows.
• What changed: Added the missing powershell branch in installCompletion(), corrected the source-line syntax from bash source to PS dot-source (. ), and switched detectSystemTimeFormat() to use resolvePowerShellPath() (which already prefers PS7).
• What did NOT change: No changes to completion script generation, shell detection logic, or any non-Windows code paths.

Change Type

• Bug fix

Scope

• UI / DX

Linked Issue/PR

• Closes # (no existing issue — discovered while using OpenClaw on Windows)

User-visible / Behavior Changes

• openclaw completion --install --shell powershell now works on Windows: creates/updates Microsoft.PowerShell_profile.ps1 with . "${cachePath}" dot-source syntax.
• On Windows with PS7 installed, time-format detection now correctly invokes pwsh.exe instead of powershell.exe.

Security Impact

• New permissions/capabilities? No
• Secrets/tokens handling changed? No
• New/changed network calls? No
• Command/tool execution surface changed? No — resolvePowerShellPath() was already used throughout shell-utils.ts; this aligns date-time.ts with the existing pattern.
• Data access scope changed? No

Repro + Verification

Environment

• OS: Windows 11 (x64), Node v24.7.0
• Runtime/container: Native Windows (no WSL)
• Model/provider: N/A
• Integration/channel: N/A
• Relevant config: N/A

Steps

1. Install OpenClaw on Windows with PowerShell 5.1 as default shell
2. Run openclaw completion --write-state
3. Run openclaw completion --install --shell powershell

Expected

• Profile at %USERPROFILE%\Documents\PowerShell\Microsoft.PowerShell_profile.ps1 is created/updated with . "${cachePath}"

Actual (before fix)

• Prints Automated installation not supported for powershell yet. and exits with no file written

Evidence

• Failing test/log before + passing after

# Before fix: installCompletion("powershell") hit the else-branch silently
# After fix: 7/7 tests pass

✓ detects pwsh from SHELL env
✓ detects powershell from SHELL env basename
✓ returns zsh as default when SHELL is unset
✓ cache path for powershell uses .ps1 extension
✓ installs PowerShell completion with dot-source syntax
✓ detects completion as installed after writing profile
✓ does not use bash source keyword in PowerShell profile

Test Files  1 passed (1)
Tests       7 passed (7)

Human Verification

• Verified scenarios: TypeScript typecheck (tsc --noEmit) clean, oxlint 0 errors, oxfmt clean, all 7 new tests pass on Windows.
• Edge cases checked: Profile already exists (idempotent update), profile directory doesn't exist (auto-created), isCompletionInstalled() correctly detects after install.
• What I did not verify: Actual runtime execution on macOS/Linux (no code path changes for those platforms); PS7 time-format path requires a Windows machine with pwsh.exe installed.

Compatibility / Migration

• Backward compatible? Yes
• Config/env changes? No
• Migration needed? No

Failure Recovery

• How to revert: git revert the single commit; no config changes were made.
• Known bad symptoms: None expected — the PS branch was entirely missing before, so any regression would be a no-op (same "not supported" behaviour as before).

Risks and Mitigations

• Risk: Profile path for PowerShell on macOS/Linux (.config/powershell/Microsoft.PowerShell_profile.ps1) — untested on those platforms with pwsh installed.
  • Mitigation: Path logic was already present in getShellProfilePath() and is unchanged; this PR only wires up the call that was missing.