Cognee
An open-source **persistent agent-memory framework** that builds a hybrid graph-plus-vector memory layer for LLM agents. Cognee ingests unstructured data (documents, conversations, tool outputs), automatically extracts entities and relationships into a knowledge graph (NetworkX, Neo4j, KuzuDB), and dual-indexes the same content into a vector store (LanceDB, Qdrant, Weaviate, Milvus) — giving agents both relational reasoning (graph traversal) and semantic retrieval (similarity search) from a single ingest pipeline.
Definition
An open-source **persistent agent-memory framework** that builds a hybrid graph-plus-vector memory layer for LLM agents. Cognee ingests unstructured data (documents, conversations, tool outputs), automatically extracts entities and relationships into a knowledge graph (NetworkX, Neo4j, KuzuDB), and dual-indexes the same content into a vector store (LanceDB, Qdrant, Weaviate, Milvus) — giving agents both relational reasoning (graph traversal) and semantic retrieval (similarity search) from a single ingest pipeline.
Pure-vector memory loses the ability to answer questions that require *connecting* entities ("which of these documents involve the same legal entity?"). Pure-graph memory loses semantic similarity ("find documents that *feel* like this one even without exact entity overlap"). Most enterprise memory needs are both. Cognee productizes the dual-index pattern so developers don't hand-roll the entity-extraction + graph-construction + vector-embedding pipeline themselves.
Document-heavy agentic workflows (legal research, due diligence, medical record synthesis) where both relational queries and semantic retrieval matter; multi-source data ingestion pipelines where entity resolution across sources is the differentiator; building Animesis-CMA-style constitutional memory layers on top (Cognee provides the substrate; CMA provides the governance).
Recent developments
- Cognee repo + reference notebooks public. Active development; supports a configurable stack of graph engines + vector stores + LLM extraction backends. Per GitHub — cognee project.
- Listed alongside Mem0 / Zep / Letta in the State of Agent Memory 2026. Cognee positioned as the "graph-native" option in the AI-memory-framework comparison matrix. Per Mem0 — State of AI Agent Memory 2026.
- Dual graph-and-vector indexing as the differentiator. Cognee's pitch vs Mem0 (vector-first) and vs Graphiti (graph-first): both indexes built from one ingest, both queried by the agent depending on question shape. Per the Cognee repo.
Connections 7
Outbound 7
scoped_to1