Knowledge
Per-project instructions that guide the OpenV2 AI for a specific app.
Knowledge stores custom instructions that apply only to the current project. Content is saved as PROJECT_KNOWLEDGE.md in your workspace and included in AI context on every chat turn.
What to put in knowledge
Good candidates:
- Product name, tone, and terminology
- Feature priorities ("MVP is habits only, no social")
- Technical constraints ("Always local-first for notes")
- Business rules ("Free tier limited to 3 projects")
Editing knowledge
- Open V2 Cloud → Knowledge
- Write or paste instructions in the editor
- Save — updates persist to the project file
You can also ask the AI to update knowledge:
TEXT
Knowledge vs. account memory
| Knowledge | Account memory | |
|---|---|---|
| Scope | This project only | Your whole OpenV2 account |
| Edited in | V2 Cloud → Knowledge | Dashboard → Memory |
| Example | "Brand color is teal" | "Prefer large tap targets on mobile" |
Project knowledge wins if it conflicts with an account memory entry.
Knowledge vs. skills
| Knowledge | Skills | |
|---|---|---|
| Scope | This project only | All OpenV2 projects |
| Edited by | You | OpenV2 team |
| Example | "Brand color is teal" | Native layout contract |
See Skills & knowledge.