@pauliusztin_: I researched how Cognee, Graphiti and agent-memory (by Neo4j) built their agent-memory solutions and compiled the whole…

X AI KOLs Timeline News

Summary

A summary of research comparing agent-memory solutions from Cognee, Graphiti, and Neo4j, which all use knowledge graphs and vector search with LLM-based data extraction.

I researched how Cognee, Graphiti and agent-memory (by Neo4j) built their agent-memory solutions and compiled the whole architecture into a 2800-word article. Their solution has huge overlaps: - It's based on knowledge graphs (KG) + vector search - the data model and ontology sit at the core - data extraction is done via LLMs (+ some other tricks to reduce costs)
Original Article
View Cached Full Text

Cached at: 07/15/26, 10:00 PM

I researched how Cognee, Graphiti and agent-memory (by Neo4j) built their agent-memory solutions and compiled the whole architecture into a 2800-word article.

Their solution has huge overlaps:

  • It’s based on knowledge graphs (KG) + vector search

  • the data model and ontology sit at the core - data extraction is done via LLMs (+ some other tricks to reduce costs)

Similar Articles

rohitg00/agentmemory

GitHub Trending (daily)

agentmemory is an open-source persistent memory layer for AI coding agents (Claude Code, Cursor, Gemini CLI, Codex CLI, etc.) that uses knowledge graphs, confidence scoring, and hybrid search to give agents long-term memory across sessions via MCP, hooks, or REST API. Built on the iii engine, it requires no external databases and exposes 51 MCP tools.

@yibie: Recommend this article. The teams from SJTU and Tsinghua systematically evaluated 12 agent memory systems. It's not one of those "our model is better" papers but rather breaks down how to choose memory systems from a data management perspective—when to use RAG, when to use vector databases, when to use knowledge graphs. Long-term memory for agents...

X AI KOLs Timeline

This paper from SJTU and Tsinghua systematically evaluates 12 agent memory systems from a data management perspective, decomposing memory into four modules and providing guidelines on when to use RAG, vector databases, or knowledge graphs for long-term agent memory.