Open SourceImportance: Medium

Why one builder ditched heavy knowledge-graph memory for markdown + LLM wikis

r/AI_AgentsJul 15, 2026 · 1d ago

The author three major tools — Cognee, Graphiti, and Neo4j's offering — and found they all converge on the same heavy knowledge-graph design: a defined ontology, an LLM extraction pipeline, and logic. For personal or small-scale use, this setup adds too much friction, creates silos between systems, and locks data into a specific service without delivering proportional value.

As a result, continues to live in plain markdown files across Obsidian, Readwise, and Google Drive, combined with per-project LLM wikis — no dedicated required, while still approximating the knowledge-graph experience. That said, the value of the knowledge-graph itself is not dismissed: the same structure was rebuilt as a data-mining tool using MongoDB, VoyageAI, and , but scoped tightly to one specific problem and ontology domain to avoid the noise that comes with a general-purpose .

Radar's take

For anyone optimizing agent token and cost, the key claim is that full knowledge-graph memory stacks — ontology plus extraction pipeline plus — are overkill at personal or small scale, since each of those stages typically means extra LLM calls and overhead every time something is stored or retrieved. Swapping that for plain markdown files and an LLM wiki removes that overhead, at the likely cost of weaker retrieval accuracy and relationship reasoning — so the real trade-off is figuring out at what scale a graph actually earns its cost.

What's notable is that the same author reintroduced the knowledge-graph approach for a narrowly scoped domain, suggesting the deciding factor isn't graph-vs-no-graph but how tightly the problem is scoped. That's a useful heuristic if you're designing memory for your own agent.

Key points

and compared three tools: Cognee, Graphiti, and Neo4j's
All three converge on a heavy knowledge-graph design with ontology, LLM extraction, and
Judged overkill for personal/small-scale use due to setup friction, data lock-in, and low value relative to cost
kept in markdown files (Obsidian, Readwise, Google Drive) plus per-project LLM wikis, with no dedicated
Rebuilt the same graph with MongoDB, VoyageAI, and , but scoped narrowly to cut knowledge-graph noise

Read original ↗

Why one builder ditched heavy knowledge-graph memory for markdown + LLM wikis

Key points

Related