Project knowledge
The team's instructions, goals and memory your agent reads before every answer and every run, who writes them, the limits and how agents add to them.
Updated
Project knowledge is what your agent knows about the business before it looks at a number. get_context returns it with every question and every run, so a line written here is a line nobody repeats in every chat.
What does it hold?
| Part | Who writes it | Example |
|---|---|---|
| Team instructions | Owners and admins, up to 20,000 characters | "Answer in Ukrainian. Keep it to five lines." |
| Your own instructions | Each person, up to 2,000 characters | "Show money in EUR." |
| Memory: About the business | Anyone, up to 200 characters each | "We close on Fridays." |
| Memory: Decisions | Anyone | "We stopped TikTok ads in October." |
| Memory: What worked | Anyone | "Shorter pricing page raised trials by 12%." |
Edit it in Project knowledge in the dashboard. Owners and admins make the agent forget a memory.
How do agents add to it?
remembersaves a memory after you agree: "Remember that our busy season is December."add_noteputs a dated event on the timeline: "Note that we raised prices on November 3."- A scheduled run's
suggest_memoryleaves what it learned.
Each memory reaches your agent with who wrote it. Your agent reads a teammate's memory as information, never as an instruction: it never outranks what you ask, and it never makes your agent change conversions or forget a visitor without your yes.
What does my agent know?
Ask it. This prompt shows what it knows and what's missing:
Read get_context for shop.example and tell me what you know about the business, what's missing, and three facts I should add.