Knowledge
Knowledge
Knowledge is where a project's context, documents and rules live. Equip it to a thread and the AI reads it before answering. The moment you notice you're explaining the same thing again, that's the signal to write it here.
What belongs here
| Kind | Examples |
|---|---|
| Context and instructions | The goal of this project, tone of voice, what to avoid, how to prioritise |
| Documents | Product details, pricing, specs, past meeting notes, reference links |
| Rules and decisions | “In this situation, do this”, and decisions already made with the reasoning |
| Access notes | How to reach an external service, where the keys live, what's already configured |
Creating knowledge
＋New at the bottom of the sidebar → Knowledge.
Give it a name. Including the project or client makes it findable later.
Write the context and instructions you want the AI to read. You can attach files too.
It then appears under Knowledge in the sidebar.
Equipping it to a thread
Open the thread you want to use it in.
Open 📚 Knowledge, roles, connections in the composer.
Select the knowledge you want (multiple is fine).
Everything equipped shows as a chip above the composer, so you can always see what the AI is receiving.
Equipping unrelated knowledge blurs the instruction and lowers quality. Pick only what actually applies to this piece of work.
How it's stored (OKF)
Knowledge isn't locked inside the app. It's saved under knowledge-base/ in your storage folder,
one folder per knowledge entry, as Markdown — following the OKF (Open Knowledge Format) convention.
| File | Contents |
|---|---|
instructions.md | Context and instructions |
ai-knowledge.md | Knowledge written for the AI |
product.md | Product or service information |
There are two reasons for this shape. First, your context and instructions survive even if the app's internal data is damaged. Second, because it's plain Markdown, you can hand it to other AI tools as-is. Folder names keep their original wording — being human-readable is the point of OKF.
Organising with folders
As knowledge accumulates, group it into folders using the 📁 button on each row:
- Move to folder — put it in an existing folder
- New folder… — create one and name it
- Move out of folder — take it back out
Folders are visual only — they don't affect equipment or where files are stored. Empty folders disappear automatically.
Keep access notes (important)
Nobody remembers how an external service was wired up. Without a note, you redo the setup every time. Keeping those details in knowledge is worth the two minutes.
- Which service, connected which way
- Where the credentials live — the location, not the value
- The date it was set up
- Any trap you hit, and how you got around it
Never paste the actual API keys or passwords. Let the app's keychain hold the secrets and record only that they are configured. Assume anyone you share this knowledge with will read every word of it.
Sharing with a team
If you belong to a team space, ＋New offers Shared knowledge, which syncs to members through the shared folder. See Team spaces.
What deleting does
Deleting asks for confirmation. Afterwards, threads that had it equipped simply lose the reference. Deleting shared knowledge removes it for everyone in the space, and cannot be undone.
Where to go next
- Skills — reuse the procedure rather than the context
- AI team — give different roles different context
- Settings and where data lives — the actual folder structure