I think everyone's ended up building one of these for themselves. I did too[0]. In the end it's quite easy these days:
* I use the bge-en-base CPU embedding model
* I put storage behind a simple endpoint that has read,write,update,search semantics
* The endpoint just stores markdown in an S3 like structure (bucket-key-value; tree structure is inferred) and vector indexes
* The actual persistence is just SQLite
Most modern models are pretty good at handling this. Our home agents (voice and text) use this to store information and I also have skills for claude code and codex to do that as well. Overall, works quite well.
I still use MEMORY.md for the home agents to keep short-term memory, and use the KB for long-term memory. You do need a self-reflection/consolidation/dream step in order to periodically consolidate and groom the KB but that's also just another job.
The whole setup is pretty trivial and what anyone would come up with from scratch and it's surprising that it works but it does. I'm a pretty good documenter so it helps. In some future perhaps a vision model could see all the things I'm doing and remember, but for now I just tell it and it's pretty good about everything I want.
I wasn't but now, doing a lot of work inside a harness that is logging everything and can easily create docs from that, I'm finally persisting a lot of knowledge.
What did you find wasn't working well? Perhaps I have insufficient content for it to start failing. Works quite well in Claude Code / Codex / Custom Harness with DSV4F.
Comments
I think everyone's ended up building one of these for themselves. I did too[0]. In the end it's quite easy these days:
* I use the bge-en-base CPU embedding model
* I put storage behind a simple endpoint that has read,write,update,search semantics
* The endpoint just stores markdown in an S3 like structure (bucket-key-value; tree structure is inferred) and vector indexes
* The actual persistence is just SQLite
Most modern models are pretty good at handling this. Our home agents (voice and text) use this to store information and I also have skills for claude code and codex to do that as well. Overall, works quite well.
I still use MEMORY.md for the home agents to keep short-term memory, and use the KB for long-term memory. You do need a self-reflection/consolidation/dream step in order to periodically consolidate and groom the KB but that's also just another job.
The whole setup is pretty trivial and what anyone would come up with from scratch and it's surprising that it works but it does. I'm a pretty good documenter so it helps. In some future perhaps a vision model could see all the things I'm doing and remember, but for now I just tell it and it's pretty good about everything I want.
0: https://wiki.roshangeorge.dev/w/Blog/2026-07-01/The_Everythi...
I wasn't but now, doing a lot of work inside a harness that is logging everything and can easily create docs from that, I'm finally persisting a lot of knowledge.
It's not easy, that's why they all suck.
What did you find wasn't working well? Perhaps I have insufficient content for it to start failing. Works quite well in Claude Code / Codex / Custom Harness with DSV4F.