Hermes: a practical decision dossier

Before you start

• Check current account access, plan and task requirements.

When to consider it

Consider it for terminal-oriented tasks and a controlled memory experiment with a compatible provider.

Important boundary

A written memory file is storage evidence. The meaningful check is whether a new session changes its next action after a correction.

Questions before committing

1. Which executable and profile does the real gateway use?
2. What state besides MEMORY.md must a full recovery preserve?

A useful acceptance task

Give the candidate one read-only task with fixed input, a clear expected output and an explicit stop condition. Save the input, returned evidence, elapsed time and any human intervention. Repeat after a new session; assess observed behavior, not a polished demo.

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://hermes-agent.nousresearch.com/docs/getting-started/quickstart
• https://hermes-agent.nousresearch.com/docs/user-guide/features/memory
• https://hermes-agent.nousresearch.com/docs/user-guide/messaging/
• https://hermes-agent.nousresearch.com/docs/user-guide/security

Continue the decision

• Hermes 2026.9.24: release tag and internal version are different
• How do I know an agent really remembered a correction?
• Check that a memory update changes the next session