Cold-start reliability release
Hermes Launcher now starts the local workstation stack before it tries to connect. A fully stopped machine no longer remains on CONNECTING with ECONNREFUSED 127.0.0.1:9119.
Highlights
- Start and await the configured model server and Hermes backend during a cold desktop launch.
- Join an already-starting supervisor when launcher and script startup overlap.
- Prevent a losing supervisor process from deleting the active supervisor's PID state.
- Ignore stale status from an earlier supervisor process.
- Preserve the portable model, profile, runtime, path, acceleration, and port configuration introduced in v0.18.0.
Update an existing installation
Pull the latest public repository and rerun the idempotent setup:
Set-Location D:\Hermes-Local
git pull
& '.\Setup-Hermes-Local.ps1' -NonInteractiveThen install the v0.18.1 Windows setup asset below, or run the rebuilt dist\Hermes Launcher.exe directly.
Fresh installation
Clone the repository, run Setup-Hermes-Local.ps1, then use either Windows launcher asset below. The release binaries contain the launcher, not the model weights or managed runtimes.
The binaries are not Authenticode-signed, so Windows may show a reputation warning. Verify SHA256SUMS.txt before running them.
Verification
- Real packaged cold start with ports 8011 and 9119 initially down: passed in 40.7 seconds.
- Two simultaneous start callers joined one supervisor and both succeeded.
- Clean stop removed the supervisor PID record and closed both ports.
- Portable extraction and live Home/TUI test: passed.
- Model, runtime, port, and profile persistence test: passed.
- PowerShell parsing, configuration schema validation, TypeScript, focused Electron tests, changed-file lint, and exact eight-patch reconstruction: passed.
- Microsoft Defender found no threats in the installer or portable artifacts.