wiki

LM Studio plugin that turns a folder into a persistent, LLM-maintained wiki: pages, raw sources, an auto-rebuilt index, and an append-only activity log.

The pattern follows Andrej Karpathy's LLM Wiki gist: instead of querying raw documents from scratch every time (RAG), the model incrementally builds and curates a markdown wiki that compounds over time. Three workflows: ingest new sources, query the wiki, lint for drift.

The plugin provides the primitives — sandboxed, atomic, with auto-backup and auto-indexing. The model is the curator.

Layout

The plugin owns a single root directory, configured via the Wiki root field:

<root>/
├── index.md           # auto-maintained catalog (between marker comments)
├── log.md             # append-only activity log
├── WIKI.md            # editable schema/conventions doc the model reads
├── pages/             # wiki pages (markdown), one topic per file
├── sources/           # raw immutable sources (+ optional <name>.meta.json)
└── .wiki-backup/      # snapshots of overwritten/deleted files

index.md and log.md use marker comments (<!-- wiki:pages:auto -→…<!-- /wiki:pages:auto -→) so the plugin only ever rewrites the auto-region — anything outside is yours to edit freely.

Tools

Lifecycle

• wiki_init(name?, description?, schema?, overwrite?) — scaffold a fresh wiki. Creates the dirs and the three top-level files.
• wiki_status() — counts of pages and sources, last 10 log entries. First call when picking up wiki work.
• wiki_lint() — read-only health-check: pages missing from the index, broken cross-links, orphans, duplicate names.

Pages

Sources

• wiki_save_source(name, content, origin?) — store a raw source. origin is recorded in <name>.meta.json and shown in the index.
• wiki_read_source(name) — read with origin.
• wiki_list_sources(filter?) — list with origins.

Search & log

• wiki_search(pattern, scope?, ignore_case?, max_results?) — regex across pages/, sources/, or both.
• wiki_log_append(kind, subject, message) — manual log entry for query results, ingest decisions, etc. (Writes/deletes/renames already log themselves.)

Why no preview/confirm step

The sibling filesystem plugin uses a two-call write protocol so the user can approve a preview before any write. That works on ~8B models but is brittle on ~4B (small models tend to skip the confirm). The wiki plugin drops the protocol entirely:

• One-shot writes — fits the small-model tool-call budget.
• Backups happen anyway before any overwrite/delete (.wiki-backup/<kind>/<name>.<timestamp>.bak), so writes are reversible.
• Every write also rebuilds the index and appends a log line — the wiki keeps itself coherent without a separate housekeeping step.

This is the design choice: trade explicit preview for atomic operations + recoverability. Suited to a personal knowledge base where the user inspects the result after.

Composition

Designed to compose with the other plugins in this repo:

• with filesystem: pull in something from anywhere on disk and fold it in.

Configuration

Field	Type	Default	Notes
Wiki root	string	""	Absolute path of the wiki dir. Tilde (~) expands. Required.
Max page size (KB)	int	512	Cap on wiki_read_page / wiki_read_source.
Max search matches	int	200	wiki_search stops after this many lines.
Max search files	int	2000	wiki_search stops after scanning this many files.

Naming and structure conventions

Encoded in the auto-generated WIKI.md. Edit it freely to encode your own taxonomy — the model is expected to read it before contributing. Defaults:

• Pages: kebab-case, .md extension. One canonical name per concept.
• Optional YAML frontmatter on a page: category, tags, summary (used by the index).
• Cross-references: [link text](other-page.md). The lint tool flags broken links.

Install

Linux (AppImage) / cross-OS:

After install: in any chat, click the tools button and enable wiki. Then set the Wiki root field in the per-chat config (e.g. ~/Documents/wiki) and ask the model to call wiki_init.

License

MIT