Show HN: Detailed Guide to Agent Memory
https://www.cognee.ai/agent-memory
I wrote a detailed guide to agent memory from the perspective of a builder in the space that has been doing it for 3 years. Hope you like it, and would love to hear feedback.
https://www.cognee.ai/agent-memory
I wrote a detailed guide to agent memory from the perspective of a builder in the space that has been doing it for 3 years. Hope you like it, and would love to hear feedback.
I created one simple place to consolidate all of Karpathy's stuff, like his essays, courses and GitHub projects. You can browse it like a normal wiki, or ask it a question. Every answer cites the underlying source and gets saved as context graph that can build a new page, so asking a question is the same as editing the wiki. I made it very strict about citations. Claims have to point at a real...
https://github.com/topoteretes/cognee-claude-code-binary
Successfully restructured the entire leaked source code of Anthropic's Claude Code using OAI's Codex, rewritten in Binary without copyright issues . You won't get it more performant than this
We just completed our most extensive internal evaluation of cognee to date, using HotPotQA as a baseline. While the results showed strong gains, they also reinforced a growing realization: we need better ways to evaluate how AI memory systems actually perform.
We ran Cognee through 45 evaluation cycles on 24 questions from HotPotQA, using ChatGPT 4o for the analysis. Each part of the evaluation process is affected by the inherent variance in GPT’s output: cognification, answer generation, and answer evaluation. We especially noticed significant variance across different metrics on small runs, which is why we chose the repeated, end-to-end approach.
We compared results using the same questions and setup with:
Mem0 Lightrag Graphiti
While they are standard in QA, EM and F1 scores reward surface-level overlap and miss the core value proposition of AI memory systems. For example, a syntactically perfect answer can be factually wrong, and a fuzzy-but-correct response can be penalized for missing the reference phrasing.
LLMs are inconsistent, that is another issue.
Even HotPotQA assumes all relevant information sits neatly in two paragraphs. That’s not how memory works. Real-world AI memory systems need to link information across documents, conversations, and knowledge domains that traditional QA benchmarks just can’t capture.
Consider the difference:
Traditional QA:
“What year was the company that acquired X founded?”
Memory Challenge:
“How do the concerns raised in last month’s security review relate to the authentication changes discussed in the architecture meeting three weeks ago?”
Only one of these tests long-term knowledge, reasoning across sources, and organizational memory—care to guess which one?
We are working on a new dataset and benchmarks to measure memory, and would love feedback!
At cognee we are working on building graph/vector based memory on top of vector and graph stores. Our pipelines had 116k runs last month and we are projecting north of a million in a few months. We need help on the infra side.
Check our OSS tool here: https://github.com/topoteretes/cognee
Open Roles: Platform Engineer - https://apply.workable.com/topoteretes-ug-haftungsbeschrankt...
We have temporal resolution mechanisms we are building, and framework is generalizable enough to build any custom logic. We have a few ideas and some things will be posted there soon.
cognee has notion of nodesets which work similar to tags: https://docs.cognee.ai/core-concepts/node-sets
And also we have graphs per user now available. So, user permisions + graph filtering
https://github.com/topoteretes/cognee
Hey HN! We're Vasilije, Laszlo and Lazar, the authors of a new paper and part of https://www.cognee.ai. cognee let’s you build memory layers for AI applications and agents, allowing them to personalize results, connect various data sources, and add custom rules. This enables AI apps to deliver increasingly accurate responses, we reached almost 90% on standard industry benchmarks as you can see...
https://github.com/topoteretes/cognee
Hey there HN! We’re Vasilije, Boris, and Laszlo, and we’re excited to introduce cognee, an open-source Python library that approaches building evolving semantic memory using knowledge graphs + data pipelinesBefore we built cognee, Vasilije(B Economics and Clinical Psychology) worked at a few unicorns (Omio, Zalando, Taxfix), while Boris managed large-scale applications in production at Pera and...
https://github.com/topoteretes/cognee
Hi, We are building an open-source framework for loading and structuring LLM context to create accurate and explainable LLM answers using knowledge graphs and vector stores.We built the tool with four main concepts in mind:1. Loader -> uses dlt in the backend to load and structure the data2. Cognify step -> creates a graph with summaries, labels and factoids that are interconnected across...
Hi! We created UI/UX flow on top of OpenAI API + Langchain and gave connected agents access to tools. The outcome is a mobile app that can decompose your thoughts, remember them, help with ideas and automate actions via Zapier integration. Would love to hear the thoughts and advice on how to make it better! Repos: https://github.com/topoteretes/