I thought markdown memory would be enough for agents. It turned into prompt debt.

Reddit r/openclaw News

Summary

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.

I thought markdown memory would be enough for agents for a while. back in my OpenClaw setup, the agent memory was basically markdown files. readable, editable, easy to back up, no weird vendor lock-in. honestly it felt like the correct boring answer. then it grew to 80+ md files and somewhere past 5 million characters. and technically, yeah, it was all still "there." but every run started to feel like: "please scan this giant pile of notes and somehow guess which parts still matter." that was the part that kept biting me. storage was solved. memory was not. the annoying thing about flat text memory is that it works beautifully for one scale, then quietly turns into prompt debt. project facts, old bugs, decisions, people, preferences, half-dead plans... they all sit there as chunks waiting to be reread like they have equal weight. the thing that finally clicked for me, weirdly enough in the shower lol, was that I didn't want a better notebook. I wanted the agent to render the relevant part of its memory for the current task. so I ended up moving toward graph memory: each memory as a node, relationships stored as edges, and retrieval as "what part of this map should light up right now?" instead of "dump the top 10 similar notes into context." not saying markdown is bad. I still like it as an archive/export format. I just don't think long-term agent memory can stay purely text-shaped once it gets big enough.
Original Article

Similar Articles

@mem0ai: https://x.com/mem0ai/status/2054580022049198513

X AI KOLs Timeline

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.

@tricalt: https://x.com/tricalt/status/2057173322924806651

X AI KOLs Timeline

A founder discusses the scaling challenges of using markdown files for AI agent memory in production, highlighting common pitfalls with permissions, multi-agent interaction, and temporal queries, and suggests that teams often end up patching around these issues without realizing they are rebuilding a more complex system.