Markdown docs beat a vector DB for one agent’s knowledge base, at least at small scale
Old_Visual_6596 · reddit · 2026-07-24
The author replaced a full vector-database retrieval stack with a folder of cross-linked Markdown files and found it worked better for a few thousand pages of docs.
Why it was easier
- Markdown preserves whole concepts instead of splitting them across chunks.
- Retrieval bugs are inspectable: open the file, see the issue, fix the source.
- The knowledge base lives in git, so changes are diffable, versioned, and reversible.
- There is no separate index drifting out of sync with the source of truth.
Where it breaks down
- This is a scale-dependent solution; the author says a few thousand documents are fine, but millions would still need real vector infrastructure.
- It depends on current models being good at navigating structured Markdown with plain file tools and grep.
The post asks where other people hit the crossover point and whether anyone is using a hybrid setup where files remain the source of truth and the index is only derived.
More from coding & agent
- Could stdio MCP servers start only on tool calls and exit immediately after? — gelembjuk · 2026-07-24
- Infinitty app adds task tracking and MCP UI rendering for agents — jasonkneen · 2026-07-24
- GitHub Copilot Still Feels Useless on Large, Messy Codebases — SkeleMortal · 2026-07-24
- Seven system design mistakes that keep AI agents from working reliably — goyalshaliniuk · 2026-07-24
- Built a local Qwen assistant for internal docs, now asking if companies would buy it — teriyaki_tofu1 · 2026-07-24
- Google codelab shows how to use parallel worktrees and resolve conflicts in Antigravity 2.0 — ksoonson · 2026-07-24