Is Hermes Agent v0.12.0 stable?
70/100Fact score: 70/100 · evidence-based, not a YES/NO verdict
“Backfill refreshed: v0.12.0 picked up late-arriving, version-gated evidence. Not a catastrophe, just another gremlin with a timestamp.”
Stability Score
70Base
80
Evidence
-25
Votes
-0
Survived
+15
Curated
+0
80 base−25 evidence−0 votes+15 (3×5 days survived)=70
Affected components
uicodexwindowsgatewaywhatsappplugin-installprovider-response
Install this version
npm install hermes-agent@0.12.0Score Evidence
| Issue | Area | Type | Penalty | Reason |
|---|---|---|---|---|
| NousResearch/hermes-agent issue 19896 → | ui | runtime | -4 | v0.12.0 Linux CLI crashes at startup with invalid c-S-c key |
| NousResearch/hermes-agent issue 19981 → | codex | provider-integration | -3 | 0.12.0 Codex Cloudflare headers are dropped from wrong SDK attribute |
| NousResearch/hermes-agent issue 20782 → | windows | runtime | -4 | 0.12.0 Windows terminal and write_file tools fail inside agent sessions |
| NousResearch/hermes-agent issue 21336 → | codex | provider-integration | -4 | 0.12.0 Codex rejects memory tool schema with top-level allOf, breaking agent calls |
| NousResearch/hermes-agent issue 21301 → | gateway | runtime | -4 | 0.12.0 /compress and gateway hygiene compression can overwrite original transcript history |
| NousResearch/hermes-agent issue 18646 → | channel-specific | -2 | 0.12.0 send_message ignores WhatsApp group target and routes to home channel | |
| NousResearch/hermes-agent issue 19690 → | plugin-install | tool-specific | -1 | 0.12.0 repo Homebrew formula still points to 0.6.0 placeholder sha256 |
| NousResearch/hermes-agent issue 17248 → | provider-response | runtime | -3 | v0.12.0 can go silent after successful tool calls, then hit an unbound assistant_msg path instead of returning a final response. |