Hide the deploy launcher console window on Windows#88
Open
rjckkkkk wants to merge 1 commit into
Open
Conversation
The native runtime launches engines via `schtasks /it`, which runs the launcher .bat in a visible cmd.exe console on the interactive desktop (Session 1). Because that cmd is the engine process's parent, the console stayed open for the whole life of the deployment — users saw a "C:\WINDOWS\SYSTEM32\cmd" window pop up and linger on every deploy. Wrap the .bat in a tiny VBS launcher and run it via wscript with window style 0 (WScript.Shell.Run cmd, 0, False) so the cmd console is hidden. The engine still runs in Session 1 (GPU access intact); PID discovery by port/name is unchanged. Verified: llama-server runs (parent cmd.exe, hidden), deploy reaches ready, launcher .bat/.vbs are cleaned up. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
rjckkkkk
added a commit
that referenced
this pull request
Jun 12, 2026
) New version-stamped build aima-windows-amd64-v0.5-dev-amd-strix-halo-20260612.exe (source commit fa35aa4) on top of the HIP-engine build. Adds, vs the 20260610 exe: #87 native deploy readiness uses the real runtime name (no false "not ready") #88 deploy launcher hidden (no cmd.exe console popup) via VBS launcher #89 Qwen2.5-VL-3B-Instruct catalog knowledge (vlm + aliases + verified perf) #90 zero-config vision: llama.cpp --mmproj auto-wired for VL gguf models #91 openclaw sync preflight-probes :6188 and warns loudly when unreachable serve.bat now points at the 20260612 exe; older builds kept for rollback. README build table + fixes list + OpenClaw data-plane guidance updated. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
On Windows the native runtime launches engines via
schtasks /it, which runs the launcher.batin a visible cmd.exe console on the interactive desktop. That cmd is the engine's parent, so theC:\WINDOWS\SYSTEM32\cmdwindow pops up and stays open for the whole life of the deployment on every deploy.Fix
Wrap the
.batin a one-line VBS launcher run viawscriptwith window style 0 (WScript.Shell.Run cmd, 0, False) → the console is hidden. Engine still runs in Session 1 (GPU access intact); PID discovery unchanged.Verified (AMD Strix Halo Win11 rig)
aima runreaches ready;llama-server.exeruns with parentcmd.exe(now hidden), serving on its port; launcher.bat/.vbscleaned up after PID discovery.🤖 Generated with Claude Code