Plasma Wiki

We built Plasma Wiki after running many agents on large projects at Plasma. They kept reloading the same material into context and overwriting each other's edits.

Plasma Wiki gives them a compact index to read first, so each agent opens only the pages a task needs. It became part of our daily workflow, and it is our first open-source tool. Fractal keeps each agent node's memory in a wiki.

Install the package and initialize a wiki:

wiki map prints the tree with word counts for each page and subtree. This is what the agent sees first:

The agent reads api/ (210/4.5k) as a 210-word index summarizing a 4,500-word subtree. It opens api/ only when a task touches it, then reads a single page such as auth rather than the whole project.

Once the wiki has content, the loop is wiki map to see the layout, wiki search <pattern> to find a page, and wiki read <name> --words :100 to read its first 100 words. Agents run that loop through the /wiki skill or call the wiki CLI directly.

Under the hood it's just files: each folder becomes a section, each Markdown file an entry, with _index.md files wiring the tree together. The same files serve people and agents: you edit them in Obsidian or any editor, and agents query them through the wiki CLI.

We are not the first to point agents at a wiki: Andrej Karpathy sketched an LLM-maintained one, and Google's Open Knowledge Format standardizes the shape. What Plasma Wiki adds is a deterministic CLI that keeps the index and links in sync, so the LLM only writes content.

Unlike a single AGENTS.md or an unindexed docs folder, the indexed tree scales: the agent navigates it instead of scanning everything.

New information updates the topic's existing page instead of accumulating as dated entries, so the wiki reads like a reference. Because it is plain files in your repo, every change is a reviewable diff and any page can be edited by hand.