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 of the Project's memories. A search field above the list filters across title, body, tags, and path.
Who can change them
Each memory is saved and injected into agent context when relevant. The row shows the title, "Updated 5d ago", and any tags.
At Project scope there are no proposals to review. A builder on the Project writes memories directly, from this section or through the agent in a conversation, and the change is live at once. Members can read the Project's memories but cannot change them, and the agent in a member's conversation cannot save one.
The drawer marks each entry with a Manual or Learned provenance 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.
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 create, edit, and delete. A workspace admin can 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 and Workflow 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.