Is Hermes Agent v0.9.0 stable?
63/100Fact score: 63/100 · evidence-based, not a YES/NO verdict
“v0.9.0 improves the line but still has sharp edges in dashboard/gateway connectivity, custom-provider paths, memory prefetch, Feishu approvals, and OpenRouter.”
Stability Score
63Base
80
Evidence
-26
Votes
-0
Survived
+9
Curated
+0
80 base−26 evidence−0 votes+9 (3×3 days survived)=63
Affected components
webchatgatewayprovider-integrationmemoryfeishuapproval-boundarymodel-routinglocal-model
Install this version
npm install hermes-agent@0.9.0Score Evidence
| Issue | Area | Type | Penalty | Reason |
|---|---|---|---|---|
| NousResearch/hermes-agent#9313 → | webchat | runtime | -3 | 0.9.0 upgrade can leave web dashboard showing Gateway not online despite gateway process running |
| NousResearch/hermes-agent#9711 → | provider-integration | runtime | -3 | v0.9.0 named custom providers ignore api_mode and always create OpenAI client |
| NousResearch/hermes-agent#9973 → | memory | kernel | -4 | 0.9.0/v2026.4.13 gateway recreates AIAgent each turn and loses memory prefetch cache |
| NousResearch/hermes-agent#10202 → | gateway | runtime | -3 | v0.9.0 dashboard command uses gateway run --replace and can kill Feishu WSS connection |
| NousResearch/hermes-agent#11096 → | model-routing | kernel | -4 | v0.9.0 reproducibly hits context_length override, thinking-block session, and config/env precedence bugs |
| NousResearch/hermes-agent#11249 → | provider-integration | runtime | -4 | Hermes Agent v0.9.0 can fail every API call when shared httpx client is closed via dict mutation |
| NousResearch/hermes-agent#11600 → | feishu | channel-specific | -2 | v0.9.0 Feishu approval card clicks can fall through to unsupported /card path and not resolve approvals |
| NousResearch/hermes-agent#16804 → | provider-integration | runtime | -3 | Hermes 0.9.0 returns empty-body HTTP 400 on OpenRouter while curl with same key/model succeeds |