Hermes 2026.9.24: release tag and internal version are different

Before you start

• Check current account access, plan and task requirements.

Documented change

The release notes describe a patch roll-up, Connectors replacing the MCP tab and changes to profile and gateway lifecycle. They defer the full curated notes to a future 0.22.0 release.

Operational interpretation

A desktop connector being visible does not prove a separately running messaging gateway has loaded it. Check which profile, executable and configuration the actual process uses.

Next checks

1. Save the installed tag, internal version and profile name.
2. Check one connector from a new conversation and one message through the intended gateway.
3. Keep the previous environment until rollback and memory recovery have been checked.

Evidence and limits

Official documentation checked

• Source-backed facts plus BotClaw editorial interpretation. No product account, inference or agent performance test was run.

Sources

• https://github.com/NousResearch/hermes-agent/releases/tag/v2026.9.24
• https://hermes-agent.nousresearch.com/docs/user-guide/messaging/

Continue the decision

• How do I upgrade an agent without losing working state?
• Check that a memory update changes the next session