points by mmasu 8 hours ago | 0 comments
I am curious about what people do these days and how do they tackle this problem. At repo level you can alter by with AGENTS.md and perhaps a curated set of additional docs with the project history, but as soon as you get out of it and want to have additional context the solutions available are too many - Hindsight, Graphiti, and many others; or simply roll out your own? I would like something I can spin up with Postgres or with an S3 bucket and that writes me .md files while retaining some sort of relationship among different entities - however it looks like there is no “simple” solution out there yet, with many of the existing implementations being way too elaborate and/or requiring exotic DB solutions. Would be very interesting to hear if someone knows of a bare bones solution I can plug into any agent.
[–] everforward 8 hours ago
[–] Muromec 7 hours ago
Right, I have a simple key-value thingy backed by the filesystem. Not even gzipped. Maybe I will get something elastic shaped or what not at some point, but likely not.
Like what are you store there that text files aren't enough.
[–] skeptic_ai 8 hours ago
Why not a simple git you can push to main directly?
[–] everforward 6 hours ago
The notes and code are usually tied together, and putting them in separate repos just forces you to sync them.
The notes for v1 probably don’t apply to v2.
Maybe different if you’re doing a global memory instead of a per-project memory.
The agent actually did pretty well managing and searching it with grep.
A lot of these memory systems are reaching for the stars and I sort of suspect we’re way past the Pareto point for coding there.