Plasma Wiki Review 2026: Deterministic Indexed Wikis for Agents

As agents start writing and editing knowledge bases, a familiar problem returns: who maintains the index? Plasma Wiki answers with a deterministic CLI that generates and maintains _index.md files and cross-links for markdown wikis designed to be read and written by both humans and AI agents.

What is Plasma Wiki?

Plasma Wiki is a set of command-line tools for indexed knowledge bases — a deterministic CLI that generates and maintains _index.md index files at every directory level, with cross-links between entries. Agents consult the index and open only the pages a task needs, instead of loading the whole wiki. It’s Apache-2.0 and aimed squarely at the “LLM wiki” pattern (Karpathy’s and Google’s Open Knowledge Format).

Key features

• Deterministic index generation — the CLI automatically generates _index.md files at every directory level, creating a tree of markdown files linked together by index pages.
• Auto-resolved parallel edits — generated regions of _index.md use a *** delimiter; when parallel agent edits collide, the generated region auto-resolves on merge, while your authored content below the delimiter still merges normally.
• Agent-native CLI tools — wiki init, wiki config (Obsidian plugins + git merge driver), wiki lint, wiki update, wiki map, wiki search, wiki read. Built for both human and agent use.
• Obsidian integration — humans author in Obsidian (or any editor); agents query through the CLI. Includes staged Obsidian config and Front Matter Title plugin setup.
• Strong docs for its size — Sphinx docs on ReadTheDocs; documentation quality is a standout for a 46-star project.
• Agent-ecosystem awareness — Claude Code and Codex plugin/marketplace support show it was built with agents in mind.

Who should use it?

Plasma Wiki is for teams and individuals running a markdown knowledge base that both humans and AI agents edit. If you’re building an “agent-readable wiki” — a second brain your coding agents can navigate without context-bloating — the deterministic index and parallel-edit resolution are exactly the hard parts it solves.

It’s less compelling if you just want a personal note vault you never share with agents; at 46 stars and a single contributor, it’s early and the community is small.

How it compares

Generic note tools (Obsidian, Logseq) give you a wiki but leave index maintenance to you. RAG pipelines index content but don’t produce a human-navigable, agent-consultable markdown tree. Plasma Wiki sits between: a deterministic, merge-friendly index layer purpose-built for agent + human co-editing. Pair it with your Claude Code or Cursor workflow.

Pros and cons

Pros: deterministic indexing; parallel-edit auto-resolution; agent-native CLI; Obsidian integration; Apache-2.0; excellent documentation for its size; agent-ecosystem aware.

Cons: early-stage (46 stars, 1 contributor); small community and limited real-world validation; moderate maturity; focused on markdown wikis, not general knowledge stores.

Pricing

Free and open source (Apache-2.0).

FAQ

Does Plasma Wiki replace Obsidian? No — it complements it. Humans author in Obsidian; agents query the wiki through the CLI, and the index stays in sync.

How does it handle concurrent agent edits? Generated index regions use a *** delimiter and auto-resolve on merge, so parallel edits converge instead of conflicting.

Is it open source? Yes, Apache-2.0. See the ai-code category for more developer-focused agent tools.