Knowledge Base for AI assistants
Prepare a shared document library for RAG assistants, product guides or virtual trainers. Select which files each character may use when answering questions.
The Knowledge Base is how a character stops improvising and starts answering from your actual material — the price list, the policy document, the product manual. Open it from the top bar: Knowledge › Knowledge Base ("Documents and pages your characters answer from"). Files live here at workspace level; each character is then given access to specific ones on its own Knowledge Base tab (Mind & knowledge › Knowledge Base in the character editor).
What you can upload
Drag files onto the drop zone or click it (Drag a file or click). You can drop several at once; each is processed on its own.
| Format | Notes |
|---|---|
| The most common source. The text layer is read page by page; a scanned PDF with no text layer fails. | |
Word (.docx) | Handled directly — no need to export to PDF first. The paragraph text is read, so put important answers in paragraphs rather than Word tables. |
Text and Markdown (.txt, .md) | Ideal, because you control exactly how it is written. |
| CSV | Good for price lists and specification tables. It is read as plain text, so keep column headings meaningful. |
| Images — JPG, PNG, WebP | The text inside them is read automatically, so a photographed menu or a screenshot of a table works. |
Maximum 50 MB per file. Other file types are refused, and so is a file whose contents do not match its extension.
What happens after upload
- PROCESSING — the file is read, split into short overlapping passages, and indexed so it can be searched by meaning rather than by keyword.
- READY — the file can now be used. The list (Files, with a count) refreshes itself, so you can watch it change. Each row shows the size, the number of chunks, the date and whether the file is tenant-wide.
- FAILED — the file could not be read. Usually a scanned PDF with no text, or an image with no readable text.
Deleting
The trash icon on a file removes it from the workspace, together with its indexed passages and every character's access to it, immediately and without a confirmation prompt. There is no undo — re-upload if you delete the wrong one. To stop one character using a file without deleting it, switch it off on that character's Knowledge Base tab.
Writing documents that retrieve well
Retrieval finds passages, not documents. How you write has more effect on answer quality than which model you pay for.
| Do | Instead of |
|---|---|
| One file per subject — "Returns policy", "Delivery times", "Warranty" | A single 200-page company handbook |
| Headings that read like customer questions — "How long does delivery take?" | "Section 4.2.1 — Logistics" |
| The answer immediately under the heading | An answer spread across three pages |
| Spelling out the subject in each section | "As mentioned above, it is 14 days" |
| Plain sentences | Tables of abbreviations with no context |
Checking it works
Every character's Knowledge Base tab has a Search Test box. It searches only the files enabled for that character. Type the question a real customer would ask — not the keyword you think is in the document — and confirm the returned passages actually contain the answer. If they do not, the fix is in the document, not in the character.