The missing knowledge layer for open-source agent stacks is a persistent markdown wiki
Posted by knlgeth@reddit | LocalLLaMA | View on Reddit | 5 comments
I connected llm-wiki-compiler as the knowledge layer beneath my agent stack and it finally stopped repeating the same research every session.
Pattern: ingest docs → compile into interlinked markdown wiki → agent queries via MCP. Tags carry over. Map of content auto-generates.
When the agent answers something new, query --save pushes it back into the wiki as a page. Next query is smarter because the artifact is richer.
That's the difference between a stateless file upload and a knowledge base that actually accumulates.
If you're building with Hermes / Claude Code / Codex and hitting the "it doesn't know my domain" problem, a persistent markdown wiki underneath changes everything.
R_Duncan@reddit
I think I found a bug:
>llmwiki ingest https://en.wikipedia.org/wiki/Lunar_Lake
>llmwiki ingest https://en.wikipedia.org/wiki/List_of_Intel_Core_processors
>llmwiki compile
..... logs putting both pages in the wiki.....
✓ 2 compiled, 0 skipped, 0 deleted
>llmwiki query "what is Lunar Lake?"
Selecting relevant pages
────────────────────────────
i Reasoning: Failed to parse page selection response
* Selected 0 page(s):
Generating answer
─────────────────────
! No matching pages found. Try refining your question.
jwpbe@reddit
the missing peepee poopoo is my markdown repository please send money to my github sponsor
Not_your_guy_buddy42@reddit
kinda overdid mine, just glad quartz can handle 10k pages, but living wikis are rad
Limp_Statistician529@reddit
This is really the future now tbh and how I wish I was still a college because this will really help me a lot when it comes to basic research and sourcing
knlgeth@reddit (OP)
Repo link: https://github.com/atomicmemory/llm-wiki-compiler