Building an LLM Wiki 📚

This feature grows scattered material into a knowledge wiki the agent manages on its own. A movie's lore, a recipe book, a paper archive, a work wiki — anything works.

← Home: ObsiKO 101 · Parent: 16 AI Agent

---

Getting started

💡 In Prompt Helper ▸ Wiki tab you can start by writing just a topic. Once you have a wiki, you can also add material, see its status, and ask to organize it or answer questions there. → 16-7 Prompt Helper

1. (Optional) Open a fresh vault, and tell the agent "build me an LLM wiki."
2. The agent will ask whether you want a quick start or a deep start.
   • Quick start: just give it a topic and language, and it sets up a basic skeleton in seconds.
   • Deep start: it asks more — who you are and why you're collecting this (your reuse axis), the wiki's sub-categories, the kinds of material, how often it updates, and even the agent's personality (persona) — for a sturdier setup.
3. Once you've answered, it builds the folders, system files, and a getting-started guide (Read-me-first.md) all in one go.

📱 On mobile too (a lightweight edition)

Even without a desktop, you can start a lightweight LLM wiki from the chat AI on your phone or tablet.

• Say "build me an LLM wiki" in chat and it creates the essential skeleton — the rulebook (AGENTS.md), index.md, and the 00. Inbox / 10. Raw Sources / 20. Wiki folders. That's already a real wiki: collect, ask, and lint all follow the rules.
• Day-to-day use works on your phone as well: the chat recognizes a wiki vault on its own and files material by the rules. "Organize this", questions, "check this over" — all fine.
• Requirements: the chat AI has an API key, and Allow note editing is ON in options (≡). → 16-8 Chat-only Mode (Mobile & Web)
• For the full edition (the Soul.md persona interview, /ingest-style command files, the wiki-map.canvas structure map), continue with the desktop agent — it's the same vault, so the skeleton you built on your phone carries straight over.

The resulting structure

• System files: CLAUDE.md (entry point/manifest) · Soul.md (the agent's identity) · AGENTS.md (working rules) · user.md (about you) · memory.md (things you've agreed on together) · index.md (dashboard index) · log.md (work log)
• Folder hierarchy:
  • 00. Inbox/ — an inbox where you drop new material.
  • 10. Raw Sources/ — kept exactly as-is (never edited). Organized by kind, e.g. 11. Articles/12. Papers/13. Books….
  • 20. Wiki/ — the wiki pages the agent curates and maintains. Organized by category, e.g. 21. Concepts/22. Entities/23. Guides/24. Maps….
  • 30. Queries/ — where answers to your questions get filed back as pages.
  • 80. References/ — storage for images and attachments.
• A structure mind map, wiki-map.canvas — a mind map of the whole wiki at a glance (center = wiki name, branches = categories). You can drag it around and edit it yourself!

💡 Subcategory names adapt to your topic — a worldbuilding wiki might use 21. Characters/22. Factions/23. Places/24. Timeline instead.

📥 File formats you can drop in Inbox (the agent can read them)

These are the file extensions the agent can read and organize when you put them in 00. Inbox/ or drag them into the chat.

💡 poppler, pandoc, and whisper are free external tools — they're only needed when you ask for that specific format, and if they're not installed you'll get a one-line install tip. (Text, images, and data tables work right away with no extra install! And transcription works without whisper too — with an OpenAI/Gemini API key it goes through the cloud.) For video URLs, YouTube, or RSS, just give the address instead of a file.

Running it (4 core actions)

Just drop material into 00. Inbox/ and talk to it. It works both in natural language and via slash commands. (Note: /ingest, /query, /lint, /status below are not the built-in assistant commands — they work through rules (system files) installed into that vault when you build an LLM wiki — so calling them in natural language is more reliable. Newly built wikis install the commands for desktop and mobile chat, so /ingest shows up on your phone too.)

• Ingest: keeps Inbox material as-is in 10. Raw Sources/, then creates or updates wiki pages linked together with wiki links, and updates index.md and log.md. One topic = one page — it first looks for an existing page (aliases included) and updates that, adding new spellings as aliases; re-adding the same source doesn't create duplicates. Processed Inbox files are marked "done" with a one-line note so they aren't processed twice.
• Query: answers based on the wiki pages, citing sources, and saves valuable answers to 30. Queries/.
• Lint: fixes orphaned pages, broken links, and index mismatches; suspected duplicates and contradictions (flagged with > [!warning]) are reported as candidates for you to decide — never merged on its own.
• Status: summarizes counts per tier and recent collection activity from the actual files.

Making it your own

• Open Soul.md (personality), AGENTS.md (rules), user.md (about you), and memory.md (shared memory) and edit them directly to change how the agent behaves. The wiki is effectively the agent's "brain"! (Wikis built earlier may use a hidden .memory.md instead — it works the same.)
• Start by reading the Read-me-first.md file created in the vault.
• (Optional) In the panel's options (≡) button → the 'git' category, turn on "Auto-commit to git after agent work" to stack up changes as snapshots — connect a remote (GitHub) too for automatic backups! → 23 Settings & Themes

📤 Sharing it with others (Send this wiki)

To let a friend or colleague use the same wiki, bundle it into one file and hand it over.

1. In the wiki vault, click the share button (↑) at the top right ▸ Share this whole wiki ▸ [Send as a file] (or ＋ ▸ Add knowledge pack ▸ Send this wiki…, or "Send LLM wiki" in the command palette).
2. Pick Structure only (rules, persona and folders — they start with their own sources) or With contents (the pages and sources you've collected — to include notes unrelated to the wiki as well, turn on 'Also send notes outside the wiki'), then Save as file to get wiki-name.opack. (On a phone it's saved at the top of the vault — share it from the Files app.)
3. The other person opens an empty vault and picks the file in ＋ ▸ Add knowledge pack ▸ Import a pack file… — that's it. The rulebook, persona and commands (/ingest etc.) come along, so it runs right away.

• Left out automatically: personal files (user.md, memory.md, log.md — sent as blank placeholders), unprocessed items in the Inbox, and notes unrelated to the wiki. Images and attachments can't fit in a pack, so they're left out (they show as blanks in the received notes).
• Look before you receive: you can open the rule files the AI follows (AGENTS.md and others), and lines worth a look — web addresses, commands — are marked. If the wiki came from someone you don't know, read them.
• A vault that already has a wiki won't receive another (two rulebooks would stop the wiki from working) — open a new empty vault instead.
• Changes made after sending don't follow automatically. To share updates, send it again — or hand over a subscription link (below).

🔗 Keep them in sync (subscription link)

A file is frozen at the moment you send it. To have the other person's copy change every time you edit your wiki, give them a subscription link.

1. In the wiki vault, press the share button (↑) ▸ Share this whole wiki ▸ [Create subscription link] (or [Create subscription link…] in the Send this wiki window, or "Create LLM wiki subscription link" in the command palette).
2. The first time, connect a GitHub account (only the sender needs one). Read the number of pages that will go up and the Good to know notes, press [Create link], and you get a one-line link https://obsiko.com/s/… — [Copy] it and give it to the other person.
3. The receiver taps the link (landing page ▸ Open in ObsiKO), or pastes it into + ▸ Add knowledge pack ▸ Subscribe by link… (command palette "Subscribe to a wiki by link"), presses [Look], then [Receive into this vault]. No sign-up or login needed — receiving into an empty new vault is recommended.

• How fast does it follow? About a minute after you edit, it publishes on its own (if the AI is organizing, it waits and publishes once when it's done), and the receiver catches up within 1–2 minutes. Publishing only happens while the sender's ObsiKO has that wiki vault open (on one device), and the receiver's side checks every minute while the subscribed vault is open.
• Who can read it? Your pages go to a new public repository (obsiko-pub-…) created on your GitHub, locked (encrypted — the key lives inside the link), and ObsiKO's server keeps only "which edition is the latest". So anyone with the link can read it, and pages already received can't be taken back — only share it with people you trust.
• What doesn't go up: your own info, memory and work log (user.md · memory.md · log.md), unsorted material in the inbox, and notes unrelated to the wiki. Images used by wiki pages go along. If a line looks like an API key, it stops and asks before publishing.
• Size limit: a subscription holds up to 3,000 files and 50 MB.
• A received wiki is locked: it can't be edited (edits made in an outside editor are undone on the next update, and the edited copy is kept in My notes/Edited copies), not even by the in-app AI. Write your own thoughts in the My notes folder. The sender's rule files are kept only as reading material in _ObsiKO/Sender rules so this vault's AI doesn't follow them — here the AI only reads the wiki and answers questions. Internet images in someone else's notes aren't loaded automatically.
• Safety brakes: if many pages disappear at once on the sender's side, it asks before deleting them here (deleted pages go to the trash). If anything looks off while receiving, it stops without changing anything.
• Stopping: the sender has [Stop publishing] (the receiver sees that it has ended) and [Change link] (everyone currently subscribed is cut off); the receiver has [Unsubscribe] — received pages stay as your own notes and become editable again.

---

💡 Tip — Use it like NotebookLM, a "my-material" assistant

Just like Google NotebookLM, you can use it as an assistant that answers only from material you've collected and cites its sources. (The tools and semantic search above effectively play the role of RAG here.) If setting up a full LLM wiki feels like too much, you can start light like this instead.

1. Gather material first: put the PDFs, documents, images, audio, and notes you'll draw on into one folder (e.g. 00. Inbox/ or Material/). Any extension from the "file formats you can drop in Inbox" table above works.
2. Answer only from your material, with sources cited: just add one line to your question —
   • "Answer only based on the attached/this folder's material, and cite the source (filename, passage). If it's not in the material, say so honestly (no making things up)."
3. The same kinds of outputs NotebookLM gives you:
   • "Make a core-summary briefing from this material" · "Turn it into a study guide (concepts, likely questions)" · "Make 10 FAQs" · "Make a timeline" · "Make a comparison table of the differences and similarities between these two sources"
4. Finding by meaning (semantic search): ask something like "find everything similar to this topic," and it'll use a local index to find passages that are close in meaning even if the wording differs (and answer based on those results). → See 16 AI Agent for how to turn it on

ObsiKO's edge: both your material and the answers stay as your own .md files, so they're truly yours — and if you want to grow it further, you can promote it straight into an LLM wiki and start running /query (source-cited Q&A) and /lint. In other words, it's not a "use once and done" notebook, but a knowledge base that keeps growing.

---

← Previous: Writing & Composition · Home · Next: Zettelkasten & Ontology →