fix(windows): add windowsHide to all Windows spawn resolution paths#48320
fix(windows): add windowsHide to all Windows spawn resolution paths#48320TerminalsandCoffee wants to merge 1 commit intoopenclaw:mainfrom
Conversation
The direct and shell-fallback resolution paths in the plugin SDK's Windows spawn resolver were missing windowsHide: true, causing visible cmd.exe console windows to flash on every ACP spawn on Windows desktop. Closes openclaw#40340 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Greptile SummaryThis PR closes a Windows UX regression where every ACP spawn would flash a visible
Confidence Score: 5/5
Last reviewed commit: 8d36db3 |
|
I reviewed this change and the implementation looks sound. The patch fills the two missing Windows resolution outcomes in I also checked the surrounding call sites, and the resolved The tests line up with the change: there’s a new direct- From a code and scope perspective, this looks reasonable to land. |
|
Codex review: needs changes before merge. Summary Reproducibility: yes. Source inspection on current main shows Win32 direct Next step before merge Security Review findings
Review detailsBest possible solution: Land or replace this PR with the shared resolver fix on current main, SDK-level regression tests, and a changelog entry, while leaving MCP proxy production spawn work to #60678. Do we have a high-confidence way to reproduce the issue? Yes. Source inspection on current main shows Win32 direct Is this the best way to solve the issue? No for the branch as currently shaped. Setting Full review comments:
Overall correctness: patch is incorrect Acceptance criteria:
What I checked:
Likely related people:
Codex review notes: model gpt-5.5, reasoning high; reviewed against 5f373ae4d3db. |
The execLoginShellEnvZero helper was missing windowsHide: true, causing a PowerShell console window to flash briefly during gateway startup on Windows. This completes the fix started in openclaw#48320 and openclaw#70308 for the v2026.5.4 code path. Closes openclaw#78159
The execLoginShellEnvZero helper was missing windowsHide: true, causing a PowerShell console window to flash briefly during gateway startup on Windows. This completes the fix started in openclaw#48320 and openclaw#70308 for the v2026.5.4 code path. Closes openclaw#78159
|
Thanks for the fix here. I rechecked this against current main while working through the Microsoft tracker, and this PR is now obsolete rather than mergeable as-is.\n\nCurrent main already carries the Windows spawn hiding behavior in the shared Windows spawn helper paths, including |
Summary
windowsHide: trueto thedirectandshell-fallbackresolution paths insrc/plugin-sdk/windows-spawn.tsnode-entrypoint,exe-entrypoint) already set itwindowsHidefrom the resolution, so the fix propagates automatically.exeresolution assertingwindowsHide: truewindowsHide: truewindowsHide: trueto rawspawn()calls in test files to prevent console flash during test runs on WindowsRoot Cause
resolveWindowsSpawnProgramCandidate()only setwindowsHide: truefornode-entrypointandexe-entrypointresolutions. Thedirectpath (e.g..exefiles resolved on Windows) and theshell-fallbackpath (unresolved.cmdwrappers) leftwindowsHideasundefined, causing every ACP spawn to flash a visiblecmd.execonsole window.Test plan
pnpm vitest run extensions/acpx/src/runtime-internals/process.test.ts— 15/15 passingsets windowsHide on direct exe resolution on windowsfalls back to shell modenow assertswindowsHide: truewindowsHideis ignored on non-Windows platformsCloses #40340
🤖 Generated with Claude Code