Looking for feedback: Memory system that both AI agents and humans can use
Summary
The author introduces Noosphere, an open-source memory and wiki layer for AI agents and humans, seeking feedback on its structured Postgres-backed memory, Redis-cached recall, and human-editable wiki pages.
Similar Articles
How are people handling long-term memory + replay/debugging for AI agents?
A developer discusses limitations in current AI agent memory systems and proposes a new memory layer tool with episode storage and replay debugging, seeking community validation.
I built an open-source persistent memory layer for AI coding agents
An open-source persistent memory layer for AI coding agents that stores and retrieves project decisions and context using Postgres and pgvector, aiming to reduce context window size and improve agent consistency.
rohitg00/agentmemory
agentmemory is an open-source persistent memory layer for AI coding agents (Claude Code, Cursor, Gemini CLI, Codex CLI, etc.) that uses knowledge graphs, confidence scoring, and hybrid search to give agents long-term memory across sessions via MCP, hooks, or REST API. Built on the iii engine, it requires no external databases and exposes 51 MCP tools.
I asked if a local-first Markdown memory server existed. You gave me ~20 suggestions. Here's what I found after going through all of them.
A comprehensive review of local-first AI agent memory systems, comparing options like mem0, Hindsight, and mnem, ultimately recommending Engram for its unique combination of local storage and human-readable Markdown files.
What's the "best" multi-agent memory system for coding agents? I raised 9 issues on rohitg00/agentmemory and have given up on it.
A developer discusses alternatives to the agentmemory library for multi-agent memory systems in coding agents, comparing Mem0 and ByteRover, and asks for confirmations on Opencode and Pi.