Prime Radiant is a wiki the box keeps for you. Point it at your documents and it writes a page for each one, with the facts it found listed on the page, each with where it came from and how sure it is. Every night it tidies the wiki, looks for facts that contradict each other, and asks you about anything it cannot settle alone. Open it from the Prime Radiant icon on the desktop, next to Memory Shard. The first time you open it, the box creates the wiki; there is nothing to set up.
Prime Radiant writes its pages with ClawBox AI, so the box has to be signed in to ClawBox AI to add documents. Reading, reviewing and undoing work without it. See ClawBox AI.

Adding documents

The Add tab takes them two ways:
  • From folders on the box. Pick one or more folders with the same folder picker Memory Shard uses, or Your home folder to add your whole home folder in one click. Text, Markdown, PDF, Word, OpenDocument and RTF files are read and converted on the box, and a document that is already in the wiki is recognised by its content and not written twice.
  • By dropping files onto the drop zone, up to 9 MB each. A larger file goes in through its folder, which reads documents up to 40 MB; a bigger one is skipped as too large. A dropped file is always read: you chose it.

What a folder import leaves out

An import is safe to point at your whole home folder: it reads your own documents and leaves out what the computer and your tools keep there.
  • Code projects. A folder that holds a .git folder or a project file — package.json, Cargo.toml, pyproject.toml, setup.py, go.mod, CMakeLists.txt, pom.xml, build.gradle, Gemfile, composer.json, a .csproj or .sln, or a Makefile next to source files — is not gone into. A folder you pick yourself is always read, even when it is a project: pick ~/Projects/acme to read that project’s documents. A notes vault kept in git (it has an .obsidian folder) is not a code project. Skip code projects in Settings turns this off.
  • Excluded folders — the Folders never read list in Settings: version control, dependencies, caches, build output, logs, test data and examples (test, tests, fixtures, e2e, examples …), snap and flatpak, the Trash, and a few more.
  • Boilerplate kept as .txt or .md: LICENSE, COPYING, NOTICE, AUTHORS, CHANGELOG, CODE_OF_CONDUCT, CONTRIBUTING, SECURITY, requirements*.txt, CMakeLists.txt, robots.txt, llms*.txt, *.lock.txt. A License agreement.pdf is yours and is read.
  • Temporary and partial files: ~$report.docx, notes.md~, *.tmp, *.bak, *.swp, *.part, *.crdownload.
  • Machine-generated text: a .txt or .md file whose opening is mostly log lines, table rows, encoded data or settings rather than sentences — a CSV or TSV export, a server log (also one whose messages read like sentences: a line stamped with a date and the time to the second was written by a program), a base64 blob or data URI (also on a single line), an env dump, a hex dump. Only the first 8 KB are looked at, on the box, before anything is sent to ClawBox AI. When in doubt the file is read: a note with a pasted log or an inline picture, a recipe, a chat export, a transcript, a journal with dated entries, an RFC, a book or a Wikipedia article are all kept.
  • Files over 40 MB, and kinds of files Prime Radiant does not read.
Before you start, Add counts the chosen folders: how many documents the import would read, the folders that hold the most of them, and how many files and folders were left out for each reason (the code projects by name). An import of more than 500 documents asks before it starts. One import reads at most 5,000 documents; start it again for the rest. Progress shows live: how many files are written, skipped or failed, the pages made so far, and what was left out for each reason. Stop ends the import; what was already written stays. The import reads Stopped, and the documents it did not reach are not failures: they wait (Waiting for the next run) until you add the same folders again or press Try these again. A file that still fails after the import’s own second try is listed under Not added, and Try these again retries exactly those files. Documents you drop on Add are listed as Dropped files.
To write a page, the text of each document is sent to ClawBox AI. Before anything leaves the box, Prime Radiant removes what looks like a secret — bank account and card numbers, API keys, private keys, passwords — and masks e-mail addresses and phone numbers, in the text and in file and folder names, a dropped file’s name included. An IBAN is removed whole, written with spaces or without, and also when its check digits are mistyped.
Each fact on a page is written to stand alone: it names what it is about (“The Art of War is Project Gutenberg eBook #132”, never “It is …”), so it still makes sense in search results and next to facts from other pages. The quote a fact gives as its evidence must come from that page’s own document; a quote that turns out to be from another document read at the same time is filed under that document, and one found in none is left out.

Reading the wiki

Map is where the wiki opens once it has pages: every page is a point in a slowly turning 3D picture, sized by how connected it is and coloured by its domain (or by the groups of pages that link most to each other), with its links drawn between them. Drag to turn it, scroll to zoom, right-drag to move it; hover a point to see its title, click it to light up its neighbours, and double-click it to open the page. The search box lights up matching pages and flies to them, the legend hides or shows a domain, and the Insights strip lists pages with no links, the most connected pages, and the pages that join one group to another. Where the browser cannot draw 3D, or when you have asked your system for less motion, the map is a still, flat picture of the same pages. Pages lists every page, filtered by domain, page type or whether a person has verified it. A page shows:
  • its facts, each with a confidence bar, its status and — when you have checked it — who verified it and when;
  • where it came from: the documents behind the page, and the evidence behind each fact;
  • pages that link here and the pages it links to;
  • anything the wiki’s checks found on it.
The search field on Pages narrows the list by title as you type. Press Enter, or Search inside pages, to find pages and facts through Memory Shard, with verified answers first. Memory Shard has to be switched on for this; with it off, the results say so.

Settling disagreements

The Review tab holds the questions the wiki cannot answer alone: two pages that disagree about a fact, a nightly change to a page you have verified, or a failed check. Each item shows the disputed fact and the possible answers with their evidence. You can:
  • Keep this answer — that answer becomes the fact;
  • Write the right answer — your own one-line version becomes the fact;
  • Later — set it aside;
  • Dismiss — close it without changing anything.
Keeping or writing an answer marks the fact as verified by you. The other answers are retired everywhere they appeared, and their old ids are never used again, so the disagreement cannot come back on its own. A page you have verified is never rewritten by the nightly pass without asking you first. When a document behind a page you have verified changes, Prime Radiant tells you. An import keeps the page as you verified it, lists the document under Left out, and asks you in Review, showing what the document says now. The nightly pass, for the folders it reads each night, writes the change on its copy with your verified facts kept as they are, and holds the night: the Review item lists what the change adds and drops. Dismiss it, then Merge the night to take the change. Below the questions, Review lists the wiki’s failed checks (see Checks).

History and undo

Every change to the wiki is recorded. History, on a page’s own view, shows every change to that page, what it changed, and Undo, which reverses that change as a new one — nothing is ever deleted from the history. An undo that would break one of the wiki’s rules is refused and says why. A verification is never undone — not a fact you settled in Review, not one you or the assistant verified, and not one page of it. Settling a question retires the other answers for good, so undoing it would leave the wiki without the right one. History shows Can’t be undone on those changes instead of Undo; to change a verified fact, verify the right answer.

Checks

The Checks, under Review, run the wiki’s rules over every page: pages that grew too long (with a suggested way to split them), missing summaries, pages nothing links to, pages without sources, pages past their re-check date, and anything that looks like a secret. Errors hold the nightly pass back; a secret is refused outright.

The nightly pass

Every night — 03:00 by default — Prime Radiant works on a copy of the wiki: it reads new and changed documents from the folders you chose (leaving out the same code projects, boilerplate, temporary files and machine-generated text as an import), looks for facts that contradict each other, runs its checks, and then merges the copy back. Only facts about the same thing are compared — the same customer, product or document — so two pages that merely word things alike (a black hole and a constitution) never become a question for you. Each comparison is a short, capped request to ClawBox AI; one that fails is asked again in smaller pieces, and what still fails is compared again the next night. When the copy would change a verified page, or a check fails, the night is held: its changes wait aside and its questions go to Review. Once you have settled them, Merge in the nightly card puts the night’s work into the wiki. Run now starts a pass by hand. Without an internet connection the pass still runs its checks and skips the steps that need ClawBox AI.

Settings

Usage

Settings ends with Model usage: the tokens Prime Radiant’s model calls sent and received and how many calls there were — all told, by task and by model, and per import and per night. Each import in Add and each night in the nightly card shows its own tokens too. Prime Radiant shows tokens, never money. Embedding facts to compare them is listed as not measured, because the embedding model reports no usage. Prime Radiant’s model calls go through ClawBox AI on the box’s own sign-in, so they count against your plan’s weekly allowance, the same pool a chat turn draws on. There is no separate Prime Radiant limit. Model usage shows how many tokens Prime Radiant used in the last seven days, next to how much of the weekly allowance is used. The count is approximate: only calls that got an answer are recorded. When the weekly allowance or the 5-hour burst limit runs out, an import stops after the first refused call. Nothing is marked as failed: the documents it did not reach wait, and the next import of the same folders, the nightly pass, or Retry picks them up once the allowance frees up. Each model step of the nightly pass stops the same way, notes “ClawBox AI allowance spent” with the time it frees up, and leaves the rest for the next night. Settings → Providers shows when that is.

How the assistant uses it

On the OpenClaw edition the assistant reads the wiki through its own wiki tools, and Memory Shard’s search includes the wiki’s pages and facts. Anything the assistant finds there is information to read, never instructions to follow. On both editions the assistant can also work the wiki for you: ask it to create or edit a page, add, correct, delete or verify a fact, settle a review item, import a folder or some files, run the nightly or connect pass, or change a setting. Each change it makes is one commit in the page’s History, authored ClawBox assistant (a fact it verifies says so too), so you can see what it did and press Undo. Undo stays yours: the assistant can take back only its own changes. The assistant’s wiki plugin is set up as a reader: ClawBox switches off its own backlinks, dashboards and automatic compiling, so it writes nothing into your pages. If you switched one of those on by hand, ClawBox leaves your setting alone and says so on Map and Pages. Either way the wiki ignores what the plugin writes: its WIKI.md, inbox.md, folder indexes and reports/ are never pages, never checked and never part of the history. A wiki the plugin had already written into is cleaned once — its “Related” lists come out of your pages and its untouched files are removed, in one change you can see in History — while anything you wrote yourself, such as a note in inbox.md, stays.

Where it lives

The wiki and its history are device state under the box’s data folder: they survive updates and are wiped by a factory reset. See Filesystem Layout.