Use memory without losing control
Let Edvin remember useful preferences and project context, then review or clear memories whenever needed.
Updated May 21, 2026
What you will have
Outcome
Edvin can reuse durable context while keeping memory visible and controllable.
Decide what is worth remembering
Writing style, project context, coding preferences, and personal preferences can save repeated explanations.
Keep memory simple
Use memory for stable context, not temporary task details. A one-off instruction belongs in the chat.
Review and clear
Open Memory & Context in Settings to see saved memories, delete individual items, or clear all memory.
Try it in chat
Use this as a starting point. Add your real goal, source material, and deadline.
“Remember that I prefer direct answers and usually work on founder/product tasks.”
More ways to ask
“Remember that I like concise launch plans.”
“Remember that my app is built with Next.js and Supabase.”
“Forget the old positioning for my project.”
Things worth knowing
- Disable memory if you want fresh chats.
- Do not store sensitive secrets in memory.
- Use project docs for detailed context.
Still blocked?
Tell us where the guide stopped being useful.