Hermes
Hermes uses the UnifiedMemory plugin for pre-turn recall and post-turn writeback. It is especially important to keep Hermes writeback clean because chat crumbs and long assistant answer dumps can otherwise flood review.
Scope and capabilities
| Setting | Value |
|---|---|
| Source app | hermes |
| Default container | jeethendra |
| Default scope | own |
| Primary mode | Plugin-based recall and writeback |
Install
From the UnifiedMemory repo checkout:
mkdir -p ~/.hermes/plugins/memory
ln -sfn "$PWD/integrations/hermes-unifiedmemory" ~/.hermes/plugins/memory/unifiedmemory
hermes config set memory.provider unifiedmemory
hermes memory setup
Set the scoped key in the environment expected by the plugin or through the Connections-generated setup bundle.
Verify
Ask Hermes to run its memory setup verification. The check should prove:
- the scoped key is active;
- recall works for
jeethendra; - writeback can store a disposable fact;
- obvious residue is rejected or quarantined;
- Courtroom read works for returned memory IDs.
Writeback hygiene
Hermes should retain:
- decisions made during a session;
- completed tool outcomes;
- durable owner preferences;
- reproducible fixes.
Hermes should not retain:
hey,thanks, or emoji-only messages;- long assistant explanations as a single memory;
- generic web summaries with no owner/project tie;
- proof/test/diag rows as assistant-visible memory.