Whether Hermes Agent v0.8.0 is worth updating right away depends on whether you are using gateway, MCP, long task, Slack/Telegram approval, or multi-model switching. v0.8.0, released on April 8, 2026, is not simply a bug fix, it makes up for many "stuck hands in real use"; But if you only chat occasionally locally, you can also back up first and then update at the right time.
The 6 most noteworthy changes
- Long task notifications: Background processes can be notified of completion with
notify_on_completewithout constant polling. - /model mid-switch: CLI, Telegram, Discord, Slack, and other portals can cut models in the middle of a session.
- Nous Portal Free Assisted Model: MiMo v2 Pro can be used for assisted tasks such as compression, visual, summarization, and more.
- MCP OAuth 2.1: More standardized when connecting MCP services that require login, and also adds OSV malicious packet scanning.
- Log centralization:
~/.hermes/logs/andhermes logsare better for troubleshooting. - Slack/Telegram Approval Button: Dangerous commands are no longer hand-
/approve.
Who should update right away
If you use Hermes Agent as a long-term online assistant, code executor, or multi-platform agent, it is recommended to update. Especially for users who run tests, deploy, crawl data, connect to MCP, and connect to Slack/Telegram, this version can reduce a lot of "tasks running and running without knowing the results".
What to do before updating
Back up your ~/.hermes/ first, then look at the hermes version and release notes. Run the hermes config check after the update, and then use a short task to verify that the provider, gateway, MCP, and logs are normal. Don't just lose the production task as soon as you update, let it run a round of small tasks first.
Official open source address: https://github.com/NousResearch/hermes-agent; Official document entry: https://hermes-agent.nousresearch.com/.
