At a glance
The philosophical difference
The Hermes Agent architecture (developed by Nous Research) organizes agent memory into a pragmatic four-layer stack:- Prompt Memory: a static snapshot of
MEMORY.mdandUSER.mdinjected into system prompts. - Session Archive: historical interaction logs indexed via SQLite FTS5
(
state.db) for episodic keyword recall. - Procedural Memory: extracted task procedures saved as executable markdown skills.
- Pluggable Memory Providers: hooks to external memory stores (e.g. Mem0, Supermemory).
When Worlds fits
- You need deterministic graph querying (SPARQL) to traverse relationships across complex domain facts.
- You require fact-level chronological provenance and auditability across all asserted data.
- You want an open, standards-based RDF memory layer shared across multiple agent runtimes (Claude Code, Letta, Hermes).
- Your application demands strict compliance, safety, and deterministic filtering where keyword or similarity search alone is insufficient.
When Worlds does not fit
- You want an all-in-one local agent CLI framework that manages prompt context
files (
MEMORY.md) and session history out of the box. - You prefer simple FTS5 text search over episodic agent conversations without establishing a formal knowledge graph vocabulary.
Coexistence
Hermes agents support pluggable memory provider plugins. Hermes can use its internalMEMORY.md for local prompt conventions while connecting Worlds as an
external memory provider tool to query authoritative RDF facts via SPARQL during
complex multi-step reasoning.