Comment by rcarmo
4 hours ago
Nice to see more OKF-based approaches. My entry in this field is https://rcarmo.github.io/projects/memento/, which I’ve been running for a few months now.
4 hours ago
Nice to see more OKF-based approaches. My entry in this field is https://rcarmo.github.io/projects/memento/, which I’ve been running for a few months now.
Since you built something on OKF, how would you contrast it with knowledge graph implementations? How do you manage the ontology of what to keep knowledge about? Any cases where traversal would have helped?
I’m not using pure OKF. Mine has links (both explicit and semantic, based on embeddings), and I tap into both Needle for routing searches and a Qwen/Gemma or gpt-mini for doing the actual traversals on behalf of the client.
Please excuse my noob-ish, naïve question, but to what extent is the business of getting the LLM to actually consult memory a model-dependent thing? Do you have to introduce the tool and guide models with different language for different model families?
Looking at your tool descriptions (as wit the ones on the original post) I wonder if this something perhaps only current frontier models will do, but the systems themselves seem like they'd be even more useful for open weights models with shorter working contexts.
All SOTA models seem to work fine (including Sonnet and Gemini), as does Kimi and DeepSeek. But this is not for short-term memory.
I have seen the value of recording past sessions but I am more skeptical of the value in recording facts, which may soon become stale, about a constantly changing code base. Got benchmarks?
This is not for code bases, that’s pointless. This is for durable facts like “this is the prod server” or “this is the skill for managing GitHub Actions cleanup policies”.
In short, this is for my agents to have a shared skill library, a shared fact library and durable information such as which projects run where.
The rest should be in your repo.
Well, do you see the value of writing notes for yourself occasionally, even though they might soon become stale in your constantly changing environment? Yes, right?
Same principle. It's a good idea to have a schedule to clean them up periodically - an idea you can also put into a note.
I'll write one off notes for myself, but I am not going to do that in the code base unless it is really high value; it does not scale. The only place I write myself now is AGENTS.md
1 reply →