SpiritBox knowledge interactive simulation
Interactive simulation: files, passages, counts, and status values are examples. No file is uploaded or indexed.
Preview limits
Knowledge Base
Upload Documents
Example formatsThis example illustrates extracting and indexing document text for semantic recall, then reviewing passages before adding selected context to a chat.
Example Indexed Documents
Demo data| Document | Type | Status |
|---|---|---|
| Q4_Financial_Report.pdf | Indexed | |
| Product_Requirements.docx | DOCX | Indexed |
| Customer_Feedback_2026.csv | CSV | Indexed |
| API_Documentation.md | Markdown | Indexed |
| Budget_Projections.xlsx | Excel | Indexed |
| Meeting_Notes_Feb.txt | Text | Indexed |
How Knowledge Base Works
This simulation depicts document extraction, pgvector embedding, and PostgreSQL storage on user-controlled hardware. Use >>recall <topic> to retrieve relevant chunks and choose which ones enter the model context. Core knowledge storage is designed to remain local; optional model, search, messaging, update, and API connections may send selected data to external services when you enable them.
Semantic Recall
In chat, request matches with:
>>recall project schedule risks
SpiritBox returns matching chunks for review. You decide which passages to inject into the conversation.
Local Storage Boundary
Best Practices
- Use clean, well-formatted documents for best results
- PDF tables are extracted with pdfplumber for accuracy
- CSV/Excel files are chunked row-by-row with headers
- Markdown preserves code blocks and structure
- Review how large documents are split before relying on retrieved passages
- Re-upload a file to update its index