LIFEHUBBER
Theme

AI Resources

LLM Wiki

LLM Wiki is a cross-platform desktop app that turns documents into an organized, interlinked personal knowledge base maintained with LLM help.

The official repository presents LLM Wiki as an app that ingests documents, builds wiki pages with source traceability, keeps a persistent knowledge graph current, supports optional vector search, and exposes a local API plus a companion agent skill for tools such as Codex or Claude Code. Use this as a first read, not a recommendation. Open the original project before trusting details like terms, limits, privacy, cost, setup, or safety.

What it is

A personal wiki built from documents

LLM Wiki is framed around importing documents and letting an LLM compile them into durable wiki pages, links, summaries, review items, and searchable context rather than answering from scratch each time.

Why it stands out

Document memory with graph context

The project combines document ingest, source traceability, knowledge graph views, lint and review flows, optional vector retrieval, deep research, and an Obsidian-compatible wiki folder into one desktop workflow.

Availability

Repo, releases, local API, and agent skill

Readers can inspect the public repository, download desktop releases, review the local HTTP API, or compare the companion skill that lets an agent query a running LLM Wiki instance with local citations.

Why it matters

Why readers may notice it

Many readers are trying to move beyond loose chat history and into knowledge systems that stay organized over time. It gives them a concrete app to compare for document memory, source-backed wiki pages, and agent-readable personal context.

Reporting note

What appears notable

The repository is useful for checking the two-step ingest flow, source traceability, graph insights, optional embedding search, source-folder watching, deep research providers, Chrome web clipper, local token-protected API, and companion agent skill.

Before using

What readers may want to review

How sensitive documents, imported folders, web-clipped pages, generated wiki files, API keys, and provider settings will be stored and handled on the reader's machine.

Which model provider, embedding endpoint, web search provider, and optional vector-search setup fit the intended project and budget.

Whether to enable the local API and companion agent skill, and how token access should be managed before connecting external tools.

Reader fit

Who may find it relevant

Readers who want a desktop knowledge base that turns documents into source-linked wiki pages instead of only storing chat answers.

Builders comparing personal RAG, Obsidian-adjacent knowledge workflows, graph search, and agent-readable local context.

Less relevant for readers looking only for a hosted chatbot, a model checkpoint, or a simple note-taking app without LLM-maintained structure.

Editorial note

Why it is included here

The original LLM Wiki materials give readers a starting point for persistent, source-linked personal knowledge bases, including the agent-context layer that can help tools query local documents more deliberately.

Source links

Original materials

Reader note

Before relying on this entry

LifeHubber lists entries to help readers inspect AI projects, not to endorse them or prove they are safe, suitable, accurate, maintained, or right for a specific use. We do not verify every entry in depth. Before relying on anything listed, review the original materials, terms, privacy practices, limits, and risks that matter for your situation.

Sponsored

Sponsored

Related in LifeHubber

Keep the thread going

Follow the next layer with AI Resources for AI projects worth inspecting at the source, AI Guides for decision habits for messy AI choices, AI Access for free and low-cost ways to compare AI model access, AI Ballot for a clearer view of what readers are leaning toward, and AI Radar for AI stories that deserve a second look.