Library
Four places a model can reach for: knowledge, notes, memory and skills. All of it is yours to see and edit, and shareable read-only.
The four parts
| Part | What it holds | Who writes it |
|---|---|---|
| Knowledge | Documents, images and web pages, grouped into named bases — one per subject, project or client. | You (and a model, when allowed) |
| Notes | Longer things a model writes down and finds again later. | The model, and you |
| Memory | Short facts about you, in front of the model on every turn. | The model, and you |
| Skills | Saved procedures a model can follow — and write. | You, and the model |
Open it from the sidebar’s Library. Reports from schedules are a tab there too. Memory is under Settings → Memory.
Giving a model the library
Nothing is on by default for a model. Under Admin → Models, choose which built-in tools it gets: knowledge search, notes, memory, skills. Reading and writing are separate permissions for notes, memory and skills, so a group can read the shared skills without being able to change them.
Knowledge bases
- A chat with no base attached searches everything you can read. Tick bases in the chat’s settings panel and it searches only those.
- Knowledge is searched before the web.
- Sharing happens per base: share it and everything in it comes too, read-only.
- Saving a link makes the server fetch it. Addresses on the server’s own machine and network are refused unless an administrator allows them under Admin → Web search.
Search
Library search is keyword search out of the box, with nothing to run and nothing sent anywhere. Pick an embedding model and it also searches by meaning, so “how do I get paid” finds a document about invoicing. See Search.
From the LLeMbas CLI
A CLI logged in with the library scope uses your library on the server by default — memory, notes, skills and knowledge — through the server’s MCP endpoint. Write library: local in its config to keep that machine’s own.