Create & Configure a Knowledge Base
Open Knowledge Base → Knowledge base management — the "My knowledge bases" overview. The table lists title (link to detail), description, public flag, strict flag; the actions column offers Docs / API / Edit / Delete.
- The search box filters by title (Enter or click the search button);
- The table paginates at the bottom ("{n} items in total").

Creating a Knowledge Base
- Click Add to open the form (five settings cards);
- Fill in each group as described below;
- Save and return to the list.
TIP
For a first base, only the title is required — start importing with defaults; splitting and retrieval settings can be changed later (splitting changes trigger a rebuild, see below).
1. Basics
| Field | Required | Description |
|---|---|---|
| Title | yes | Name of the knowledge base |
| Description | no | Purpose, visible to others when public |
| Public | no, default private | Public: visible and usable by everyone; private: creator only |
| Strict mode | no, default lenient | In-app hint (translated): "Strict mode: strictly match the knowledge base; if there is no search result, return 'no answer' directly. Lenient mode: if there is no search result, pass the user's question to the LLM to continue." See Overview |
2. Document Index Settings (Vector)
| Field | Description |
|---|---|
| Split overlap | Characters shared by adjacent segments (marked "applies to new indexing after change") — keeps boundary information intact |
| Split strategy | Recursive / by paragraph / by line / by sentence / custom separator (required when custom, e.g. \n\n, \n) |
| Max tokens per segment | Upper bound of a segment |
| Token estimator | OpenAI / Qwen / Huggingface counting conventions — match your embedding model family |
TIP
"By paragraph" suits well-structured documents; "recursive" is the general default; tables and logs suit "by line" or a custom separator.
3. Document Index Settings (Model)
Model: the in-app hint (translated) reads —
The model used for graph extraction and QA generation; if empty, the first available model is used.
WARNING
Graph extraction and QA generation both consume this model's tokens. Pick a cost-effective model; leaving it empty falls back to the first available model.
4. Retrieval Settings
| Field | Description |
|---|---|
| Max retrieved | Maximum segments recalled per query — higher is more thorough but costs more |
| Min score | Segments below this similarity are excluded — higher is stricter and filters out more noise |
5. LLM Parameters
| Field | Description |
|---|---|
| System prompt | Persona for knowledge base Q&A (e.g. "You are the company policy assistant; answer only from retrieved content") |
| Creativity / randomness | Answer temperature: lower = more conservative, higher = more varied |

Editing
Click Edit in the actions column. Note the consequences:
| Change | Effect |
|---|---|
| Retrieval settings, LLM parameters | Immediate, no rebuild |
| Splitting parameters (overlap / strategy / max tokens…) | Save prompts "Changing split parameters will automatically rebuild the vector indexes of all documents in this knowledge base. Save?" — confirming triggers an automatic rebuild of all indexes (can take a while for large bases) |
API
The API action generates this base's API key and endpoint docs — see API Reference · Knowledge Base Q&A.
Deleting
- Click Delete in the actions column;
- Confirm "The data cannot be recovered after deletion. Delete knowledge base [{title}]?".
WARNING
Deleting removes documents, segments, vectors and graphs — irrecoverable. Characters linked to the base lose its retrieval.
Previous: Overview · Next: Import Documents