Skip to content

fix(wasm): add windowsHide to spawnSync re-exec to suppress terminal popup on Windows#521

Open
JirA44 wants to merge 1 commit into
colbymchenry:mainfrom
JirA44:fix/windows-terminal-popup
Open

fix(wasm): add windowsHide to spawnSync re-exec to suppress terminal popup on Windows#521
JirA44 wants to merge 1 commit into
colbymchenry:mainfrom
JirA44:fix/windows-terminal-popup

Conversation

@JirA44
Copy link
Copy Markdown

@JirA44 JirA44 commented May 28, 2026

The spawnSync call in relaunchWithWasmRuntimeFlagsIfNeeded was missing windowsHide: true.

When the MCP server is launched by a host (e.g. VS Code) it is spawned with windowsHide: true, so it has no attached console. When the server then re-execs itself with --liftoff-only via spawnSync — without windowsHide: true — Windows finds no existing console to inherit and opens a new one, producing the visible terminal flash on every save/MCP invocation.

The fix is one line: add windowsHide: true to the spawnSync options, matching the flag already present on the initial daemon spawn in src/mcp/index.ts.

Fixes #510

…popup on Windows

The spawnSync call that re-execs Node with --liftoff-only was missing
windowsHide: true. When the MCP server starts without a console (spawned
with windowsHide: true from the host), the re-exec child inherits no
console and Windows opens a new one instead, causing the visible terminal
flash on every codegraph invocation.

Fixes colbymchenry#510
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Annoying terminal pops up

1 participant