Is Hermes Agent v0.6.0 stable?
72/100Fact score: 72/100 · evidence-based, not a YES/NO verdict
“Early API/gateway rough edges: Telegram model control, fallback config, profile isolation, and one-time approvals all have explicit 0.6.0 repros.”
Stability Score
72Base
80
Evidence
-20
Votes
-0
Survived
+12
Curated
+0
80 base−20 evidence−0 votes+12 (3×4 days survived)=72
Affected components
telegramgatewayprovider-integrationmcpapproval-boundaryuiplugin-systemsessions-management
Install this version
npm install hermes-agent@0.6.0Score Evidence
| Issue | Area | Type | Penalty | Reason |
|---|---|---|---|---|
| NousResearch/hermes-agent#4039 → | telegram | channel-specific | -2 | 0.6.0 Telegram /model command is exposed but cannot reliably switch models |
| NousResearch/hermes-agent#4091 → | provider-integration | runtime | -3 | v0.60/0.6.0 fallback_model documented config shape crashes or fails with OpenRouter 401 |
| NousResearch/hermes-agent#4280 → | mcp | runtime | -2 | 0.6.0 MCP servers added in one profile leak into another profile |
| NousResearch/hermes-agent#4306 → | plugin-system | runtime | -4 | 0.6.0 --clone-all profile creation can recursively copy profiles until disk/path exhaustion |
| NousResearch/hermes-agent#4331 → | ui | runtime | -3 | v0.6.0 CLI launch can crash with UnboundLocalError ctx_len before use |
| NousResearch/hermes-agent#4507 → | sessions-management | runtime | -2 | 0.6.0 API server chat completions lack stable session continuity by default |
| NousResearch/hermes-agent#4697 → | approval-boundary | kernel | -4 | 0.6.0 gateway plain /approve grants session-wide approval instead of one-time approval |