Skip to main content
Andrej Karpathy’s llm-wiki Gist hit 5,000+ stars within weeks, and developers finally saw a solution to a problem they had for a long time: information everywhere, nothing organized. Here’s how it works: feed raw documents into an LLM, have it compile everything into an interlinked wiki of markdown files, and use Obsidian to browse and query the result. The LLM writes and maintains the wiki; you just supply sources and ask questions. Knowledge compounds every time you use it. In this guide, we’ll walk you through how to build your own Karpathy-style Wiki Knowledge Base with OpenCode and SiliconFlow. OpenCode is the agent that does the actual work — browsing the web via Chrome, extracting content, and writing structured markdown into your Obsidian vault. The oh-my-openagent plugin makes OpenCode smarter: instead of using one model for everything, it routes each task to the model best suited for it — fast models for extraction, strong reasoners for analysis, long-context models for compilation. All of these models run through SiliconFlow, giving you access to 200+ frontier models — DeepSeek V4 series, GLM-5.1, Kimi K2.6, and more — with a single API key.

​
Prerequisites

Before you begin, ensure you have:

​
Step 1: Give Your Agents the Right Models

oh-my-openagent is a plugin that transforms OpenCode from a single-model assistant into a multi-agent development team. It provides specialized discipline agents — each tuned for a different type of cognitive work:
AgentRoleRecommended modelNote
sisyphus / prometheus / atlasOrchestration, planning. Communicative models.Kimi-K2.6 / GLM-5.1Claude-like family — safe swap
hephaestus / oracle / momusDeep autonomous work, complex reasoning. Principle-driven.DeepSeek-V4-ProDo not use Kimi/GLM here
explore / librarianFast search, documentation retrieval.DeepSeek-V4-FlashHigh-reasoning models are overkill
multimodal-looker / visual-engineeringVisual tasks, frontend, multimodal.Qwen3-VL-32BVLM models
When you submit a task, Sisyphus delegates subtasks to the right agent, and each agent uses the model best suited for its work — without manual juggling. For more details, please refer to oh-my-openagent official document: https://omo.dev/docs

​
Installation

Open your OpenCode and paste the following prompt: 
Install and configure oh-my-openagent by following the instructions here:
https://raw.githubusercontent.com/code-yeongyu/oh-my-openagent/refs/heads/dev/docs/guide/installation.md
Or read the full Installation Guide for manual setup, provider authentication, and troubleshooting.

​
Configuration

Then edit ~/.config/opencode/oh-my-openagent.jsonc to wire each agent to a model. Here’s a recommended configuration: 
{
  "$schema": "https://raw.githubusercontent.com/code-yeongyu/oh-my-openagent/dev/assets/oh-my-opencode.schema.json",
  "agents": {
    "sisyphus": {
      "model": "siliconflow/moonshotai/Kimi-K2.6"
    },
    "prometheus": {
      "model": "siliconflow/zai-org/GLM-5.1"
    },
    "metis": {
      "model": "siliconflow/zai-org/GLM-5.1"
    },
    "atlas": {
      "model": "siliconflow/zai-org/GLM-5.1"
    },
    "hephaestus": {
      "model": "siliconflow/deepseek-ai/deepseek-v4-pro"
    },
    "oracle": {
      "model": "siliconflow/deepseek-ai/deepseek-v4-pro"
    },
    "momus": {
      "model": "siliconflow/deepseek-ai/deepseek-v4-pro"
    },
    "explore": {
      "model": "siliconflow/deepseek-ai/deepseek-v4-flash"
    },
    "librarian": {
      "model": "siliconflow/deepseek-ai/deepseek-v4-flash"
    },
    "multimodal-looker": {
      "model": "siliconflow/Qwen/Qwen3-VL-32B-Instruct"
    }
  },
  "categories": {
    "ultrabrain": {
      "model": "siliconflow-cn/Pro/zai-org/GLM-5.1"
    },
    "deep": {
      "model": "siliconflow-cn/Pro/zai-org/GLM-5.1"
    },
    "visual-engineering": {
      "model": "siliconflow/Qwen/Qwen3-VL-32B-Instruct"
    },
    "artistry": {
      "model": "siliconflow/deepseek-ai/deepseek-v4-flash"
    },
    "writing": {
      "model": "siliconflow/deepseek-ai/deepseek-v4-flash"
    },
    "quick": {
      "model": "siliconflow/deepseek-ai/deepseek-v4-flash"
    },
    "unspecified-low": {
      "model": "siliconflow/deepseek-ai/deepseek-v4-flash"
    },
    "unspecified-high": {
      "model": "siliconflow/deepseek-ai/deepseek-v4-flash"
    }
  }
}

​
Step 2: Initialize Your Wiki in Obsidian

Once the oh-my-openagent plugin is installed, type ultrawork (or ulw for short) to activate Ultra Work mode, and you’re ready to build your wiki knowledge base in Obsidian. Open OpenCode and tell it:
ulw Build me a personal wiki knowledge base in Obsidian following Andrej Karpathy’s wiki knowledge base concept (reference: https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f).
OpenCode, powered by oh-my-openagent, will research your sources and then create the scaffolding — folders for entities, concepts, and raw sources; an index that links everything together; and entry templates with fields for summaries, tags, and source URLs. You don’t need to design the structure yourself.
Image (37)
Open the generated folder in Obsidian (File > Open Folder as Vault) and you’ll see the full wiki structure. To populate it, drop your source files into the raw folder — or let OpenCode do that for you. In the next step, we’ll show you how to use OpenCode’s browser automation to make the entire data collection and analysis pipeline hands-off.
Image (38)
Image (32) Copy (1)

​
Step 3: Let OpenCode Browse for You

This is where the pipeline gets interesting. Because Chrome exposes the Chrome DevTools Protocol (CDP), OpenCode can launch a browser in debug mode and take control of it — browsing pages, clicking through navigation, and reading the content just like you would manually. Tell OpenCode:
Launch Chrome in debug mode and browse the sites you want to visit. Explore your key topics, compile your findings, and save the source material to the raw/ folder in my wiki knowledge base. Then ingest the sources in raw/ — extract the key entities, concepts, and summaries, and create wiki entries for each with cross-links between related pages.
OpenCode will open the browser, navigate the page, and take notes. Once it’s done reading, it saves the content as raw source material in your wiki vault. You can do this for as many sources as you want. You can also skip the browser entirely and just drop existing files — notes, PDFs, articles — directly into the raw/ folder. Then, it identifies entities (companies, models, APIs), extracts concepts (RAG, MoE architecture, token pricing), writes summaries, and builds cross-links between entries. Everything gets written into your Obsidian vault as structured markdown files.
Image (39)

​
Here’s What You Get

Press Ctrl+G / CMD+G in Obsidian to open Graph View. This is what the wiki looks like after processing documentation from SiliconFlow, DeepSeek, Stepfun, and Z.ai — along with a few background research entries on Andrej Karpathy and AI infrastructure companies. Every node is an entry. Every line is a connection the AI found. The knowledge base didn’t just store the content; it understood the relationships.
Image (40)

​
Your Wiki Grows With You

The loop is simple:
  1. Come across something worth keeping — a useful project, an insight, a rabbit hole you want to revisit
  2. Tell OpenCode to go read it
  3. It becomes part of your wiki
  4. Next time you’re curious about the same topic, you already know more
Once the wiki reaches critical mass, you can ask OpenCode complex questions against it — and it will go research, cross-reference, and synthesize answers from everything you’ve accumulated. Karpathy called this the point where things “get interesting.” Your curiosity compounds.

​
Resources

​
Andrej Karpathy’s llm-wiki

​
OpenCode

​
oh-my-openagent

​
SiliconFlow