Show HN: 10x better performance from the Coding Harnesses with LLM-wiki

LLM-compiled knowledge bases forany AI agent with awesome outputs. Parallel multi-agent research. Thesis-driven investigation. Source ingestion. Wiki compilation. Session memory. Feedback curation. Topic archiving. Inventory tracking. Dataset manifests. Truth-seeking audits. Querying. Artifact generation. Ships as a Claude Code plugin, an OpenAI Codex plugin, an OpenCode instruction file, or a portable AGENTS.md. Obsidian-compatible. Every run compounds. Sources become cross-referenced articles. Articles become reports, slide decks, study guides, playbooks, and implementation plans. Session digests keep the agent oriented without turning private chats into topic evidence. What it does One command spins up a topic wiki, dispatches up to ten agents, ingests what's worth keeping, collects provenance-rich catalogs before tracking them, archives old topics without deleting them, tracks durable follow-up state, indexes large datasets without copying them, captures redacted session context and feedback candidates without hoarding transcripts, compiles sources into articles, and hands you a deliverable built on top. All plain Markdown you own. Research 5–10 parallel agents search academic, technical, applied, news, and contrarian angles. --min-time 2h keeps going in rounds, drilling into gaps each round finds. Thesis mode Start from a claim. Agents split across supporting, opposing, mechanistic, meta, and adjacent angles. Output is a verdict — not a summary. Round two fights confirmation bias. Ingest URLs, files, PDFs, inbox drops, Git doc repos, MediaWiki dumps, message archives, and Wayback CDX snapshots. Raw sources stay immutable; articles synthesize on top. Collect Find, dedupe, download bounded public media, and catalog discoverable artifacts, examples, memes, tools, entities, and source candidates. Captures aliases, found-in-context provenance, local asset paths, hashes, scale, media policy, and inventory fit. Inventory Track durable things the wiki should remember: items, source candidates, corpora, entities, open questions, watch items, and next actions. Chat views default to compact tables. Datasets Index large, external, mutable, or operational data with manifests, samples, profiles, and query recipes. The wiki becomes the interface; the data stays where it belongs. Archive Move whole topic wikis to topics/.archive/. Preserved knowledge stays structurally maintainable but out of default query, compile, research, collect, output, and maintenance context. Compile Raw sources become synthesized articles with cross-references and confidence scores. Every directory has an _index.md — nothing is scanned blindly. Query Quick (indexes), standard (articles), or deep (everything + sibling wikis). --resume picks up where you left off. Sessions Default-on hook capture writes redacted events, state JSON, and Markdown digests under.sessions/. Rehydrate future turns with compact context; promote only what belongs in a topic. Feedback Curates high-signal corrections, preferences, approvals, and plan acceptance under.sessions/feedback/. Generic acknowledgements are ignored; durable lessons are explicitly promoted. Librarian Score every article for staleness and quality. Two-tier scan: fast metadata check, then deep content read for flagged articles. Checkpoint recovery. Machine-readable JSON + human-readable report. Audit Answer the broader trust question. Reuse the librarian pass, trace outputs across raw/, wiki/, and output/, detect drift, inspect provenance, and do fresh research when local evidence is not enough. Lessons Extract lessons learned from the current session — error→fix patterns, user corrections, discoveries. Saved as structured notes the wiki can query later. --rules emits enforceable rules instead of prose. Plan Wiki-grounded implementation plans. Reads the knowledge base, interviews you about requirements, fills gaps with targeted research, and produces a phased plan citing wiki articles as evidence. --format rfc|adr|spec. Output Reports, slide decks, study guides, playbooks, implementation plans, timelines, glossaries, comparisons. Filed back into the wiki so the next output builds on every previous one. Install Claude Code Native plugin. Recommended. claude plugin install wiki@llm-wiki Installs from the public marketplace. Restart Claude Code to apply. OpenAI Codex Marketplace plugin. Invoke with @wiki. codex plugin marketplace add nvk/llm-wiki # Then open /plugins, enable "LLM Wiki", use @wiki Or from a local checkout:./scripts/bootstrap-codex-plugin.sh --scope user --verify. The Codex tree is a generated mirror of the Claude source of truth — updates land identically. OpenCode Instruction file. # In opencode.json: { "instructions": [ "path/to/llm-wiki/plugins/llm-wiki-opencode/skills/wiki-manager/SKILL.md" ] } Or copy to ~/.config/opencode/AGENTS.md. Web search requires =1. Pi Instruction file. Best for local models. pi --instructions path/to/llm-wiki/plugins/\ llm-wiki-opencode/skills/wiki-manager/SKILL.md Pi's 1K system prompt leaves room for the full wiki skill on 32K context local models. Uses the same skill file as OpenCode. Any LLM agent Portable AGENTS.md. curl -sL https://raw.githubusercontent.com/nvk/llm-wiki/master/AGENTS.md \ > ~/your-project/AGENTS.md Drop the file into any agent's context or project root. Works with anything that can read/write files and search the web. Upgrading an existing install Claude Code: claude plugin update wiki@llm-wiki # Restart Claude Code to apply If the update command misses a new version (stale marketplace cache), sync manually: git clone https://github.com/nvk/llm-wiki.git # or: git -C ~/llm-wiki pull REPO=~/llm-wiki/claude-plugin DEST=~/.claude/plugins/cache/llm-wiki/wiki VERSION=$(grep '"version"' "$REPO/.claude-plugin/plugin.json" | grep -o '[0-9.]*') rm -rf "$DEST"/* mkdir -p "$DEST/$VERSION" cp -R "$REPO/.claude-plugin" "$REPO/commands" "$REPO/skills" "$DEST/$VERSION/" Codex: codex plugin marketplace upgrade llm-wiki. For a local checkout: re-run./scripts/bootstrap-codex-plugin.sh --scope user --verify. AGENTS.md: re-run the curl command above to replace the file. Quick start One command, from anywhere — creates a topic wiki, launches parallel agents, keeps researching for an hour, comes back compiled. /wiki:research "gut microbiome" --new-topic --min-time 1h More common flows: /wiki:research "nutrition" --new-topic /wiki:research "fasting" --deep --min-time 2h /wiki:research "What makes articles go viral?" --new-topic /wiki:research --mode thesis "fiber reduces neuroinflammation via SCFAs" /wiki:query "How does fiber affect mood?" /wiki:query --resume /wiki add https://example.com/article # fuzzy router → ingest /wiki what do we know about CRISPR? # fuzzy router → query /wiki:ingest-collection https://github.com/bitcoin/bips --wiki bitcoin /wiki:collect "bitcoin memes" --wiki bitcoin /wiki:collect "bitcoin memes" --scale medium --media reference --inventory corpus /wiki:inventory add item "TRX-4M ring and pinion" --wiki trx4m-1-18 /wiki:inventory list --view actions --limit 10 /wiki:dataset add "Bitcointalk Temporal Graph" --location https://figshare.com/articles/dataset/BitcoinTemporalGraph/26305093 /wiki:dataset list --view schema --limit 10 /wiki:archive topic old-interest --reason "No longer active" /wiki:archive list --archived /wiki:archive restore old-interest /wiki:session status /wiki:session rehydrate --cwd "$PWD" /wiki:feedback list --unpromoted /wiki:session disable # optional opt-out /wiki:compile /wiki:output report --topic gut-brain /wiki:assess /path/to/my-app --wiki nutrition /wiki:lint --fix Session memory without transcript hoarding Long agent runs lose useful context when chats compact, terminals close, or work moves from Claude to Codex. LLM Wiki now has a hidden operational layer for that: redacted checkpoints, compact digests, and user-feedback candidates under HUB/.sessions/. It helps the next turn get oriented without treating private chat logs as curated wiki knowledge. Default-on, easy opt-out Trusted hooks capture in balanced mode by default. /wiki:session disable writes enabled: false so those hooks become no-ops. Redacted by design Capture stores metadata, state, small events, and distilled Markdown digests. Full transcripts are not stored by default. Rehydrate future work /wiki:session rehydrate returns a compact context block pointing the agent to relevant digests for the current directory, topic, or session ID. Promotion stays explicit Session digests and feedback candidates remain operational memory until promote writes a distilled note into a topic's raw/notes/. What gets stored HUB/.sessions/ ├── config.json # enabled/mode/privacy/rehydrate settings ├── registry.jsonl # append-only lifecycle events ├── queue/YYYY-MM-DD.jsonl # small redacted hook events ├── state/ /.json # latest per-session machine state ├── digests/YYYY/MM/ -.md ├── feedback/ │ ├── candidates.jsonl # corrections, preferences, approvals, plan acceptance │ └── status.json └── indexes/ # derived caches for cwd/topic/session lookups Common session commands /wiki:session status /wiki:session rehydrate --cwd "$PWD" /wiki:session list --limit 10 /wiki:session show codex:abc123 /wiki:session promote codex:abc123 --topic meta-llm-wiki /wiki:feedback list --unpromoted /wiki:feedback show fb-abc123 /wiki:feedback promote fb-abc123 --topic meta-llm-wiki /wiki:session disable # opt out /wiki:session enable # turn capture back on The same.sessions/ layout works across Codex, Claude Code, OpenCode, Gemini-style adapters, and local.wiki/ project wikis. How it works 1ResearchParallel agents search the web, ingest sources, and compile articles in one command. 2IngestURLs, files, PDFs, inbox drops, repos, dumps, archives, or snapshots. 3CollectCatalog many discoverable things first, then decide what deserves inventory, raw ingestion, or dataset indexing. 4CompileRaw sources become synthesized wiki articles with cross-references and confidence scores. 5TrackInventory records and dataset manifests preserve next actions without polluting source evidence. 6ArchiveQuiet old topic wikis without deleting their sources, articles, outputs, or logs. 7QueryQuick (indexes), standard (articles), deep (active content plus archived index hints). 8CaptureSession hooks keep redacted checkpoints under.sessions/; no full transcripts by default. 9RehydrateFuture turns can receive a compact digest list instead of rereading the whole chat. 10FeedbackReview high-signal user-feedback candidates and promote only durable lessons. 11LintBroken links, missing indexes, orphan articles, archive registry drift. --fix auto-repairs safe issues. 12OutputSummaries, reports, slides, plans — filed back into the wiki. Architecture ~/wiki/ # Hub — lightweight, no content ├── wikis.json # Registry of all topic wikis ├── _index.md # Lists topic wikis with stats ├── log.md # Global activity log ├──.sessions/ # Operational session memory, digests + feedback └── topics/ # Each topic is an isolated wiki ├── nutrition/ │ ├──.obsidian/ # Obsidian vault config │ ├── inbox/ # Drop zone for this topic │ ├── inventory/ # Items, candidates, corpora, views │ ├── datasets/ # Manifests for large/external data │ ├── raw/ # Immutable sources │ ├── wiki/ # Compiled articles │ │ ├── concepts/ │ │ ├── topics/ │ │ └── references/ │ ├── output/ # Generated artifacts │ ├── _index.md │ ├── config.md │ └── log.md ├── woodworking/ # Another topic wiki └──.archive/ # Archived topic wikis, hidden by default One topic, one wiki Each research area is isolated. No cross-topic noise. Queries stay focused. A multi-wiki peek finds overlap when relevant. Dual-linking [[wikilinks]] for Obsidian plus standard markdown links for everything else. Works in every viewer — including no viewer at all. Raw is immutable Once a source is ingested it is never modified. Articles synthesize on top. Retraction removes both cleanly. Collector catalogs /wiki:collect records aliases, source context, media URLs, cached asset paths, hashes, dedupe notes, scale, and inventory recommendations before anything becomes evidence or durable state. Inventory is state Parts, source queues, corpora, watch items, and next actions live under inventory/ so they can be listed and revisited without becoming evidence. Datasets stay external datasets/ stores manifests, samples, profiles, and query recipes for large data. The wiki indexes data without copying it into the source corpus. Archive is quiet Archived topics live under topics/.archive/. Most tools skip them by default; deep queries may surface index hits, and explicit --include-archived can read them. Sessions are operational memory.sessions/ is hidden, cross-topic operational state for redacted checkpoints, digests, rehydration indexes, and feedback candidates. Topic promotion is explicit. Zero dependencies Runs entirely on the host agent's built-in tools. Plugin is Markdown + commands. No servers, no services, no telemetry. Commands All commands accept --wiki to target a topic wiki and --local for the project wiki. Archived topic wikis are skipped by default; commands that support --include-archived require that explicit flag before reading or writing archived material. query, output, and plan also accept --with for cross-wiki context. CommandDescription /wiki Fuzzy intent router — say what you want, it routes to the right subcommand. /wikiShow status, stats, and list all topic wikis. /wiki init Create a topic wiki at ~/wiki/topics/ /. /wiki:ingest Ingest a URL, file path, or quoted text. /wiki:ingest --inboxProcess files dropped into the topic wiki's inbox. /wiki:ingest-collection Bulk-ingest Git doc repos, BIP-style proposal sets, MediaWiki dumps/API sites, message archives, or Wayback CDX snapshots. /wiki:collect " "Find, dedupe, and catalog artifacts, examples, resources, media, memes, tools, entities, or source candidates. /wiki:collect " " --scale tiny|small|medium|large|hugeControl write behavior by operational scale: row count, media weight, provenance burden, volatility, and inventory usefulness. /wiki:collect " " --media archive|thumbnail|referenceDownload bounded originals by default for media-bearing collections; use thumbnails for previews or reference to opt out. /wiki:collect " " --inventory corpus|recordsCreate one corpus record for medium or media-heavy sets, or per-item records only for small durable lists. /wiki:inventory listList durable tracking records as compact chat tables or bullets. /wiki:inventory add "title"Add items, source candidates, entities, corpora, questions, tasks, or watch records after a fit check. /wiki:inventory scan-outputs --dry-runPreview legacy queues/backlogs before an additive inventory migration. /wiki:dataset listList dataset manifests without opening samples, profiles, queries, or underlying data. /wiki:dataset add "title" --location Index large or external data with a manifest; the data stays outside the wiki. /wiki:dataset profile --dry-runPreview lightweight profiling of size, format, headers, or schema observations. /wiki:archive list [--archived]List active topic wikis and optionally archived topic wikis. /wiki:archive topic --reason "why"Move a topic wiki to topics/.archive/ and hide it from default context. /wiki:archive restore Restore an archived topic wiki to active status. /wiki:archive peek Search archived topic indexes without reading archived article bodies. /wiki:session status|disable|enableInspect, opt out of, or reconfigure default-on redacted session capture. /wiki:session capture|list|showCreate, browse, and inspect redacted session digests kept outside topic evidence. /wiki:session rehydrate|promoteLoad compact session context or explicitly promote a distilled digest into topic raw notes. /wiki:feedback list|showReview redacted feedback candidates for corrections, preferences, approvals, and plan acceptance. /wiki:feedback capture|promoteManually add a feedback candidate or explicitly promote one into topic raw notes. /wiki:compileCompile new sources into wiki articles. /wiki:query Q&A against the wiki. --quick / --deep / --list / --resume / --include-archived. /wiki:llExtract lessons from current session into wiki. --dry-run, --rules. /wiki:research 5 parallel agents. --plan (multi-path), --deep (8), --retardmax (10), --new-topic, --min-time 1h. /wiki:research --mode thesis Thesis-driven research: for + against → verdict. /wiki:plan Wiki-grounded implementation plan. --format rfc|adr|spec. /wiki:output summary, report, study-guide, slides, timeline, glossary, comparison. /wiki:assess Assess a repo against wiki + market. Gap analysis. /wiki:auditTruth-seeking audit across wiki, outputs, provenance, and fresh research when needed. /wiki:librarianScore articles for staleness and quality. Checkpoint recovery. --article for single article. /wiki:lintHealth checks. --fix auto-repairs. --deep web-verifies facts. /wiki:retractRemove a source and clean up downstream references. /wiki:projectGroup outputs into projects with goals and manifests. Guides From zero to a compiled wiki in 5 minutes. Quick Start — Your first wiki in 5 minutes 1. Install the plugin claude plugin install wiki@llm-wiki 2. Create a topic wiki Pick any topic you're curious about: /wiki init nutrition This creates a hub at ~/wiki/ and your first topic wiki at ~/wiki/topics/nutrition/. 3. Research it /wiki:research "gut microbiome and mental health" --wiki nutrition # or just say it naturally: /wiki research gut microbiome and mental health Five parallel agents search the web from different angles (academic, technical, applied, news, contrarian), ingest the best sources, and compile them into cross-referenced wiki articles. Takes 2-5 minutes. 4. Ask your wiki a question /wiki:query "how does fiber affect mood?" --wiki nutrition # or naturally: /wiki how does fiber affect mood? The wiki answers from its compiled articles with citations. 5. Audit before you trust an output /wiki:audit --wiki nutrition /wiki:audit --artifact output/report-gut-brain.md Audit rechecks the wiki layer, traces the output's evidence chain, flags drift, and will do fresh research if the local corpus is not enough to answer the trust question. What to do next: /wiki:research "topic" --deep — 8 agents instead of 5, adds historical and data angles /wiki:research "topic" --min-time 1h — keep researching in rounds for an hour /wiki:research "topic" --plan — decompose into parallel research paths /wiki:audit --project nutrition-playbook — verify outputs and upstream wiki state together /wiki add https://example.com/article — fuzzy router detects the URL and ingests it /wiki what do we know about CRISPR? — fuzzy router detects the question and queries /wiki:lint --fix — clean up any structural issues Research workflow — From question to compiled knowledge A typical research session flows through four stages: Stage 1: Ask a question or pick a topic llm-wiki auto-detects whether you're asking a question or naming a topic. Use the direct command or the fuzzy router: /wiki:research "What makes long-form articles go viral?" # direct command /wiki research quantum computing # fuzzy router — same result /wiki:research --mode thesis "fiber reduces neuroinflammation via SCFAs" # thesis → for/against evidence Stage 2: Agents search in parallel 5 agents (8 with --deep, 10 with --retardmax) search simultaneously from different angles — 2-3 web searches each, full-content fetch, quality scoring (1-5). A credibility pass deduplicates before ingestion. Stage 3: Sources are ingested and compiled Top sources are saved to raw/ (immutable — never modified after ingestion). Then the compilation pass synthesizes them into wiki articles under wiki/concepts/, wiki/topics/, and wiki/references/ with cross-references, confidence scores, and bidirectional links. Stage 4: Gap report and follow-up After each round, you see what's covered, what's still missing, and suggested follow-ups. If 2+ gaps remain, you're offered to close them in parallel: ### Close gaps? 1. Dose-response curves for wavelength specificity 2. Long-term safety data for daily exposure 3. Device comparison (clinical vs consumer panels) Enter numbers (e.g. 1,2,4), "all", or "skip": Multi-round research: Add --min-time 2h to keep researching in rounds, each drilling into gaps the previous round found. Add --plan to decompose into parallel paths upfront. How the wiki works — Hub, topics, sources, and articles The hub (~/wiki/) is just a registry. No content — only wikis.json, _index.md, and log.md. All content lives in topic sub-wikis. Topic wikis (~/wiki/topics/ /) are isolated research areas. Each has its own sources, articles, outputs, and Obsidian vault config. Isolation means researching quantum computing can't pollute your nutrition wiki. Raw sources (raw/) are immutable. Once a paper, article, or data file is ingested, it's never modified. This is the audit trail — every claim in every article traces back to a source. Wiki articles (wiki/) are LLM-compiled syntheses organized into three categories: Concepts — foundational ideas, mechanisms, theories Topics — specific subjects, comparisons, state-of-the-field References — tools, frameworks, data tables, lookup resources Archive (topics/.archive/) is for whole topic wikis the user no longer wants in normal context. It preserves source history, articles, outputs, and logs while keeping old interests quiet by default. Sessions (HUB/.sessions/) are operational memory for redacted harness checkpoints, compact digests, rehydration indexes, and feedback candidates. They are not compiled as topic evidence unless explicitly promoted into raw/notes/. Inventory (inventory/) is for durable operational state: actual items, source candidates, corpora, entities, open questions, tasks, watch items, and next actions. It is intentionally not evidence for factual claims. Dataset manifests (datasets/) let the wiki index large or external data without copying it into raw/. Manifests can point to local paths, URLs, archives, samples, profiles, and query recipes. Articles use dual-link format: [[wikilink]] for Obsidian + standard markdown links for everything else. Confidence scores (high/medium/low) reflect source quality and corroboration. Indexes (_index.md) exist in every directory. They're derived caches — rebuilt automatically from file frontmatter. The agent reads indexes first and never scans blindly. Outputs (output/) are generated artifacts: reports, slide outlines, study guides, implementation plans. They're built from wiki articles, so every output compounds on all prior research. Audit walks that full artifact graph. It can trace an output back through the wiki state and raw sources it depended on, then escalate into fresh research when the stored evidence is stale or incomplete. Session capture — Context without transcript hoarding Session capture is default-on operational memory. Trusted Codex, Claude, OpenCode, and Gemini hooks write redacted checkpoints into HUB/.sessions/ or a local.wiki/.sessions/. The topic wiki stays clean until you promote something. What is captured: harness name, session ID, current directory, git branch/remote, small redacted hook events, per-session state JSON, markdown digests, and feedback candidates. Full transcripts are off by default. HUB/.sessions/ ├── config.json ├── registry.jsonl ├── queue/YYYY-MM-DD.jsonl ├── state/ /.json ├── digests/YYYY/MM/ -.md ├── feedback/candidates.jsonl └── indexes/ Daily commands: /wiki:session status /wiki:session rehydrate --cwd "$PWD" /wiki:session list --limit 10 /wiki:session show codex:abc123 /wiki:feedback list --unpromoted /wiki:feedback promote fb-abc123 --topic meta-llm-wiki Opt out: /wiki:session disable writes enabled: false in.sessions/config.json, so trusted hooks become no-ops. /wiki:session enable turns it back on. Promotion rule: session digests and feedback candidates are useful for continuity, but they become topic knowledge only after /wiki:session promote or /wiki:feedback promote writes a distilled note under raw/notes/. DS4 wiki profile — Native local wiki agent Use native ds4-agent for DS4 wiki work, not a bare chat profile. LLM Wiki needs a real tool loop for targeted reads, writes, edits, shell checks, and index-first navigation. Profile rule: keep ds4c-wiki as an opt-in side command. Load the LLM Wiki instruction file into -sys, launch with --chdir "$PWD", and keep your model, checkout, and hub paths in environment variables. export DS4_REPO="$HOME/src/ds4" export DS4_MODEL="$HOME/models/deepseek-v4-flash-q2.gguf" export LLM_WIKI_REPO="$HOME/agent-workspace/llm-wiki" export WIKI_INSTRUCTIONS="$LLM_WIKI_REPO/plugins/llm-wiki-opencode/skills/wiki-manager/SKILL.md" # Run from the project or fixture you want ds4-agent to edit. ="$PWD" ="$(printf '%s\n' \ 'You are ds4c-wiki, a native ds4-agent profile for LLM Wiki workflows.' \ 'Resolve the hub, read indexes first, choose a topic, then use targeted reads/searches.' \ 'Do not broad-scan home directories, unrelated source trees, or dependency folders.' \ 'Keep.sessions operational until the user explicitly promotes a digest or feedback candidate.'; \ cat "$WIKI_INSTRUCTIONS")" "$DS4_REPO/ds4-agent" \ -m "$DS4_MODEL" \ -c "${DS4_CTX:-100000}" \ --chdir "$ " \ --nothink \ -sys "$ " \ --non-interactive \ -p 'wiki status: tell me which hub or local.wiki you would use, then stop' Public examples rule: use placeholders like ~/src/ds4, ~/models/model.gguf, ~/agent-workspace/llm-wiki, and ~/wiki. Before sharing snippets, redact local usernames, hostnames, LAN or VPN IPs, SSH fingerprints, tokens, raw traces, and full.sessions/ content. First real test: run a disposable local wiki fixture before pointing DS4 at your real hub. tmp="$(mktemp -d)" cd "$tmp" git init cat > AGENTS.md " starts from a specific claim and uses it as a filter. Agents are split across supporting, opposing, mechanistic, meta/review, and adjacent — balanced by design. Sources that don't relate to the claim's variables are skipped, which keeps the wiki tight. Output is a verdict: supported, partially supported, contradicted, insufficient evidence, or mixed. With --min-time, round two focuses harder on the weaker side of the evidence — counter-weight against confirmation bias. Is it free and open source? Yes. LLM Wiki is MIT-licensed. Source and releases at github.com/nvk/llm-wiki. Does it work offline? Compiling, querying, linting, and generating artifacts from an existing wiki work offline — everything is plain Markdown on your disk. Research and ingestion need internet since they fetch URLs and search the web. What dependencies does it have? Zero runtime dependencies. LLM Wiki uses only the built-in tools of the host agent (file read/write, web fetch, web search). The plugin itself is Markdown: command definitions, skills, and reference docs. Optional: ask-grok-mcp for best-in-class tweet ingestion, tobi/qmd for local search beyond ~100 articles. How do I update to the latest version? Claude Code: claude plugin update wiki@llm-wiki and restart. Codex: codex plugin marketplace upgrade llm-wiki (or re-run the bootstrap helper for a local checkout). AGENTS.md: re-curl from the master branch to replace your file. See Install for the manual sync fallback when the plugin updater hits stale cache. Credits learntoprompt.org — sister site: practical guides for AI coding agent setup, sandboxing, and prompting workflows. Andrej Karpathy — the LLM wiki concept and idea file. Elisha Long — retardmaxxing philosophy. tobi/qmd — recommended local search engine for scaling beyond ~100 articles. rvk7895/llm-knowledge-bases — prior art in Claude Code wiki plugins.