llm-wiki

Self-cartography engine.

Turn your scattered personal data into a queryable Obsidian wiki. You and your agents read from the same surface.

[!WARNING] Heavy prototype development. This is a single-author scratch space, not a stable tool. Architecture, CLI surface, file layout, and config schema can break at any time without notice or migration path. No semver, no deprecation cycle, no compatibility promises. If you install it, expect to read commits before pulling.

11 substrate collectors

8 psychometric instruments

MIT open source

Yesterday's Claude Code session is already a daily-log entry. This week's screenshots already have a summary article. Open a fresh agent session and the wiki index loads before you type. You read what the agent wrote. The agent reads what you wrote. Both refine the same surface.

Contents

• What is this · Why it exists · What you get
• What it looks like in Obsidian · Two ingest paths converge at compile · What a compiled article looks like · The defining choice
• Engine vs. vault split · Install · Update · Running scripts manually
• Documentation map · Security · CLI Reference · For contributors

What is this

An opinionated knowledge-compilation engine for personal substrates. Drop raw materials in — daily session logs, web clippings, screenshots, emails, calendars, browser history, HTML files — and a Claude Agent SDK loop compiles them into atomic Markdown articles with wikilinks. Renders as a navigable wiki inside Obsidian. The same wiki gets injected into every AI-agent session as context, so the loop closes: you read what you wrote, the agent reads what it wrote, both refine the same surface.

The vault holds data. The .wiki/ directory holds the engine. They never mix on disk.

A map, not an agent. The wiki is a map of the operator — a compiled, always-current, descriptive portrait of what you know, did, and committed to, read daily by you and your agents. It describes; it doesn't act. That's why it's a self-cartography engine, not a "second brain": "brain" implies the part that thinks and does, which is deliberately out of scope. Anything that acts on the map — automating a task, syncing a commitment to an external tool — is an operator-gated consumer downstream of the compiler, never the compiler itself.

What this isn't. Not a vector database, not a RAG service, not a Notion / Logseq / Mem replacement, not a docs-site generator, not a team wiki — and not a task manager, executive/agent layer, or "second brain." It is a compile loop for one operator's substrates, output as plain Markdown that any tool can read.

Why it exists

A solo knowledge worker's thinking lives in too many partial substrates: daily notes capture what happened, AI-agent memories capture working thought, clippings capture curiosity, screenshots and calendars capture everything else. Each is queryable in isolation, but not as a whole — and most are illegible even to the person who produced them.

Existing tools either solve a slice or solve a different problem:

• Karpathy's LLM Wiki — the raw/ → knowledge/ shape and the compile-don't-retrieve choice; a sketch, not a working pipeline.
• claude-memory-compiler (Cole Medin) — the session-capture pattern; only handles AI-agent memories, doesn't ingest other substrates.
• Obsidian — manual curation, no compilation.
• Notion — team docs, not personal cartography.
• RAG systems — retrieval, not compilation; weak cross-doc reasoning.