I reverse-engineered the three biggest agent-memory tools. Then I went back to markdown files and LLM wikis over Obsidian.
Summary
The author reverse-engineered three major agent-memory tools and concluded that markdown files and LLM wikis in Obsidian are preferable.
Similar Articles
@mylifcc: Recently while working on Agent memory and personal knowledge systems, I discovered this project obsidian-wiki, so fitting! It brings Andrej Karpathy's LLM Wiki pattern to Obsidian: enabling AI Agents to autonomously inges…
This tweet introduces the obsidian-wiki project, which implements Andrej Karpathy's LLM Wiki pattern on Obsidian, allowing AI Agents to autonomously ingest multi-source knowledge and organize it into a wikilink-interconnected markdown knowledge base. It supports Delta incremental updates and source attribution (provenance), and has built-in features like query, audit, graph export, etc. Currently at 2k stars.
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.
I thought markdown memory would be enough for agents. It turned into prompt debt.
The author reflects on the limitations of using flat markdown files for long-term agent memory, which leads to prompt debt as the memory grows, and advocates for graph-based memory representations that retrieve relevant context dynamically.
@kepochnik: https://x.com/kepochnik/status/2071915153957011826
Hermes Agent v0.14 integrates with Obsidian vault to provide persistent, inspectable memory for AI agents, using plain markdown files instead of vector databases.
@mem0ai: https://x.com/mem0ai/status/2054580022049198513
This article explains how memory works in Codex CLI, OpenAI's open-source coding agent. It describes the memory architecture based on markdown files, the write path with phased extraction and consolidation, and the read path using keyword search, all designed for predictability and low retrieval cost.