Karpathy LLM Wiki

by Greener-Dalii
5
4
3
2
1
Score: 77/100

Description

The Karpathy LLM Wiki plugin turns notes into an interlinked wiki and lets you query that graph from a side panel inside the editor. It extracts entities and concepts into separate pages, adds aliases, builds bidirectional wiki links and maintains an index, while keeping source notes unchanged. Retrieval uses a five stage cascade with lexical matching, LLM generated keywords, local substring scanning, fallback reseeding and Personalized PageRank over wiki links instead of embeddings or a vector database. The plugin also includes linting, duplicate and contradiction checks, smart repair flows, batch ingestion, PDF ingestion with provider specific and local OCR paths and support for many cloud and local model providers. Query answers link back into the wiki and PDF markdown can be cached under .obsidian/plugins/karpathywiki/pdf-cache/.

Reviews

  • Ana Rosa Amorim
    Reviewed on Oct 27th, 2026
    No review text provided.

Stats

782
stars
70,481
downloads
95
forks
106
days
1
days
5
days
620
total PRs
1
open PRs
51
closed PRs
568
merged PRs
330
total issues
29
open issues
301
closed issues
1,357
commits

RequirementsExperimental

  • A configured LLM provider, such as OpenAI, Anthropic, Ollama, LM Studio or another compatible endpoint

Latest Version

5 days ago

Changelog

🌟 Karpathy LLM Wiki v1.30.0

Highlights

  • A monthly Periodic Lint no longer crashes Obsidian. 30 * 24 * 60 * 60 * 1000 is 2,592,000,000 ms, and a browser timer converts its delay to a signed 32-bit integer: the value wrapped negative, clamped to 0, and the callback ran as fast as the event loop allowed. With no watched folders configured every one of those ticks started a full vault lint. One reporter's 313,000-file vault exhausted a 3.3 GB / 4.2 GB heap about 85 seconds after launch, six crash reports deep. The period is data now, not a timer delay, and a lint that outlives its period can no longer start a second copy of itself.
  • Extraction Focus and Additional Content Rules are edited in the settings panel. Two things used to require editing schema/config.md by hand are now fields: what the extractor should look for, and rules it must follow. The schema file stays the only place your own domain knowledge lives.
  • The answer context has a token ceiling, applied while the context is built. The old budget was a page count — 20 — and each page carried its own character cap, so there was no ceiling on the total: 20 × 12,800 characters is the worst case. On the maintainer's production vault 27 of 30 answers exceeded an 8k window while the budget still read "20 of 20". Pages are now dropped from the tail until a token ceiling is met.
  • Lint Wiki now tells you which hubs have crystallized. A page that has become the quiet centre of a neighbourhood is exactly the page a licence-to-ignore exists for. The report lists candidates with their degree. It is report-only: nothing is written, retired or merged.
  • A Query Wiki failure no longer leaves the pane dead. A model error before the answer arrived left the view stuck in its running state, so the next question did nothing. The pane is released on the failure path now.

What's in this release

Added

  • The answer context's token ceiling is fitted before assembly (Issue #880). RETRIEVAL_BUDGET = 20 still bounds the page count; what was missing was a bound on the total. queryContextBudgetTokens (default 8,192, 0 disables it) is that ceiling, and pages are dropped from the tail until the context fits.
  • "Extraction Focus" and "Additional Content Rules" live in the settings panel (Issue #895). Both are injected at call time, so the schema file keeps holding your domain knowledge only and never a runtime parameter.
  • The Lint Wiki report lists crystallized hub candidates (Issues #954 / #215). Report-only, on the one-shot Lint Wiki path. On a 175-page vault it reports nothing because the 10 hubs sit below the degree floor; on a 370-page vault it reports 3, with degrees between 35 and 43.

Changed

  • "Additional Content Rules" now says where it applies (Issue #902). The description promised a rule could add content anywhere. A rule cannot add a section: the section list belongs to the plugin, and it is enforced at all three write paths, so a rule written against a new section was dropped after the model had obeyed it. Both strings, in all 11 locales, now say a rule shapes the sections a page already has.
  • The query prompt constrains what the assistant may assert, not just how it links (Issue #908). The link rule was stated five times — about 700 characters — and almost nothing constrained an invented number. The format section is now one rule plus two examples, and the space it gave up pays for exact values, evidence, and refusal.
  • The architecture track landed and every module it named is settled (Issues #925–#928). A ratchet in gate:1 fails by name on a new import cycle or a new core/ to upper-layer edge; a golden net records ordered task labels and write paths across ingest, lint, query and conversation. Three modules were deleted, one was wired, and two moved out of src/.
  • Every dependency pin is proven to reach both trees (Issue #907). package-lock.json builds the released bundle, the pnpm tree runs CI, and neither reads the other's pins. A test now fails when the two maps differ and names the side you missed.

Fixed

  • Monthly Periodic Lint crashed the renderer (Issue #957). Daily and weekly never crossed the 32-bit limit; only monthly did. The tick is one hour, each tick compares the clock against the period, and an in-flight guard stops overlap.
  • A gateway that answers a non-streaming request with an event stream works now (Issue #916). The plugin prefers a streaming request, and a provider that ignores the flag answered with text/event-stream, which the client could not read.
  • A 2xx the SDK could not parse no longer reads as a failed status (Issue #916). The status was reconstructed from a parse failure rather than from the response.
  • An empty answer now says so (Issue #916). A model that returned a 200 with no body produced a blank pane and no explanation.
  • Turning Periodic Lint off takes effect without a restart (PR #922). clearPeriodicLint cleared the timer but left the scheduled flag set, so switching it back on did nothing until Obsidian reloaded.
  • Raising an extraction limit no longer reduces output (Issue #567, PR #924). The per-round ask was sized from the ceiling, so a larger ceiling meant fewer items per round and a smaller total.
  • A Query Wiki failure before the answer phase releases the pane (Issue #914). The view stayed in its running state and ignored subsequent questions.

Dependencies

  • The four AI SDK packages are held at their current versions (Issues #891 / #942 / #947 / #948). A single-package bump (@ai-sdk/openai 4.0.91 to 4.0.105) broke the build against the pinned peers; it was reverted and dependabot is told to wait until the four can move together.
  • Dependabot: eslint 10.12.0 to 10.13.0, vitest 5.0.0 to 5.0.5, @typescript-eslint/parser 8.71.1 to 8.72.1, fast-uri 4.2.2 to 4.2.3.

Upgrading from v1.29.0

One-click update via Obsidian Settings → Community plugins. Your wiki, your settings and your data.json are untouched: no setting was renamed or removed, no command id moved, and the page format is unchanged. minAppVersion stays at 1.11.4.

If you had Periodic Lint set to monthly, this release replaces a crash with a working feature. Nothing to do beyond updating. The first scheduled run happens one period after Obsidian loads, as before.

The answer context now has a ceiling you can see and change. Settings → Advanced settings → Context token budget. Default 8,192 tokens; 0 turns the ceiling off and restores the pre-1.30.0 behaviour exactly. If you ask long questions over a large vault and something that used to be cited is now missing, raise this first — what went missing is what no longer fitted.

Two settings panels changed shape. Extraction Focus and Additional Content Rules moved out of schema/config.md into the settings panel; if you had written those by hand in the schema file, copy the text into the panel once. The panel is the source of truth from now on.

What's accepted (and why)

  • eslint-plugin-obsidianmd 0.5.1 is not in this release. Bumping it reports 18 errors in 13 files that git diff 1.29.0..HEAD never touches: two lookbehind regexes, nine dead stores, five throws without cause, two expired eslint-disable directives. The ruleset was published the day before this release and the bot pre-review of main passed on the current pin, so gating the release on a 24-hour-old ruleset would have made the release carry someone else's debugging cost. Tracked separately.
  • The periodic-lint baseline still resets when settings are saved. schedulePeriodicLint() re-initialises it, and the settings panel re-schedules on every save, so a monthly user who saves settings twice in a month never reaches the gate. This is the behaviour the old timer had too; changing it changes what "monthly" means, so it gets its own change rather than a paragraph here.
  • lastLintTimestamp is memory-only. A user who restarts Obsidian more often than their period never reaches the gate either. Also unchanged, also tracked.
  • pnpm lint:tools-bot still reports 9 warnings, 0 errors. All are in tools/dev-instrument/: static node:* imports, console.log as the output interface, and a globalThis shim. They are the accepted structural baseline, not new findings.
  • 41 eslint-disable obsidianmd/no-global-this directives exist, all under src/__tests__/. Test files need a real global object; production code uses activeDocument and no other global. 36 of these shipped in v1.29.0 and the bot accepted them.
  • The bot pre-review for this release was run against main at 2ca089a6. The release commit adds 16 files, every one of them .md.

Installation

  1. From Obsidian — Settings → Community plugins → Browse → search "Karpathy LLM Wiki" → Install (or Update, if you already have it). Then toggle Enable. This is the path for almost everyone.
  2. From the marketplace — community.obsidian.md/plugins/karpathywiki → Add to Obsidian.
  3. Manual — only needed for a specific version or without the in-app marketplace. Take main.js, manifest.json and styles.css from this release's assets and place them in <vault>/.obsidian/plugins/karpathywiki/, then enable the plugin.

Requires Obsidian 1.11.4 or later, desktop or mobile.

Configuration

Nothing needs configuring to get the fixes. Four things are worth knowing about:

  • Settings → Advanced settings → Context token budget — the token ceiling on the pages sent with one answer. Default 8,192; 0 disables it.
  • Settings → Extraction Focus / Additional Content Rules — the two fields that were previously schema-file-only. A content rule shapes the sections a page already has; it does not add a section.
  • Settings → Periodic Lint — daily, weekly or monthly. All three now work. monthly is what used to crash.
  • Lint Wiki (command) — the report gained a "crystallized hub candidates" section. It appears only when candidates exist.

Tests

5,243 tests passing (386 files). Up from 5,096 / 369 at v1.29.0.

The additions that carry the most weight are the ones built to fail: a ratchet that fails by name on a new import cycle, a golden net that records ordered write paths across four paths, a test that reads main.js to assert the shipped bundle shape, and mutation checks on the periodic-lint fix — restoring the overflowing period fails two tests by name, deleting the in-flight guard fails one, and deleting the period comparison fails two.

Contributors

  • @green-dalii (Greener-Dalii) — Maintainer. The bulk of this cycle: the architecture track (#936, #937, #943, #944, #945, #946, #953, #958, #959), the answer-context ceiling (#886), the extraction-focus settings (#895), the query prompt rewrite (#913), the three #916 client fixes (#917), the extraction-limit fix (#924), the periodic-lint crash (#960), and the dependency tree reconciliation (#909, #920, #921, #948).
  • @NotAFlightRisk — PR #922: switching Periodic Lint off now clears the scheduled flag too, so it can be turned back on without reloading Obsidian. Before that, off → on was a dead end.
  • @Broch76 — Reported the monthly Periodic Lint crash (#957) with the diagnostics that made it a one-day fix: a 313,000-file vault, six macOS crash reports, the heap ceiling at 3.3 GB of 4.2 GB, roughly 85 seconds from launch, and a controlled experiment that pointed at this setting by turning it off.
  • @DocTpoint — Architect-level contributor and co-maintainer. Reported the extraction-limit inversion (#567): raising customEntityLimit or customConceptLimit reduced output, because the per-round ask was sized from the ceiling. Fixed in #924.
  • @CronusLM — Reported the three LLM client failure modes in #916: a gateway answering a non-streaming request with an event stream, a 2xx body the SDK could not parse, and an empty answer with no explanation. All three are fixed here.
  • @dependabot — PRs #940, #941, #942.

Full Changelog

https://github.com/GD4AI/obsidian-llm-wiki/compare/1.29.0...1.30.0

README file from

Github

Karpathy LLM Wiki plugin banner — a network of interconnected wiki pages built from your Obsidian notes

🧠 Karpathy LLM Wiki Plugin for Obsidian

An Obsidian plugin that turns your notes into a connected, queryable knowledge base — the Karpathy LLM Wiki idea, built into the editor where you already write.

Obsidian Review Perfect Score • Zero-embedding graph retrieval • 11-language native • Native PDF + images + Office ingest • Works with every provider • Local-first • No backend • GDPR-Friendly

Version License Obsidian Languages Providers Maintenance Build Status Author GitHub Stars Downloads Release Obsidian plugin Ask DeepWiki

English | 简体中文 | 繁體中文 | 日本語 | 한국어 | Deutsch | Français | Español | Português | Italiano | Русский

Official Site | Obsidian Marketplace | Blog | Discussions

🤔 Why this plugin? | 🚀 Quick Start | ✨ Features | 🌐 Ecosystem | 🛠️ Headless CLI | 🔍 How Retrieval Works | 🤖 Models | ❓ FAQ | 🎯 Is it for me? | 🔒 Privacy

Ko-fi

Karpathy LLM Wiki is free, self-hosted, and has no backend of its own. If it saves you time, a one-off coffee keeps it maintained — and a ⭐ helps just as much.


🤔 Why this plugin?

You write notes. They sit in folders. Finding what relates to what means remembering threads you forgot months ago.

Other open-source reimplementations of Karpathy's LLM Wiki idea exist — but none ships as a one-click Obsidian plugin. Most are CLI tools, Claude Code skills, or separate desktop apps; this one runs inside Obsidian — Graph View, ribbons, command palette included.

How we compare

Karpathy LLM Wiki (this plugin) nashsu / llm_wiki SamurAIGPT / llm-wiki-agent atomicstrata / llm-wiki-compiler
Delivery ✅ One-click Obsidian plugin 🟡 Tauri desktop app 🟡 Claude Code / Codex / OpenCode / Gemini CLI skill 🟡 TypeScript CLI pipeline
Dependencies ✅ None — plugin only 🟡 Python runtime + sqlite 🟡 Claude Code / Codex / OpenCode runtime ❌ Embedding model + vector DB (per their docs)
i18n (UI + wiki output) ✅ 11 languages 🟡 EN / 中文 ❌ EN only ❌ EN only
LLM providers ✅ 16+ (Anthropic, OpenAI, Bedrock, Gemini, DeepSeek, Qwen, Grok, Kimi, GLM, MiniMax, Step, Hunyuan, MiMo, Gemma, Codex OAuth, Ollama, LM Studio, OpenRouter, Anthropic-Compatible, …) 🟡 OpenAI-compatible 🟡 Subscription via Claude Code / Codex 🟡 OpenAI-compatible
Retrieval & query pipeline ✅ PPR + Monte Carlo over [[wiki-link]] graph 🟡 2-hop decay (4-signal heuristic) 🟡 Louvain community detection 🟡 BM25 + semantic over chunks
Graph visualization ✅ Obsidian's native Graph View (built in, zero extra size) 🟡 Custom sigma.js + graphology in desktop app 🟡 vis.js graph.html (separate file) ❌ Read-only browser viewer
Ingest formats ✅ Markdown + PDF + images + Office (DOCX/PPTX/XLSX) — one switch flips between native PDF (Anthropic / OpenAI / Bedrock / Gemini) and the built-in MinerU multi-format backend 🟡 Markdown + PDF 🟡 Markdown / code files only 🟡 Markdown only

Three we left off the table: sdyckjq/llm-wiki-skill was a Codex skill that 404s today (deleted by author); atomicstrata is included even though its retrieval is chunk-based because it's the most active TypeScript alternative; nashsu ships the largest user base of the three (10k+ stars, others 2k+) but is a Tauri desktop app, not an Obsidian plugin.

Three things we chose on purpose, not by accident

  • 🪟 Obsidian is the runtime. No terminal, no separate app, no Docker, no Python. Install from Community Plugins, click Ingest, the wiki lives in your vault from the first second. Obsidian's native Graph View renders your [[wiki-link]] graph — built in, zero extra bundle size.
  • 🧭 Clean and self-contained. Zero dependencies. No embedding model, no vector database, no pip package — a single plugin that reads your notes, talks to an LLM, and writes wiki pages. Everything lives inside Obsidian.
  • 🔌 Any model you already pay for. Anthropic, Bedrock, OpenAI, ChatGPT Plan (Codex OAuth), Gemini, DeepSeek, Qwen, Grok, Kimi, GLM, MiniMax, Step, Hunyuan, MiMo, Gemma, Ollama, LM Studio, OpenRouter, Anthropic-compatible, custom endpoint — sixteen-plus providers, none of them required to have an embedding endpoint.

🎯 Is it for me?

✅ Yes, if you:

  • Want a 5-minute setup, not a 5-hour project. Install from Community Plugins → pick a provider → Ingest one note. No CLI, no Python, no separate runtime, no vector DB. You see wiki pages in wiki/ within seconds.
  • Want something clean and self-contained. The plugin has exactly zero external dependencies: no embedding model, no vector database, no pip package, no Docker container. It's a single Obsidian plugin that reads your notes, talks to an LLM, and writes wiki pages into your vault. Everything lives inside Obsidian.
  • Want a queryable chat that answers from your notes — not the internet — with every answer carrying [[wiki-links]] back into your knowledge graph.
  • Care about data sovereignty — runs fully local with Ollama or LM Studio, never touching the internet.
  • Write in or read from any of 10 supported languages — the UI and wiki output language are independent (your wiki can be in Chinese while the interface is in English).
  • Maintain the graph by writing [[wiki-links]] — every link you write already enriches retrieval; no separate tagging/embedding/indexing step.
  • Want one-click maintenance — Lint health scan + Smart Fix All keep duplicates, dead links, and orphan pages in check without you hand-curating.

❌ No, if you:

  • Want a general-purpose ChatGPT replacement — answers come from your vault only, not the internet.
  • Need RAG over large external corpora (Confluence, Notion, arXiv, scraped web pages) — the plugin ingests your vault plus standalone PDF/Office files; bulk external-corpus RAG is out of scope by design.
  • Want a hosted SaaS with team collaboration — there's no backend, no server, no shared state; everything runs locally inside your Obsidian.

🚀 Quick Start

  1. Install. Obsidian → Settings → Community plugins → Browse → search "Karpathy LLM Wiki" → Install → Enable. Or visit the Community Plugin page and click Add to Obsidian.

  2. Configure a provider. Open Settings → Karpathy LLM Wiki → pick a provider (OpenAI, Anthropic, Ollama, ChatGPT Plan (Codex OAuth), etc.) → enter API key (not needed for local) → click Test Connection → Save.

  3. Ingest one note. Two ways:

    • ⌨️ Keyboard: Cmd+P/Ctrl+P → "Ingest single source" → pick any Markdown (or PDF, v1.25.0+) file.
    • 🖱️ Toolbar icon: Click the sticker icon in Obsidian's left ribbon to instantly ingest the currently-open note — no menu hunting.

    Your first wiki pages appear in wiki/sources/, wiki/entities/, wiki/concepts/ within seconds.

  4. Query your wiki. Two ways:

    • ⌨️ Keyboard: Cmd+P/Ctrl+P → "Query wiki".
    • 🖱️ Toolbar icon: Click the message-circle icon in Obsidian's left ribbon.

    A right-docked side panel opens (Copilot-style) where you can chat with your wiki. Answers carry [[wiki-links]] back into your knowledge graph.

Right-docked Query Wiki side panel in Obsidian showing a chat interface with wiki-link answers back to your knowledge graph

That's it. The plugin modifies nothing in your original notes — only creates new pages under wiki/. Both Ingest and Query wiki are pinned to the left ribbon for one-click access anytime. (Cmd on macOS, Ctrl on Windows/Linux.)

Core commands

Command What it does
📥 Ingest single source Cmd+P/Ctrl+P → "Ingest single source" — pick a Markdown or PDF (v1.25.0+) file, get entity/concept/wiki pages. Also: 🖱️ ribbon sticker icon on the active note.
📂 Ingest from folder Cmd+P/Ctrl+P → "Ingest from folder" — batch-ingest every note in a folder, with smart batch skip
📑 Ingest multiple files Cmd+P/Ctrl+P → "Ingest multiple files" — pick a subset via a two-pane file tree (with live queue + per-file cancel)
🔍 Query wiki Cmd+P/Ctrl+P → "Query wiki" — chat with your wiki in a right-docked side panel; answers carry [[wiki-links]]. Also: 🖱️ ribbon message-circle icon.
🛠️ Lint wiki Cmd+P/Ctrl+P → "Lint wiki" — full health scan: duplicates, dead links, empty pages, orphans, missing aliases, contradictions
⚡ Smart Fix All inside Lint Modal — one-click causal-order repair with per-phase report
📋 Regenerate index Cmd+P/Ctrl+P → "Regenerate index" — rebuild wiki/index.md with current pages and aliases
⏹ Cancel Cmd+P/Ctrl+P → "Cancel current ingestion" or click the status bar — stops cleanly at the next batch boundary
📊 Ingestion history Cmd+P/Ctrl+P → "View operation history" — searchable UI for past ingestions, lint reports, maintenance runs

Command panel — all Karpathy LLM Wiki commands live in Obsidian's command palette

Before After
notes/machine-learning.md (a flat file) wiki/concepts/supervised-learning.md with [[bidirectional links]], aliases, source attribution, and an entry in wiki/index.md

📖 Walkthroughs in GitHub Discussions → Guides. Found it useful? Star the repo to follow releases.


✨ Features

📚 Knowledge quality

  • 🔍 Entity & concept extraction — LLM extracts entities (people, orgs, products, events) and concepts (theories, methods, terms) into standalone pages. Granularity is configurable (Minimal → Fine, plus Custom) so you trade cost vs. depth.
  • 🏷️ Mandatory aliases — every page ships with at least one alias (translation, abbreviation, variant) so cross-language duplicate detection works.
  • 🔄 Tiered duplicate detection — Tier 1 (direct name match: cross-language, abbreviation, high-similarity titles) is always verified; Tier 2 (shared links, medium similarity) fills remaining token budget.
  • 🧩 Smart merge & contradiction state — duplicates merge while preserving aliases; contradictions are flagged with source attribution; reviewed: true pages are protected from overwrite.
  • 🎨 One tag vocabulary, yours — the tags a page may carry come from three places you control: the nested tags of your notes, the nested tags already on wiki pages, and the list in Settings → Wiki → Tag Vocabulary → Custom (the place for a term no note carries yet). Prompt, write gate, lint and retag all read this one list, so what the model is offered is exactly what lands on disk; a value outside it is dropped, never written. Source pages carry it too, next to their form tag. Small/local models still drift (about one in ten returns the model's built-in taxonomy) — the gate catches it, and Lint reports a page left without tags. Design anchor: Issue #328.

📄 Document / PDF / Image ingest

Five on-ramps, switchable per ingest:

  1. 🆕 Built-in MinerU backend (v1.27.0, #404) — Settings → Wiki Configuration → Markdown Conversion Backend → MinerU. PDF + images (PNG/JPG/JPEG/JP2/WebP/GIF/BMP) + Office (DOC/DOCX/PPT/PPTX/XLS/XLSX) through MinerU's Precise parser. Token in Obsidian SecretStorage. Best path for scientific papers, scanned documents, and Office files where layout preservation matters. Server caps: 200 MB / 200 pages per PDF, 256 MB / 10,000 files per archive.
  2. ☁️ Cloud providers with native PDF — Anthropic, OpenAI, Google Gemini, and AWS Bedrock (Anthropic + OpenAI variants) read PDFs as file parts out of the box. No setup beyond provider selection.
  3. 🖥️ Local OCR on Apple Silicon — oMLX bundles Microsoft Markitdown as a built-in PDF→Markdown backend. Enable Markitdown in oMLX, load Baidu Unlimited-OCR (3B / 570M-active, open-sourced 2026-06) as the vision model, point the plugin at oMLX as a Custom OpenAI-Compatible provider, turn on Force PDF Support, pick the multimodal model oMLX is serving. The PDF never leaves your machine.
  4. 🛠️ Third-party extractor (MinerU online UI) — use the MinerU Extractor online service for a quick manual UI when you don't want to wire up an API token. Download the converted .md, drop it in your vault outside the wiki folder, and ingest as a regular Markdown note.
  5. 🔌 Force PDF Support — for any other OpenAI/Anthropic-compatible endpoint that accepts file parts, the plugin attempts the call (Settings → LLM Configuration → Advanced). The endpoint decides; failures surface as a localized Notice.
  6. 🖼️ Embedded Markdown images — turn on Analyze embedded images during Markdown ingestion in Advanced settings to analyze every eligible local ![[image.png]] and ![alt](https://raw.githubusercontent.com/green-dalii/obsidian-llm-wiki/HEAD/image.png) embed. Each image is analyzed with its nearest Markdown paragraphs, sent in 20 MiB visual-evidence packages, and capped at 10 MiB; remote URLs are never downloaded. For testable per-image output, optionally enable Save embedded image visual evidence to source page to add a collapsible audit section to the generated source page.

Caveat for Office formats: Obsidian does not natively render .docx / .xlsx / .pptx (file-formats), so the practical workflow for Office files is: MinerU converts to .md, the plugin ingests that .md into wiki pages, and the original Office file is kept around for reference. Use a community plugin like Pandoc Plugin / Docxer / Md Importer / Office Reader if you need to inline-preview Office files.

Plumbing shared across all paths:

  • 🗄️ Bounded cache — .obsidian/plugins/karpathywiki/pdf-cache/ stores converted Markdown keyed by content hash + model + converter version; 100 MB total / 1000 entries / 10 MB single-entry caps with LRU-by-mtime eviction.
  • 📝 Optional vault sidecar — Settings → Wiki Configuration → Wiki Folder → Write PDF Markdown to Vault writes <basename>.pdf.md next to the source PDF (off by default — cache-only is the default).
  • 🛡️ Verbatim transcriber prompt — OCR-style conversion with [illegible] / [figure: ...] anti-hallucination markers; markdown-fence-wrapping from small local models is auto-cleaned before cache write.
  • 🔁 Source-page verbatim quotes (v1.27.0, #496) — every generated sources/<slug>.md page now carries a Mentions in Source section built from the same verbatim quotes the extraction captured per entity/concept (the prose the model already proved it could see), so the underlying document is the one wiki page with a real, grounded trail back to its source text.

📖 Full setup walkthroughs for all paths (cloud providers, oMLX hardware tiers, MinerU installation, cache housekeeping) → docs/PDF-OCR-GUIDE.md

💬 Query & maintenance

  • 🧭 5-stage PPR cascade — see How retrieval works. Personalized PageRank over [[wiki-link]] gives graph-aware multi-hop context.
  • 🆕 Body-aware lexical scoring (v1.29.0, #837) — the fast path scores title, aliases, summary and body text with BM25F, so the longest text on a page reaches the scorer. It is the single largest recall change the project has made.
  • 🆕 Related-page shaping (v1.29.0, #841) — one hub page can no longer drag every other page toward it. Related lists are recomputed on every write from the names that survived, ranked, and capped.
  • 🆕 Legacy query scorer switch (v1.29.0, #842) — Settings → Advanced → Legacy query scorer runs the previous hand-tuned linear ranking instead of the new one. Off by default; the new ranking is the default and the toggle is the way back.
  • 🆕 The answer budget is 16,000 tokens, and the pipeline says when it runs out (v1.29.0, #852) — the answer no longer stops silently at the budget.
  • 🆕 Citations read in academic form (v1.29.0, #857) — the composer grows with the content, and clear history clears the record.
  • 🪟 Right-docked side panel — Query Wiki opens in a Copilot-style right sidebar leaf (v1.22.1+) instead of a centered modal.
  • 🔍 Lint health scan — single command catches: duplicates, dead links, empty pages, orphans, missing aliases, contradictions.
  • ⚡ Smart Fix All — one-click causal-order repair: fill aliases → merge duplicates → fix dead links → link orphans → expand empty pages, with per-phase report.
  • 🆕 Fix Dead Links leave-it outcome (v1.27.0, #485) — Settings → Advanced → Create Stubs for Unresolvable Links (default ON) lets you opt out of empty placeholder pages: when off, the dead link stays visible in every lint report until a real source defines it, and ingest creates pages through normal channels. The never-LLM-expand gate from #197 is unchanged — the new control only governs whether the stub page is written at all.
  • 📊 Operation history panel — searchable, filterable UI for past ingestions, lint reports, and maintenance runs.
  • 🛡️ Pre-ingest gate — empty / whitespace / frontmatter-only notes are rejected before any LLM call; content-hash dedup catches identical files across paths.
  • 🆕 Ingest candidate gate (v1.27.0, #514 / PR #521) — opt-in toggle (skipMentionOnlyCandidates, default off, Settings → Advanced). For sources whose language has a measured profile (de measured; en/fr/es/pt/nl/ko estimated with pinned edge cases; zh/ja character-script thresholds unmeasured), candidates named only inside parentheses / enumerations / short list items are pruned before they cost a page plus dedup and generation calls. Cross-language notes are not gated; wiki languages without a profile report once per ingest and never silently skip.
  • 🆕 Per-step task policies (v1.27.0, #525 / #490) — LLM Advanced → Task Policies field; override the per-step text-mode/thinking setting without code changes. Built-in baseline stays intact for steps you don't list.

🦙 Local-first

  • 🖥️ Ollama, LM Studio, OpenRouter, custom endpoint — out-of-the-box. Local models work for query (smaller context windows); ingest on a 2,000-page vault usually needs a long-context cloud model.
  • 📄 PDF OCR path is fully local on Apple Silicon — see Document / PDF / Image ingest above.
  • 🔐 ChatGPT Plan (Codex OAuth) — desktop loopback or mobile device-code; credentials live only in Obsidian SecretStorage. (See Anthropic vs OpenAI vs Codex OAuth below for the full provider-boundary explanation.)

🌐 Language

  • 🌍 11 UI languages — English, 简体中文, 繁體中文, 日本語, 한국어, Deutsch, Français, Español, Português, Italiano, Русский. UI and wiki-output language are independent — your wiki can be Chinese while the interface is English.
  • 📚 11 wiki-output languages — same set; pick in Settings → Wiki Configuration. Custom input option for ad-hoc prompts.
  • All UI strings translated per locale — every label, modal, and notice. Adding a 12th language is contributor-driven (PR #159 pattern).
  • 🖼 Embedded image analysis during Markdown ingest — opt-in (Analyze embedded images during Markdown ingestion, off by default). Every eligible local ![[…]] / ![…](https://raw.githubusercontent.com/green-dalii/obsidian-llm-wiki/HEAD/…) embed in a note is resolved through Obsidian and analysed together with its neighbouring paragraphs, in 20 MiB packages; each image is capped at 10 MiB, GIFs send a static first frame, and remote URLs are never downloaded.
  • 🔧 Custom Headers per provider — a free-text field directly below the API Base URL. One Name: value per line, sent with every request. Ships with an OpenCode preset and a (Responses) variant for endpoints that speak /v1/responses.
  • 📡 A stream that survives a blocked origin — when a cross-origin request is refused, the stream is retried over a desktop node:https transport instead of degrading to a buffered answer, and a failed fallback is recorded rather than swallowed.

🌐 Ecosystem

The plugin composes with the rest of your Obsidian stack — each tool below plugs into the [[wiki-link]] graph without code changes.

  • 📄 MinerU multi-format backend (built-in since v1.27.0) — what used to be a separate CLI/UI step is now a plugin switch; see Document / PDF / Image ingest for the full path table. The MinerU online service remains available for users who prefer a quick UI over an API token; self-host MinerU is also an option.
  • 🕸️ Obsidian Graph View — open the native graph on any wiki page; every [[wiki-link]] becomes a node, every back-link an edge. Built in, zero extra bundle size.
  • ✂️ Obsidian Web Clipper — official browser extension. Save web pages (articles, blog posts, Reddit threads, Hacker News, recipes, research papers, YouTube transcripts via Interpreter) into any folder of your vault, then run the plugin's Ingest from folder command to batch-extract entities and concepts.
  • 📊 Dataview — query the wiki like a database with DQL (LIST FROM "wiki/entities" WHERE contains(tags, "person")) or JS API. The plugin writes standard frontmatter (tags:, type:, aliases:) on every page, so Dataview queries work out of the box.
  • 🌿 Git — version your vault (any Git client). The plugin never rewrites your source files; only creates new pages under wiki/, so git diff cleanly separates your edits from LLM-generated content.
  • 🎞️ Marp Slides — turn any Obsidian note into slide decks via Marp frontmatter (marp: true). Wiki pages are pure Markdown, so they render as slides without extra conversion.
  • 🖼️ Canvas — Obsidian's native infinite canvas. Drag wiki cards onto a Canvas to assemble study guides, mind maps, or research overviews from [[wiki-links]] without leaving the vault.
  • 🎤 Obsidian Nous — companion plugin for local voice memo and meeting capture (whisper.cpp on macOS; audio never leaves the machine). Generates speaker-labeled transcripts and its own wiki hub pages. Independent of this plugin — both can share the same vault without coupling.

🧰 Headless CLI

Most users should ignore this section. The plugin's user-facing CLI lives in the sibling repo green-dalii/obsidian-llm-wiki-cli — install with npm i -g karpathywiki-cli and run karpathywiki-cli ingest --sources <path> --wiki <path> --provider <id> --key <key>.

What ships in this repo at tools/dev-instrument/ is the dev-only headless measurement instrument for engine contributors — it runs the real WikiEngine.ingestSource against a vault on disk with no Obsidian runtime, prints per-task token + wall-clock accounting — same numbers that drive the perf evidence in CLAUDE.md and release notes. See tools/dev-instrument/README.md for the entry command, env vars, measurement modes, and exit-code spec.


🔍 How retrieval works

Most "AI search" plugins fragment your notes into chunks and embed them in a vector DB. We don't. Karpathy's argument against RAG is that chunking breaks the LLM's ability to reason across your whole knowledge graph — and that argument holds up in practice. Instead, we walk the graph you already maintain by writing [[wiki-links]].

The 5-stage seed-selection cascade

When you ask "Who founded Microsoft?", Query Wiki runs five stages before any answer generation:

  1. Lex fast path — BM25F over every entity/concept title, aliases, summary and body text, with per-field saturation and IDF over a real document-frequency table. Free, instant, and the gating step for everything that follows.
  2. LLM keyword generation — the LLM proposes 8–12 cross-language keywords from your query (handles synonyms, abbreviations, and token-overlap-resistant terms in one LLM call).
  3. Local substring scan — every generated keyword is re-matched locally against page titles, aliases, and body snippets. No extra LLM call; rounds out noise-tolerant recall.
  4. LLM KB fallback — when lex + keyword scan returns weak signals, the LLM re-seeds the top-N candidates against the full wiki for one semantic pass.
  5. PPR graph expansion — Personalized PageRank (Haveliwala 2002) over the [[wiki-link]] graph starting from the candidate seed set. This is what gives graph-aware multi-hop context: "Bill Gates" → "Microsoft" → "competitors", not just literal title overlap.

The cascade truncates at whichever stage returned enough signal — no fixed 5-stage cost; no LLM calls when lex is sufficient; semantic fallback only when lex + keyword scan alone isn't enough.

Query expansion, and a way back

When the cascade reaches the graph stage, the query is expanded twice before the seeds are chosen: once with the wiki's own terms, then again with LLM-proposed terms. Each pass is weighted, and the gain is measured on the project's own vaults rather than assumed — on the two vaults written by the current release the expansion is worth +0.086 and +0.113 at r@10, with the interval excluding zero in both cases. The claim is deliberately narrow: the weighted form is not measurably better than the simple concatenation, and the switch that runs the previous scorer is there for a reader whose results got worse.

Settings → Advanced → Legacy query scorer runs the previous hand-tuned linear scorer instead. The new ranking is the default; the toggle is the way back.

Personalized PageRank at scale

We use Monte Carlo PPR (Fogaras 2005) — 3,000 random walks × 50 steps each — with the dead-end rule from Haveliwala 2002. Cost is O(K × L) (K = walks, L = steps per walk), independent of the number of pages, so a 2,000-page vault sees the same expansion latency as a 200-page one.

PPR @5 = 27.1% vs pure-kNN baseline 24.1% on the project's own benchmark corpus (the only published retrieval benchmark in this open-source wiki-plugin space).

Why no embeddings

We deliberately rejected the embedding path in Issue #175. The graph signal is already there — every [[wiki-link]] is a hand-curated "these are related" edge, and most providers we support (Ollama, LM Studio, Anthropic, Bedrock, Kimi, GLM, MiniMax) don't ship a /v1/embeddings endpoint at all. Adding an embedding model would mean a per-page download, a per-provider adapter, and zero benefit on retrieval quality.


🤖 Models

Supported providers (16+, all from models.dev cross-check 2026-07):

Provider Series Notes
Anthropic Claude 5 series Native PDF; /v1/messages protocol
OpenAI GPT-5.6 series (Sol / Terra / Luna) Native PDF; Platform API key
Google Gemini Gemini 3.6 series Native PDF (file parts since 1.5); OpenAI-compatible endpoint
DeepSeek DeepSeek V4 series OpenAI-compatible; lowest cost tier
Alibaba Qwen Qwen3.7/3.8 series OpenAI-compatible (DashScope)
xAI Grok Grok 4 series OpenAI-compatible; long context
Moonshot Kimi Kimi K3 series OpenAI-compatible; 2.8T MoE frontier
Zhipu GLM GLM-5 series OpenAI-compatible; strong bilingual
MiniMax MiniMax M3 series OpenAI-compatible; 1M context
Step (阶跃星辰) Step 3 series (Flash) OpenAI-compatible; fast inference
Tencent Hunyuan Hy3 series OpenAI-compatible; open-weight MoE
Xiaomi MiMo MiMo V2.5 series MIT open-source; flat pricing
Google Gemma Gemma 4 series Open-weight; 262K context
AWS Bedrock Anthropic + OpenAI variants Native PDF; VPC / compliance path; API key + SSO + IAM (v1.27.0, #425)
ChatGPT Plan (Codex OAuth) Codex Responses API Browser/device-code sign-in; SecretStorage
Local: Ollama, LM Studio, OpenRouter, Anthropic-Compatible Any OpenAI-/Anthropic-protocol model Custom OpenAI-Compatible + Anthropic-Compatible (Token Plan / Coding Plan)

This plugin feeds the LLM your full Wiki context per query — so long-context models win. The full tiered table (cloud + local) lives in docs/MODEL-GUIDE.md, cross-checked against models.dev so the picks stay current.

What matters

  • 🧠 Context window ≥ 200K tokens for vaults over ~500 pages. Below 200K the cascade may drop earlier stages to fit.
  • ⚖️ Instruction-following quality matters more than raw IQ for the extraction task — pick a model that follows the schema template, not the biggest leaderboard number.
  • 🔌 Embedding endpoint is irrelevant — we don't use embeddings. A provider that lacks /v1/embeddings is fine (most of our 16+ providers don't ship one).
  • 🦙 Local works for query, cloud for ingest — ingest on a 2,000-page vault usually needs a long-context cloud model; a 262K local model covers most queries.

For PDF / image / Office ingest, see Document / PDF / Image ingest in Features — Anthropic, OpenAI, Bedrock, and Gemini read PDFs as file parts natively; the built-in MinerU backend (v1.27.0+) and Force PDF Support cover everything else.

Anthropic vs OpenAI vs Codex OAuth — they are distinct providers

  • Anthropic (and its Bedrock variant) — separately billed Anthropic Platform API key.
  • OpenAI — separately billed OpenAI Platform API key.
  • ChatGPT Plan (Codex OAuth) — experimental, distinct provider that uses eligible Codex allowance after browser or device-code sign-in; availability follows OpenAI Codex authentication and allowance policies, not plan name. Third-party Codex compatibility, not an OpenAI partnership or a general ChatGPT API.

AWS Bedrock — three auth modes (v1.27.0, #425)

Settings → Provider → Bedrock (Anthropic / OpenAI) now picks one of three auth modes; the provider row then asks for the inputs that mode actually needs:

  • API key — the original Stage-1 bearer path; behavior is byte-for-byte identical to v1.26.4 and the recommended pick for users who already pay for a Bedrock API key.
  • SSO — IAM Identity Center device flow. Click Sign in with AWS SSO, paste the verification URL code in the browser, the plugin receives an SSO token via karpathywiki-bedrock-sso in SecretStorage, exchanges it for temporary role credentials, and signs every request with hand-rolled SigV4 (no AWS SDK added). Account ID and role name are auto-detected when the SSO identity exposes exactly one of each; otherwise enter them in the provider settings.
  • IAM — static access keys for environments without SSO (CI, scheduled batch jobs). Stored in karpathywiki-bedrock-iam in SecretStorage; the in-memory cache memoizes per access-key to keep SigV4 signing within expiry.

All three modes share the same Obsidian SecretStorage discipline (no credentials in data.json, logs, or docs) and the same zero-AWS-SDK hand-rolled OIDC + SigV4 path. Bedrock region is independent of auth mode and is configured in the same provider row.

📖 Full pick table (cloud + local + PDF OCR + Codex OAuth + quantization + hardware tiers) → docs/MODEL-GUIDE.md

❓ FAQ

What does the plugin actually do?

Pick any note, folder, or selection; the LLM extracts entities and concepts and generates an interlinked wiki with [[bidirectional links]]. Ask questions and get conversational answers grounded in your notes, not the internet. Your original vault notes are never modified.

How do I get started?

Install from Obsidian Community Plugins → pick a provider → Test Connection → run Ingest single source on any note. First wiki pages appear within seconds. See Quick Start.

Is my existing wiki safe?

✅ Backward compatible since v1.0.0. Set reviewed: true on any page to protect it from overwrite. Upgrading from v1.24.x doesn't rewrite your vault; v1.25.0's PDF ingest is cache-only by default, and v1.27.0 adds native PDF + images + Office ingest without changing the on-disk wiki layout.

Can I ingest PDFs, images, and Office documents?

✅ Yes. Anthropic, OpenAI, Bedrock, and Gemini read PDFs natively; the built-in MinerU backend (v1.27.0) covers everything else (PDF + images + Office). Full walkthrough — cloud providers, Apple Silicon OCR, Force PDF Support, cache housekeeping — in docs/PDF-OCR-GUIDE.md.

Is my data sent anywhere?

🚫 No backend, no analytics — the plugin runs entirely inside Obsidian. Only text you explicitly send for ingest/query leaves your device, and only to the LLM provider you configure. For complete data locality, use Ollama or LM Studio.

Can I use the plugin in my language?

🌍 11 languages for both UI and wiki output. UI and wiki language are independent. Adding a 12th language is contributor-driven (PR #159 pattern).

How is this different from a RAG chatbot?

🚫 No chunking. 🚫 No embeddings. 🚫 No vector DB. ✅ Personalized PageRank over your existing [[wiki-link]] graph — graph-aware multi-hop context, zero embedding cost, full local-model support.

Which LLM should I use?

Long-context models (≥200K tokens) work best. The Models section covers the principles; the full tiered table is in docs/MODEL-GUIDE.md.

Is there a published benchmark?

Yes — PPR @5 = 27.1% vs pure-kNN baseline 24.1% on the project's own corpus. The full pipeline and benchmark script are described in How retrieval works.

How do I control API costs?

Use Coarse or Minimal extraction granularity for batch ingest. Smart Batch Skip auto-detects already-ingested files. Auto-Maintenance is OFF by default. Lint shows counts before running fixes — nothing is charged without your approval.

How do I cancel a running operation?

Click the status bar (shows "Ingesting… click to cancel") or Cmd+P/Ctrl+P → "Cancel current ingestion". Stops cleanly at the next batch boundary.

Where do I get help?

GitHub Issues for bug reports · GitHub Discussions for questions and feature requests · Developer Console (Ctrl+Shift+I / Cmd+Option+I) for plugin logs.


🔒 Privacy

This plugin is listed on the Obsidian Community Plugin Market and undergoes automated review for security and permissions.

  • 🚫 No backend of its own, no telemetry, no data collection. Pure local software running inside Obsidian. The plugin operates no server and reports nothing anywhere.
  • 🔐 Network access is opt-in and explicit. It exists only to reach services you configure: your LLM provider, and — if you turn on the MinerU document backend — mineru.net. That second one is the exception worth naming: it uploads the document to a jurisdiction you did not choose and that publishes no retention statement. Where your document is processed lists every path and where the file goes.
  • 📁 Vault file access is used for wiki management (reading notes, generating pages, scanning dead links, detecting duplicates). The plugin never modifies your source files.
  • 📋 Clipboard access is used exclusively by the "Copy" button in the Query modal — and only when you click it.

For complete data locality, use Ollama or LM Studio. With a local provider, your data never leaves your machine.


💖 Support

If Karpathy LLM Wiki has become a meaningful part of your knowledge workflow:

Thanks to the following for supporting the project:

@jameses-cyber, @issaqua, Dikson Choi


🔭 Other projects

  • obsidian-llm-wiki-cli — the headless ingest CLI, sibling repo shipped as the karpathywiki-cli npm package. Runs the same WikiEngine against a vault on disk, no renderer. Install with npm i -g karpathywiki-cli. The in-tree tools/dev-instrument/ is the dev-only measurement instrument that drives the per-task cost numbers in this plugin's release notes.
  • pi-shift-router — a task-level router for pi-coding-agent. Before each turn a small LLM judge marks your message routine or consequential, and the tier it picks drives the whole turn. Complex tasks go further: the Smart tier runs as a CTO that plans the work, delegates implementation to Fast subagents, reviews each result and iterates. Upgrades are instant, downgrades wait for a sustained trend; per-tier fallback chains ride out 429s and 5xx. Zero runtime deps, MIT. → shiftrouter.greenerai.top
  • dsh-shift-router — DSH fork of pi-shift-router, same task-level routing design but targeted at the dsh-coding-agent runtime. Same judge-driven tier picks, same per-tier fallback chains, MIT.
  • dsh-plugin-dev-skill — DSH companion to the Claude-side obsidian-plugin-dev workflow: scaffolds an Obsidian plugin workspace, drives the Red→Green TDD loop, runs the Six-Gate quality closure (lint/tsc/test/build/css-lint), and prepares a release-ready branch on feat/* or fix/*. Built so DSH-using contributors get the same scaffolding + gate experience without copy-pasting from CLAUDE.md.

📜 License & Credits

Apache License, Version 2.0 — see LICENSE, NOTICE and THIRD-PARTY-NOTICES.md.

Built on:

Maintainers: @green-dalii (author) · @DocTpoint (co-maintainer since September 2026)

Star History Chart

Similar Plugins

info
• Similar plugins are suggested based on the common tags between the plugins.
Note aliases
4 years ago by Pulsovi
This plugin manages wikilinks aliases and save them on the aliases list of the linked note
GPT Assistant
4 years ago by M7mdisk
Ask GPT from your notes and get personalized answers based on your knowledge base.
Link Range
4 years ago by Ryan Mellmer
Add ranged link support to Obsidian
Links
4 years ago by MiiKey
manipulate & manage obisidian links
Semantic Canvas
3 years ago by Aaron Gillespie
An Obsidian Plugin to update note properties using links on Canvases
Nextcloud Link Fixer
2 years ago by KaelLarkin
Add links to current note
6 years ago by MrJackphil
This plugin adds a command which allows to add a link to the current note at the bottom of selected notes
Wikilinks to MDLinks
6 years ago by Agatha Uy
An Obsidian md plugin which allows for the conversion of individually selected wikilinks to markdown links, and vice versa.
Page Heading From Links
6 years ago by Mark Beattie
Obsidian plugin to populate page headings
InfraNodus AI Graph View
2 years ago by Nodus Labs
Advanced graph view for Obsidian: text analysis, topic modeling, and AI with InfraNodus AI text analysis tool: https://infranodus.com
Insta TOC
2 years ago by Nick C.
Generate, update, and maintain a table of contents for your notes while typing in real time.
ExMemo Tools
2 years ago by Yan.Xie
Use large models for smart document management and optimization, including relocating files, enhancing text, and generating metadata.
Automatic Linker
2 years ago by Kodai Nakamura
Title As Link Text
2 years ago by Lex Toumbourou
An Obsidian plugin to set the Link Text using the document title
Related Notes
2 years ago by Oluwasanya Awe
Date Range Expander
2 years ago by Mil
Obsidian plugin - Date Range Expander
Notemd
a year ago by Jacob
A Easy way to create your own Knowledge-base! Notemd enhances your Obsidian workflow by integrating with various Large Language Models (LLMs) to process your notes, automatically generate wiki-links for key concepts, create corresponding concept notes, perform web research, and more.
Folder Filelist
a year ago by Bill Anderson
Obsidian plugin for simple folder listing
EasyLink
a year ago by isitwho
Select text in your obsidian editor to find the most similar content from other notes and easily create links.
Private AI
a year ago by GB
Effortlessly chat with your Obsidian notes using a privacy first LLM. Private by design, your notes never leave the device and use local processing only.
Auto Keyword Linker
10 months ago by Daniel Rhodes
Stop manually typing [[brackets]] around recurring terms. Configure keywords with variations once, and automatically link them as you write or across your entire vault.
YOLO
10 months ago by Lapis0x0
Agent-native AI assistant — chat, write, whiteboard, learning, all in one.
Connections
10 months ago by Eric Van Cleve
Smart Lookup
6 months ago by brianpetro
Neural Composer
4 months ago by Oscar Campo
AI-Powered Graph Memory for Obsidian
Sidet
4 months ago by Jiao Yingxing
流畅自然的 AI 对话体验,移动端也出色。A smooth, natural AI chat experience that also works great on mobile.
Mention Autocomplete
4 months ago by Darren Zheng
Type `@` to instantly search and link any note in your vault — with full-text search, rendered preview, and smart sentence extraction.
Discourse Graph
3 months ago by discoursegraphs
Note Types
3 months ago by jsmorabito
Dedao Brain Importer
3 months ago by springrain | 公众号: 及时春雨
在原版基础上修复windows无法手动和自动导入问题,以及优化很多格式转换为markdown
ICOR for Life - Connect
2 months ago by Paperless Movement S.L.
Your app.myicor.com account inside your vault: ICOR Journey and Growth Assignment dashboards, knowledge-base search, reflections synced as notes you own, and myICOR context for Claude sessions. Part of the ICOR for Life suite.
Antigravity
2 months ago by ke yongcheng
Autonomous vault management, knowledge organization, and agentic intelligence powered by Google Antigravity (agy).
Mermaid Link Navigator
2 months ago by w-java123
Ontomark
a month ago by DreamLab AI
Offline ontology reasoning, SPARQL and reviewed frontmatter edits for Obsidian