← Back to blog

Save Vault Is a Wiki Builder for the Claude Era

· Save Team
wikiknowledge-baseclaudemcpsave-vaultaipersonal-knowledge-management

For the first year of Save’s life, we described it as a web clipper. You hit the button, you got a markdown file, you put it somewhere.

That description is no longer accurate.

With the new Connect to Claude toggle in Save Vault, the saved files stop being a pile of clippings and start being a wiki — one that Claude can read, search, link, and answer questions across. Save Vault isn’t a clipper anymore. It’s a wiki builder.

This post is about what changed, why it matters, and what becomes possible when your reading compounds into a structured personal knowledge base.

The Shift From Clipper to Wiki

Web clippers have existed for 20 years. Evernote, Pocket, Instapaper, Readwise, Obsidian Web Clipper. The pattern is always the same: see a page, save a copy, hope you’ll re-read it later.

Almost nobody re-reads. The clippings pile up. The clipper becomes a graveyard.

A wiki is different. A wiki has structure. Pages link to other pages. Concepts get their own articles. New information updates old articles. You don’t re-read a wiki — you query it.

Until recently, wikis required humans to maintain them. That’s why personal wikis never took off: the maintenance cost dwarfs the reading cost. Andrej Karpathy’s viral LLM Knowledge Bases post on April 3, 2026 made the obvious-in-hindsight observation that LLMs are now good enough to maintain a wiki for you. You ingest raw markdown. The LLM compiles it into structured pages, with backlinks, summaries, and concept articles. You query it like a wiki, but you never write a wiki page yourself.

Save Vault is built around this shift.

The Three Loops of a Living Wiki

A self-maintaining wiki has three loops. Save Vault gives you all three.

Loop 1: Ingest

You read something on the web that you want to keep. Click the Save button. The Chrome extension produces clean markdown using Gemini, ships it to Save Vault, and Save Vault writes it to a knowledge base folder you picked.

This is the only loop you actively run. Everything else is initiated by Claude.

The ingestion handles the things web clippers historically failed at:

  • Paywalled articles you have access to
  • YouTube videos (full transcript, not just metadata)
  • X/Twitter threads
  • Reddit discussions
  • TikTok captions and Instagram reels
  • Documentation with code blocks intact

Each save lands as a clean .md file. No HTML cruft, no ad markup, no navigation menus. Just the content, structured the way an LLM expects to see it.

Loop 2: Compile

This is the loop Karpathy described. Periodically — once a week, once a month, whenever you feel like it — you ask Claude Code to compile the raw saves into a wiki.

cd ~/Documents/Save\ Vault/AI\ Research
claude

Then ask it to:

  • Read every file in the folder
  • Generate concept pages for repeating themes
  • Add backlinks between related ideas
  • Write a _index.md with the wiki’s table of contents
  • Run a “lint” pass to flag inconsistencies, gaps, or duplicates

Claude grinds through your folder and produces a navigable structure. The original saves stay where they are — the wiki layer sits on top, linking to them.

You’re not editing files. You’re delegating the editing.

Loop 3: Query

Once Save Vault is connected to Claude (the toggle in the menu bar), every conversation in Claude Desktop or Claude Code can hit your vault. Ask any question. Claude searches your saves, reads the relevant ones, and answers using your sources.

The MCP server exposes four tools: list_knowledge_bases, list_files, read_file, and search. Claude picks them up automatically.

The result is that your reading turns into recall. “What did that PM at Linear say about retention loops?” becomes a one-line question instead of a frustrated browser-history search.

What Changes When You Have a Wiki Instead of a Folder

The practical differences are bigger than they sound.

Recall instead of search. A folder needs you to remember the file name. A wiki lets Claude do the remembering. Ask a vague question, get a sourced answer.

Compounding instead of bloat. In a folder, the 200th file makes everything harder to find. In a wiki, the 200th file makes the wiki better, because it adds context the LLM can connect to existing concepts.

Personal context instead of generic answers. Claude’s default behavior is to answer from training data. With Save Vault connected, it answers from your saved sources — articles you chose to save, framed by problems you actually have.

Provenance instead of hallucination. Every claim Claude makes can be traced to a specific .md file in your vault. You can open it, read it, edit it, or delete it. There are no embeddings, no opaque vector indexes, no “the AI said so.”

Knowledge Bases Are the Wiki Spaces

Save Vault organizes saves into knowledge bases — subfolders in ~/Documents/Save Vault/. A KB is the smallest unit of “topic” the wiki understands.

A typical setup looks like:

Save Vault/
  General/                  # default catchall
  AI Research/              # papers, threads, blog posts
  Competitors/              # competitive intel
  Customers/                # user interviews, support tickets
  Hiring/                   # candidate research, role refs

Each KB compiles into its own wiki. Claude sees all of them via list_knowledge_bases and picks the relevant one based on your question. You can have one KB or twenty — it scales linearly because Claude only opens the files it needs.

This is the part where the “wiki builder” framing actually pays off. A folder has no concept of topic. A KB does. Claude treats each KB as a coherent body of knowledge to query against.

Why Now

Three things had to be true for the wiki-builder pattern to work, and 2026 is the first year all three are.

  1. LLMs got long enough context windows to read hundreds of markdown files in one session. (Claude’s 1M-token context shipped earlier this year.)
  2. MCP became the default protocol for connecting LLMs to local files. Karpathy’s post would have been impractical 12 months ago. Now it’s a toggle.
  3. Web clippers got smart enough to extract clean content from arbitrary pages — including video, social, and dynamic JS-heavy sites — without per-site rules.

Save Vault is what happens when you assume all three. The clipper, the folder, and the MCP server were going to be three separate tools forever. Now they’re one app and one toggle.

Set Up Your First Wiki

It takes about five minutes.

  1. Install the Save Chrome extension
  2. Install Save Vault from savemarkdown.co
  3. In Save Vault, create a KB for your first topic (e.g. AI Research)
  4. Click Connect to Claude in the menu bar
  5. Save the next 5 things you read
  6. Open Claude Desktop and ask a question about them

You’ll have your first three-file wiki by lunch. The compounding starts the moment you hit Save the second time.

Save Vault is free. The Save extension is free to start. Get both at savemarkdown.co.