Cognee’s creator claims its released SDK and Claude Code plugin provide persistent codebase memory through knowledge graphs and embeddings with 86% fewer tokens on a reported query set, potentially reducing repeated context loading for coding agents.
state: seedheat: lowuncertainty: highconvergesscott: mediumagent-memory codebase-rag knowledge-graphsCogneeShort-Honeydew-7000
What is this?
Cognee is an open-source agent-memory platform; an AI Engineer profile identifies its founder and CEO as Vasilije Markovic, who started it with a Berlin team in 2024. Its GitHub documentation describes a Claude Code plugin that captures prompts, tool traces, and responses, retrieves context on each prompt, preserves memory across compaction, and syncs sessions into a permanent knowledge graph; its Codex documentation says the two plugins can share a memory dataset. The supplied snippets establish documented persistent-memory integrations, but do not substantiate the case’s 86% token reduction, its query-set methodology, or the claimed codebase-ingestion and embeddings workflow. They also do not establish that Reddit account Short-Honeydew-7000 is Markovic; results about codebase-memory-mcp concern a different project and cannot validate Cognee’s performance.
Why it matters to Scott
Cognee’s documented prompt-time retrieval and memory persistence across compaction converge with Scott’s Context Engineering position and offer a concrete integration to compare against his Ask agent’s lossy compaction and search project’s Claude-history retrieval. That makes it a practical evaluation candidate, not proof of his distinctive wiki-graph architecture: the supplied material does not substantiate the 86% token saving or retrieval quality, and the radar hits track related alternatives rather than this Cognee development.
ip:framework.context-engineeringdev:project.askdev:project.searchdev:concept.agent-authored-context-compactionradar:graphify-repository-map-contextradar:memhub-shared-coding-agent-memoryradar:memory-bench-layer-baseline-validity
queries asked of Scott's wikis
- coding agent persistent memory versus repeated codebase context loading
- knowledge graph and embedding retrieval for codebase understanding
- agent harness lifecycle hooks memory capture compaction
- cross-agent shared memory dataset scoping
- agent memory token savings evaluation retrieval quality
Measured heat
now 0 pts/hpeak 0 pts/hcomments 0/hpeers p0momentum: steady2 platformsage 820h
points/hour across evidence · reading as of 2026-10-12 02:59:37.977291+11:00 · deterministic, not a model opinion
How the heat travelled
pace: p40 vs 519 stories at the 720h mark (now 820h old) — ahead of agentgate-signed-agent-receipts (1.3x), behind artificial-analysis-optima (0.8x)
Evidence (2) — ⭐ canonical anchor
Interpretation history
2026-09-09T13:32:55Z
No substantive evidence has arrived to turn Cognee from a documented memory integration into a demonstrated efficiency improvement. It remains a bounded evaluation candidate for Scott; the 86% token-saving claim still needs reproducible methodology and retrieval-quality controls, and the repository echo adds no independent corroboration.
2026-09-07T12:34:09Z
Cognee remains a concrete persistent-memory integration to evaluate, not demonstrated evidence of token-efficient codebase retrieval. This look adds no substantive evidence: the linked repository echo is not independent corroboration, and the claimed savings still lack methodology and quality controls.
2026-09-07T12:27:28Z
grounded: converges/medium — Cognee’s documented prompt-time retrieval and memory persistence across compaction converge with Scott’s Context Engineering position and offer a concrete integ
2026-09-07T12:24:39Z
case created — The usable memory artifact and specific token-efficiency claim warrant a bounded case, while adoption and benchmark figures remain creator-reported.
Decision trace
- 09-20 06:24review_dormantscheduled targets exhausted or 28 quiet days
- 09-20 06:24drop_targetsquiet through full ladder or over cap 8
- 09-09 23:32repriceNo substantive evidence has arrived to turn Cognee from a documented memory integration into a demonstrated efficiency improvement. It remains a bounded evaluation candidate for Scott; the 86% token-s
- 09-09 23:32alert_silentThe reobservation supplies no new comment content, implementation result, or release/access change. The existing integration can wait for a briefing; there is no consequential new delta requiring Scot
- 09-09 23:32alert_routeThe reobservation supplies no new comment content, implementation result, or release/access change. The existing integration can wait for a briefing; there is no consequential new delta requiring Scot
- 09-07 22:34repriceCognee remains a concrete persistent-memory integration to evaluate, not demonstrated evidence of token-efficient codebase retrieval. This look adds no substantive evidence: the linked repository echo
- 09-07 22:34alert_silentNo new release, access change, implementation result, or benchmark evidence has arrived. The existing integration can wait for a briefing; the engagement change does not alter the prior alert judgment
- 09-07 22:34alert_routeNo new release, access change, implementation result, or benchmark evidence has arrived. The existing integration can wait for a briefing; the engagement change does not alter the prior alert judgment
- 09-07 22:32alert_silentThe creator links an available SDK and Claude Code plugin for persistent graph-and-embedding memory, making Cognee a concrete evaluation candidate for Scott’s context-engineering work. However, this r
- 09-07 22:32surface_candidateThe creator links an available SDK and Claude Code plugin for persistent graph-and-embedding memory, making Cognee a concrete evaluation candidate for Scott’s context-engineering work. However, this r
- 09-07 22:32alert_routeThe creator links an available SDK and Claude Code plugin for persistent graph-and-embedding memory, making Cognee a concrete evaluation candidate for Scott’s context-engineering work. However, this r
- 09-07 22:27groundCognee’s documented prompt-time retrieval and memory persistence across compaction converge with Scott’s Context Engineering position and offer a concrete integration to compare against his Ask agent’
- 09-07 22:24createThe usable memory artifact and specific token-efficiency claim warrant a bounded case, while adoption and benchmark figures remain creator-reported.