Personal Memory That Travels With You
Dawn now gives each user private memory pages for preferences, conventions, projects, decisions, and notes that should follow them across workspaces.
Dawn Team
Product Engineering
Dawn now gives each user private memory pages for preferences, conventions, projects, decisions, and notes that should follow them across workspaces.
Dawn Team
Product Engineering
Dawn now has personal memory: private memory pages that belong to you and can travel with you across workspaces. It gives agents a durable place to remember your preferences, conventions, projects, decisions, and notes without turning them into shared workspace knowledge.
Workspace memory is still the right place for team knowledge: project runbooks, shared decisions, source conventions, and context that everyone in a workspace should be able to use. Personal memory is different. It is for the things that make Dawn more useful for you specifically.
Some context is stable, but personal. You may prefer code reviews to start with blocking issues. You may want implementation plans before code changes. You may have a recurring project, customer, or product area that spans several workspaces. You may want Dawn to remember how you like release notes, specs, or status updates written.
Until now, that context either had to be repeated in every conversation or saved as workspace memory, where it could become visible and relevant to everyone else. Personal memory gives it a cleaner home.
You can tell Dawn things like:
Remember that I prefer PR review summaries to start with blockers, then risks, then test gaps.
Or:
Save this as my launch-writing preference: start with the user-facing change, then explain why it matters.
When that context is useful later, Dawn can use it without making you restate it.
Personal memory is organized as memory pages. The first version gives you a small tree of pages for profile context, preferences, conventions, projects, decisions, and notes. That keeps memory navigable instead of becoming one large unstructured blob.
You can manage these pages from My Memory in account settings. Search for a page, edit the content, save updates, or delete pages you no longer want Dawn to use.
Agents can also work with memory when you ask them to. If a conversation produces a durable preference or decision, you can ask Dawn to remember it. If you want to inspect what Dawn knows, ask what it remembers about a topic and review the relevant memory pages.
The important boundary is ownership. Workspace memory belongs to the workspace. Personal memory belongs to the user.
That means personal memory is not the place for shared team runbooks, public project decisions, or source-specific instructions everyone should follow. Those still belong in workspace memory. Personal memory is for user-owned context: your preferences, your working conventions, your recurring notes, and the projects you personally care about.
This separation matters in shared conversations. Dawn can use your personal preferences to shape a response when it is acting on your behalf, but it should not casually expose private memory content to other participants. If you ask Dawn to explain or share a memory, it can. Otherwise, the useful behavior is usually quiet: better answers with less repeated setup.
Personal memory also fits naturally with richer agent context. Agents already have workspace instructions, skills, connected sources, channel context, user preferences, file references, and prompt commands. Personal memory adds the user-specific layer that was missing.
That makes small interactions better. A review agent can remember your preferred review structure. A planning agent can remember how you like specs framed. A writing agent can remember your launch-post conventions. A support agent can remember that you prefer concise status updates unless you ask for detail.
The result should feel less like configuring every thread from scratch and more like continuing work with someone who already knows how you operate.
Personal memory is not secret storage. Do not use it for passwords, API keys, tokens, or credentials. It is also not a raw transcript archive or a hidden copy of every conversation.
Use it for stable context that you would be comfortable asking Dawn to remember and apply later: preferences, conventions, decisions, project notes, and profile details that improve future work.
Open account settings in Dawn Web and select My Memory. Review the default pages, add useful context, and keep the pages focused on information that should stay true across more than one conversation.
You can also start directly from chat. Ask Dawn to remember a preference, save a convention, or recall what it knows about a project. When the memory is personal to you rather than shared with the workspace, personal memory is the right place for it.
When it works well, the difference is subtle: fewer conversations that start with repeated setup, more that start with the actual work.