Agent memory as a file format
- ID
- 20379
- Status
- summarized
- Published
- 31 Aug 2026, 7:17 PM
- Fetched
- 02 Sep 2026, 7:24 AM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://calpaterson.com/memoryfields.html
- Source URL
- https://hnrss.org/best
Summary
- Score
- 7.5
- Created
- 02 Sep 2026, 7:25 AM
- Tags
- Audience
- developersvibe_codersai-agent-usersai-ml-learners
What happened
Cal Paterson argues that agent memory should be a portable file format, not a multi-stage pipeline. He proposes 'memoryfield': a zip containing markdown pages with optional YAML frontmatter and an optional SQLite vector index (using nomic-embed-text-v1.5), critiquing three common approaches—vendor-locked harness memory, over-engineered systems needing pgvector + Neo4j + a separate LLM, and graph-based 'distilled facts' that strip context.
Why it matters
If you're building AI agents, this gives you a concrete, dead-simple alternative to complex memory stacks: ship markdown files in a zip with an optional SQLite vector index, and let the model read prose in context rather than querying a graph database or paying a platform vendor for memory extraction. Evaluate whether your current memory pipeline can be replaced with a folder of markdown files before investing further in pgvector or Neo4j setups.
Discussion angle
Compare the tradeoffs of memoryfield's markdown-in-a-zip approach against what people in the group are actually using today—does the simplicity hold up when you have thousands of memories, or do you still need a vector store at scale?