From Obsidian Vault to AI-Powered Knowledge Graph in Minutes

Chaos Cypher has introduced a pipeline that converts an Obsidian vault archive into an AI-powered knowledge graph, using an LLM to extract typed entities and relationships directly from Markdown without requiring pre-existing wiki-links. The tool indexes notes with local embeddings for semantic search and RAG chat, then runs extraction to surface connections the user never manually linked. The same import is available through the web UI, a REST API (POST /api/v1/sources and /api/v1/sources/batch), and the CLI command `chaoscypher source add my-vault.zip`.

Open your Obsidian graph view and look at it honestly: every line on that screen is a link you typed by hand. The person mentioned in forty notes but never linked , the concept that appears under three different names, the two projects connected by a decision you wrote down once and forgot -- none of it shows up. Your vault knows more than its graph does. Chaos Cypher adds the missing layer. It reads the Markdown itself, extracts entities and relationships with an LLM, and makes the whole vault searchable and chat-ready -- without requiring a single connection to be pre-linked. Your manual wiki-links stay exactly what they are: deliberate structure. The AI-discovered layer sits alongside them, surfacing the connections you never typed. No plugin required -- the archive loader does the work: Confirm the detected domain. Indexing chunking + local embeddings takes seconds and immediately enables semantic search and RAG chat. After indexing, Chaos Cypher analyzes your notes and proposes an extraction domain https://chaoscypher.com/docs/user-guide/domains -- review and confirm or override it in the dialog, and extraction starts. Wait for extraction. Extraction builds the graph: typed entities and relationships pulled from the prose itself. Explore what the AI found. People mentioned across multiple notes, concepts that appear under different headings, projects connected by shared decisions, recurring themes that were never explicitly linked -- now visible, navigable, and traceable back to the exact notes they came from. The steps above walk through the UI, but the same pipeline is reachable without opening a browser. For developers: POST /api/v1/sources takes a multipart file upload and runs it through the identical loader dispatch the UI uses -- point it at your vault archive and it works the same way. POST /api/v1/sources/batch accepts a list of files if you're importing several exports at once, which is handy wired into a nightly vault-backup job: export, POST the archive, let indexing and extraction pick it up. In plain English: anything the "Upload" button does, a script can do too, over HTTP. For CLI users: the same import is one command: chaoscypher source add my-vault.zip source add isn't Obsidian-specific -- it's the general-purpose source-loading command, and it routes to the archive loader the same way the web UI does whenever it sees a .zip or .tar.gz . There's no separate "import vault" subcommand, because none is needed. In plain English: if you'd rather stay in the terminal, one command gets your vault into the graph. This workflow shines wherever the value isn't only in the notes but in the relationships between them: research notes, project journals, meeting archives, long-running personal knowledge bases. A first-class Obsidian importer -- reading vaults directly, preserving wiki-links as graph edges alongside the AI-discovered ones -- is on the roadmap. If that's your use case, tell us how you'd want it to work https://github.com/chaoscypherinc/chaoscypher/discussions ; vault structures vary wildly and real examples shape the design.