nashsu/llm_wiki
nashsu/llm_wiki — LLM Wiki is a cross-platform desktop application that turns your documents into an organized, interlinked knowledge base
What is the idea?
A desktop app that reads a folder of your documents and builds an interlinked wiki out of them by itself, instead of the usual retrieve-then-answer trick: it writes entries and cross-links them, so you browse and ask rather than search. Runs on your machine, points at whatever model you configure — cloud or a local Ollama.
Who would use it, and what do they get?
Non-developer user: a professional with a private document pile. Finished thing: a browsable, askable wiki of their own files that never leaves the laptop.
Why would anyone bother?
Someone with a hard drive of PDFs they can no longer find anything in — a graduate student, a solo lawyer, a person who inherited a company's paperwork. What they walk away with is a wiki they can browse, not a chatbot they have to interrogate.
What is missing today?
It hits a real pain but the first five minutes are geek-only. The person who needs this is a lawyer, a graduate student, a researcher with a hard drive full of PDFs — and the tracker is full of them failing at model configuration, folder selection and LAN Ollama endpoints before they ever see a wiki page.
What makes this one different?
Sell the first five minutes, not the engine. A signed installer with a working model bundled or one paid key on the vendor's account, an opinionated 'point at this folder, get a wiki in ten minutes' path, and a single named profession as the launch wedge (start with case-file review, where the documents are private by obligation and cloud AI is disallowed). Cold start (Chinese): the llm_wiki issue tracker and the self-organised WeChat group its users opened in issue #158 — they are already assembling without the maintainer; Cold start (English): r/ObsidianMD and r/LocalLLaMA, search 'ask my own documents offline'.
What is the sharpest thing about it?
Retrieval-augmented search answers one question at a time and leaves the corpus shapeless. Writing the whole wiki up front — entries, cross-links, a map you can wander — only became affordable when long-context reading got cheap enough to pass over every document twice.
What could kill it?
Obsidian, Notion and every note app are shipping the same feature this year, and they already hold the documents. 219 open issues against 33 contributors is a maintenance line going the wrong way, and 'turn my folder into a wiki' is a demo that dazzles once and then has to survive the second week.
Who pays, and for what?
Someone whose documents cannot legally go to a cloud model — a solo lawyer, an accountant, a clinician. One-off desktop licence, priced against an afternoon of hunting through folders.
What is the main risk?
The moat is the setup experience, and setup experiences are exactly what a well-funded incumbent copies in one release.
What did real people actually say?
Verbatim from the public sources linked above, not paraphrased: “接 openai、kimi、minimax 的模型，全部都 analysis failed。实在是没招了，每个 api 都不行” — github-issue “By clicking on the create button, nonthing happens. Please advise.” — github-issue “开发者好像没有建立一个微信群，试建个微信群欢迎感兴趣者加入交流” — github-issue
How much work is it?
about two months of work
Where does the evidence come from?
https://github.com/nashsu/llm_wiki