What memory you're using with your Openclaw?
Summary
A developer discusses building a custom memory plugin for the Hermes agent using Engram, which reconciles new information with existing memories to avoid staleness and duplication, and asks the OpenClaw community about their memory usage.
Similar Articles
An open source natural temporal memory for claude code, hermes and openclaw agent
agentmemory is an open-source library that provides natural temporal memory for AI agents like Claude Code, Hermes, and OpenClaw. It uses a three-tier architecture with hybrid retrieval (BM25, vector, knowledge graph) and Ebbinghaus decay, achieving ~92% fewer tokens and 200x more tool calls before context limits.
Question: how should Hermes agents handle persistent memory across sessions?
A community discussion about how Hermes agents should handle persistent memory across sessions, exploring an external memory layer (8mem) and comparing memory-aware vs generic outputs.
@bayendor: Just finished wiring a 3-layer memory stack into Hermes Agent. Layer 1: Honcho Session + peer memory on PostgreSQL. Han…
Describes implementing a three-layer memory stack for Hermes Agent, combining session memory on PostgreSQL, working memory with pattern redaction, and a long-term knowledge graph using PGLite.
@KSimback: https://x.com/KSimback/status/2058262328496554021
A comprehensive guide to memory systems for Hermes Agent, explaining the three-layer memory architecture and comparing various memory tools and providers.
Yesterday I saw a new research paper about δ-mem and integrated with openclaw
A new research paper on δ-mem improves agent response quality by 7-32% when integrated with openclaw. The project is currently usable only with mlx and Qwen3:4b, but adapters for other models are expected.