v8.0.4 — Hermes install-time MCP preservation
v8.0.4 — Hermes install-time MCP preservation (2026-08-24)
What changed
Fix: installing with the Hermes desktop app open no longer wipes the MCP board.
The installer stopped the Hermes gateway service (hermes gateway stop) but never
touched the Hermes desktop app (Hermes.exe). When the app was open during an install,
it held a stale in-memory copy of config.yaml from before the install and, on its
next save, rewrote mcp_servers: {} over the freshly written entries — silently
removing context7, github, and headroom.
The fix
INSTALL-AIO.ps1 now:
- Closes the desktop app before install work begins — captures the Hermes.exe
path, thenStop-Process -Forceon every instance, so the app cannot reload
mid-install against a half-written config. - Relaunches the app only after
config.yamlis final — the relaunch sits after
the install-state write, so the app comes back against the completed configuration
(and only when the install succeeded).
Verified: PowerShell parse OK (0 errors) and 9/9 behavioral checks — kill block
ordering before the plugin scanner, relaunch ordering after the state write, and the
real-path/bogus-path relaunch branches.
Scope
- Skill/MCP surface unchanged: 146 canonical skills per AI across the five provider trees.
- Hermes only. Claude Code, Codex, Grok, Kimi and Claude Desktop were not affected
(no long-lived GUI holding an in-memory config over their MCP files). - For an already-affected machine: re-add the three always-on servers, or re-run the
installer with the app closed, then restart the app.