Is Hermes Agent v0.11.0 stable?
75/100Fact score: 75/100 · evidence-based, not a YES/NO verdict
“v0.11.0 has defensible Windows, channel, Docker, TUI, and auth regressions; score remains website-calculated.”
Stability Score
75Base
80
Evidence
-20
Votes
-0
Survived
+15
Curated
+0
80 base−20 evidence−0 votes+15 (3×5 days survived)=75
Affected components
windowswechatuiidentityplugin-installprovider-integrationcron
Install this version
npm install hermes-agent@0.11.0Score Evidence
| Issue | Area | Type | Penalty | Reason |
|---|---|---|---|---|
| NousResearch/hermes-agent#17999 → | windows | runtime | -4 | v0.11.0 native Windows read_file and terminal tools fail on valid local paths |
| NousResearch/hermes-agent#18437 → | channel-specific | -3 | v0.11.0 Weixin send_message media path fails with event-loop errors outside gateway | |
| NousResearch/hermes-agent#15094 → | ui | runtime | -2 | v0.11.0 TUI /resume and /model picker overlays become invisible |
| NousResearch/hermes-agent#15099 → | identity | runtime | -4 | v0.11.0 OAuth refresh-token rotation is not persisted, revoking profile sessions |
| NousResearch/hermes-agent#15832 → | plugin-install | runtime | -3 | v0.11.0 Dockerfile USER hermes bypasses UID remap and can crash-loop on /opt/data permissions |
| NousResearch/hermes-agent#15973 → | channel-specific | -2 | 0.11.0 WeCom file reception remains broken after update/restart | |
| NousResearch/hermes-agent#17201 → | ui | provider-integration | -1 | v0.11.0 CLI reasoning box is not displayed for kimi-coding provider |
| NousResearch/hermes-agent#20586 → | cron | provider-integration | -1 | Issue reports cron jobs failing with provider.sort invalid input after v0.11.0 |