Project memories
Capture the short facts and rules your Project's agent should keep using, scoped tight to this one Project. Memories live with the Project and surface in every relevant conversation.
Audience: builders
Find the Memories section
Open your Project. Click the Context tab. Pick Memories. The header reads "Memories" with a count and a Memory button on the right; a one-line note underneath says "Short facts the agent has learned or been told."
The body is a flat list with two row types stacked together: live memories (the user glyph) and pending candidates (the sparkle glyph with a yellow Pending review badge). A search field above the list filters across title, body, tags, and path.
Read the two states
- Live. Saved and injected into agent context when relevant. The row shows the title, "Updated 5d ago", and any tags.
- Pending review. A proposal the agent surfaced from an analyst correction in a conversation. Renders with the Pending review badge and a "Proposed 2h ago" line.
The drawer marks live entries with a Manual provenance chip and candidates with a Learned chip, so you can tell at a glance how each memory got here.
Author a memory directly
When you already know the fact, write it down.
Open the create drawer
Click Memory in the section header. The drawer opens titled "New memory".
Fill the form
- Name. A short, searchable title. Shown in the list and when the memory is recalled.
- Memory. What the agent should remember, in your own words. Markdown works: headings, bullets, inline code.
- Tags. Optional. Topics this memory relates to. Helps search and grouping.
- Advanced > Valid until. Optional auto-expiry date. Leave blank to never expire.
Save
Click Save memory. The new entry lands at the top of the live list, scoped to this Project.
Approve a candidate
Candidates appear when an analyst correction in chat surfaces a fact worth keeping, or when the agent itself proposes one mid-conversation. Approval is the moment a candidate joins every future answer.
Open the proposal
Click a row with the Pending review badge. The drawer shows the proposed body, tags, scope, and a "Proposed" timestamp with the Learned provenance chip.
Read what would change
For an add or update, the drawer renders the proposed markdown. For a delete proposal, the drawer says plainly that approving will remove the live memory.
Approve or withdraw
An admin on the Project can approve. If you proposed the memory, you can Withdraw your own proposal from the drawer footer.
Edit or retire a live memory
Open a live row to see the rendered markdown, tags, and any expiry. The drawer footer has two actions:
- Edit. Opens the form with the existing values. Save commits a new version and stamps an "Updated just now".
- Delete. Opens an inline confirm in the footer. Click Confirm to retire the memory. A toast names what was removed.
The Audit ledger captures every approve, edit, and delete. Filter /audit by the memory path when you need the receipt.
Promote to shared
A Project memory belongs to one Project and never leaks. A shared memory is available to every Project, App, and Data Collection in scope. Lift to shared when more than one Project benefits, or when the fact is about how your company refers to a concept.
Promotion is manual today. There is no one-click promote on a Project memory. To move one up, open Shared Context > Memories, author the same entry there, and delete the Project-level original. See shared memories for the team and workspace flow, and shared versus project scope for the heuristic on when to lift.
How to think about memories
Memories are how you encode the small, durable facts your team already lives by: fiscal cutoffs, vendor naming, the way one term means two different things in two different teams. Keep them short. Keep them specific. The agent does the rest.