Repository navigation
Windows: prompt-started auto_update opens a Windows Terminal window for each due tool #14997
Unanswered
yusoofsh
asked this question in
Troubleshooting and bug reports
Replies: 2 comments
|
pr accepted |
0 replies
|
PR up: #15038. AI-assisted — Tool: Factory Droid; model: Qwen3.8 Max; version: unavailable. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
On Windows, each background update that
mise hook-envstarts for a dueauto_updatetool opens a visible Windows Terminal window titled with themise.exepath. The updates run one at a time, so with many opted-in tools a series of windows flashes up everytool_update.check_duration.Environment
2026.10.19 windows-x64 (2026-10-24), installed with WinGet (jdx.mise)1.24.12741.0, default terminal application left at "Let Windows decide"mise activate pwshauto_update = trueandtool_update.check_duration = "6h". Thetool-updateservice is not running.Steps to reproduce
auto_update = true, and activate mise in PowerShell.mise hook-env -s pwsh.What happens
The hook starts
mise __tool-update <tool> --id <id> --backgroundfor each due tool. Each of those startsmise __tool-update <tool> --id <id>, and a Windows Terminal window opens for that child while it runs. Captured from onemise hook-env -s pwsh(pid 6208) with three due tools:Earlier the same day I saw 13 of these
--backgroundprocesses queued from one parent.Expected behavior
Prompt-started updates run without a visible window, like the
tool-updateservice since 2026.10.9 (#14313).Possible cause
I have not built a fix, so this comes from reading
main:spawn_detachedinsrc/cli/tool_update.rsstarts the--backgroundprocess withDETACHED_PROCESS | CREATE_NO_WINDOW, so that process has no console.update_in_background_processstarts the update throughTick::start, which callswindows_job::spawn(&mut command, 0).windows_job::spawnadds onlyCREATE_SUSPENDED.hide_if_unattendeddescribes. Windows 11 opens it in Windows Terminal. The child is not--watch, soruns_unattendedis false and the window stays up.Passing
CREATE_NO_WINDOWfromTick::starton Windows, or at least on the--backgroundpath, should give the child a hidden console that its own children inherit. Thewindows_job::spawndoc comment already expects callers that need it to pass it.Workaround
Keep
mise __tool-update --watchrunning in a hidden console. I start it from awscriptscheduled task throughcmd /cwith window style 0. While it holds the service lock, prompts leave updates to it. With the service running, the same reproduction started no background processes and opened no windows.Possibly related: #14751 (a shim window; that reporter does not use
auto_update).AI-assisted — Tool: Factory Droid; model: anthropic/claude-opus-5.5; version: unavailable.
All reactions