Account memory
Persistent facts about you that OpenV2 applies to every chat and project.
Account memory stores durable facts about you — not about a single app. Memories are saved to your OpenV2 account, shown on the dashboard Memory page, and injected into every chat automatically so the AI can honor your preferences without repeating them every session.
Open the Memory page
- Sign in and open the dashboard (
/dashboard) - In the sidebar, choose Memory (brain icon)
You can also go directly to /dashboard?view=memory.
What to save in memory
Good candidates:
- Stack and tooling preferences ("Always use TypeScript strict mode")
- Design taste ("Prefer minimal UI with large tap targets")
- Language or tone ("Reply in Romanian")
- Recurring workflow rules ("Always local-first unless I ask for cloud sync")
- Personal context the agent should remember ("I build fitness apps for clients")
Keep each memory to one short sentence (up to 1,000 characters). The platform injects enabled memories into chat context with a total cap so a very large memory bank cannot crowd out the current task.
Memory categories
The graph organizes facts into five branches:
| Category | Use for |
|---|---|
| Projects | How you work across apps, client types, or product focus |
| Code style | Conventions, patterns, and technical defaults |
| Preferences | General builder preferences and habits |
| Personal | Context about you that helps the assistant |
| Focus | Current priorities or constraints |
When the AI saves a memory, it picks the best category automatically. When you add one manually, choose the branch by clicking an empty slot on that branch.
Using the memory graph
| Action | How |
|---|---|
| Pan | Drag the background |
| Add | Click an empty slot on a branch, or use Add a memory at the bottom |
| Read | Click a memory node to expand it |
| Edit | Double-click a memory node |
| Delete | Trash icon on the memory node |
| Rearrange | Drag memory nodes — layout is saved for your account |
| Import | Import (top right) → pick ChatGPT, Claude, Gemini, etc. → copy the export prompt → paste the reply |
Agent-saved memories show where they were learned when available (for example, Learned in My Fitness App).
Import from another AI
Use Import when you already have context stored in ChatGPT, Claude, Gemini, Copilot, Grok, or another assistant. The flow matches common memory migration patterns (copy a prompt into the other AI, then paste the structured reply into OpenV2):
- Click Import and choose your source assistant (or Paste text for any exported list).
- Step 1 — copy the export prompt and send it in your other AI. Ask it to return memories inside a markdown code block, one fact per line.
- Step 2 — paste that reply into OpenV2 and click Import memories.
OpenV2 splits the paste into individual memories, skips duplicates, and places each on the graph (category is inferred automatically). Up to 40 entries per import.
How the AI uses memory
On every chat turn, enabled memories are grouped by category and added to the AI context. The assistant treats them as established facts:
- It honors them silently — no need to repeat preferences in every prompt
- It does not claim to remember past conversations unless the fact is listed in memory
- Project knowledge wins if a memory and a project rule conflict
The agent can also save memories for you with the remember tool when you state something durable during chat (for example, "I always want dark mode by default"). It saves quietly — you will see new nodes appear on the Memory page, and OpenV2 Buddy may react with a Saved! bubble.
You can ask in chat:
Memory vs. project knowledge
| Account memory | Project knowledge | |
|---|---|---|
| Scope | Your whole OpenV2 account | One project only |
| Edited in | Dashboard → Memory | V2 Cloud → Knowledge |
| Stored as | Platform database (user_memories) | PROJECT_KNOWLEDGE.md in the workspace |
| Example | "Prefer NativeWind over StyleSheet" | "This app's brand color is teal" |
See also Skills & knowledge for platform-wide skills (maintained by OpenV2).
Privacy tips
- Do not store passwords, API keys, tokens, or other secrets in memory
- Remove outdated facts from the graph when your preferences change
- Memories apply to every project — use project knowledge for app-specific rules