Knowledge
Knowledge gives agents information to base their answers on. There are two kinds:
- Global knowledge: short rules for the whole workspace. For example: "Discounts above 10% need approval from management." Every entry goes to the model in full with every request, wherever the global knowledge is switched on. Agent steps in a workflow do not get it.
- Documents on an agent: files and texts for one agent, such as a price list or a handbook. With every question, the agent gets the matching sections.
Add global knowledge
- Open Knowledge in the sidebar.
- Type the rule into the empty row at the bottom of the page.
- Click Remember or press ⌘/Ctrl+Enter.
Enter alone starts a new paragraph. To change an entry, click its text. The change is saved when you leave the field. Escape cancels.
To delete an entry, hover over it and click the bin.
If you write something in the chat that applies permanently, the chat can suggest adding it to the global knowledge. It is saved only when you click Remember.
Export downloads all entries as a JSON file. There is no import for this file.
Limits
| Limit | Value |
|---|---|
| Entries per workspace | 50 |
| Characters per entry | 10,000 |
URLs are not allowed in entries. An entry that already exists is rejected.
At the top right, the page shows roughly how many tokens the global knowledge takes up. From about 2,500 tokens a yellow warning appears, from about 6,000 tokens it turns red. Long knowledge raises the cost of every request, and the model follows individual rules less well. Saving still works.
Turn global knowledge on or off
On an agent's page, the switch Use knowledge decides whether the agent gets the global knowledge. It applies in the chat and to the assistant that builds workflows.
Attach documents to an agent
Open the agent. The card Knowledge offers three ways:
- Files: drag files onto the card, or click it and select them.
- Paste text: click Paste text, enter a name and the text, and click Add knowledge.
- SharePoint or OneDrive: click Import from SharePoint or Import from OneDrive and choose a folder. Subfolders are imported too.
The import from SharePoint or OneDrive runs once. Changed files come in with the next import.
File types
| Format | Supported |
|---|---|
| PDF with a text layer | yes |
| Word (.docx), Excel (.xlsx) | yes |
| .txt, .md, .csv, .json | yes |
| .doc, .xls, .pptx, images | no |
| Scanned PDF without a text layer | no, there is no text recognition |
Limits
| Limit | Value |
|---|---|
| Size per file | 25 MB |
| Size per upload | 50 MB |
| Files per folder import | 100 |
| Pasted text | 500,000 characters |
How an agent uses its documents
On upload, lowcloud splits every document into sections. With every chat message, lowcloud finds the best-matching sections and passes them to the agent. The agent is instructed to say so when the answer is not in the documents.
In a workflow, you select the documents on the agent step in the field Knowledge. With little text, the step reads all of it. With more text, it gets the best-matching sections and can search for more.
The switch Show sources in the chat is on by default. The chat then marks, after each statement, the source that supports it.
Splitting and searching always run at Melious in the EU, even when the agent uses a model of the tier European servers. Documents and original files are stored in lowcloud's database. Details are under Sovereignty and models.
Update and remove documents
Upload a file with the same name to the same agent again. lowcloud then replaces the old content instead of adding a second document. The same applies to Paste text with the same name and to a repeated folder import.
The × next to a source under Stored sources removes the document from the agent.
Costs
Reading a document on upload and searching documents use credit. In the Dashboard, reading counts towards Knowledge. Searching counts towards Chat or, in a workflow, towards Workflows, including test runs. An agent without documents causes no search costs.
Knowledge when exporting an agent
The export of an agent contains the text of its documents. The global knowledge is not included. An imported agent arrives with Use knowledge switched off. You cannot import an export with more than 2,000 sections.
How to export an agent is described under Sharing and access.
Permissions
Anyone who may build (the role admin, or the former role developer) can edit the global knowledge and an agent's documents. People with the role member do not see Knowledge in the sidebar.
In a partner's client workspace, the partner's team builds. The client's own people see no build functions there, see Partner.