Author shared memories
Every team has small, durable facts the agent should already know. "Our fiscal year ends June 30." "Line 3 runs at 80% capacity in winter." "Customer Acme uses a different SKU naming convention." Shared memories put those facts in front of every Project and Workflow in your workspace.
You are not training the agent. You are encoding what your team has agreed is true.
Audience: builders
Find shared memories
Open the tools and settings menu and select Shared Context under Data & Context. The page is one overview of everything shared in the workspace: Skills, Verified Logic, and Memories.
- Scope filter. Pick All, your team, Workspace, or Built-in to narrow the overview. Team memories apply to everyone on your active team. Workspace memories apply to every team in the tenant.
- Search. Type in the Search shared context box to filter every section at once.
- Waiting for review. One queue lists the proposals for Skills, Verified Logic, and Memories together, oldest first.
- Memories. The section lists each live memory with its scope, its status, and when it was last updated.
Click a row to open its details in a drawer over the overview.
Read the two states
Every shared memory lives in one of two states.
- Live. Published and injected into agent context when relevant. Its row on the overview shows when it was last updated, and its drawer shows its tags.
- Pending review. A proposal someone or the agent surfaced through a conversation. It is listed in Waiting for review on the overview, with Memory as its kind and the time it was proposed.
Live memories carry a Manual provenance chip in the drawer when a person authored them, or a Learned chip when the agent proposed them and a reviewer approved them. The chip is your at-a-glance answer to "how did this memory get here?".
Approve a candidate
Candidates appear in the Waiting for review list whenever a correction in a conversation surfaces something worth keeping, or when the agent itself proposes a memory mid-conversation. Approval is the moment a candidate becomes part of every future answer.
Open the proposal
Click the row under Waiting for review. The drawer shows the proposed body, tags, scope badge, and a "Proposed" timestamp.
Read what would change
For an add or update, the drawer renders the proposed markdown. For a delete proposal, the drawer says it plainly: approving will remove the live memory.
Approve, reject, or withdraw
Workspace builders and admins approve workspace candidates. Builders and admins of the active team approve team candidates. The person who proposed the memory can withdraw their own proposal. Each action ends with a toast and the proposal leaves the queue.
Who can approve. Workspace scope: workspace builders and admins. Team scope: builders and admins of the active team. Members can view the list and propose, but only builders and admins act.
Author a memory directly
When you already know the fact, write it yourself instead of waiting for a candidate to emerge.
Open the create drawer
Click New in the page header, then Memory. The drawer opens with a blank form titled "New team memory" or "New workspace memory". The memory goes to your team when you can write team memories directly, and to the workspace otherwise.
Fill the form
- Title. Searchable and shown in the row list.
- Body. Plain language. Markdown is supported: headings, bullets, inline code.
- Tags. 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 memory lands live in the scope the form title names.
Edit or retire a live memory
Open a live row to see the rendered markdown, tags, and any expiry date. Builders and admins see two actions in the drawer footer:
- Edit. Opens the same form with the existing values. Save commits a new version. The relative timestamp updates.
- Delete. Asks for inline confirmation in the footer, then retires the memory. A confirmation toast names what was deleted.
The Audit ledger captures every approve, edit, and delete. Filter /audit by the memory you care about when you need the receipt.
Project memories versus shared memories
A project memory belongs to one Project and never leaks. A shared memory is available to every Project and Workflow in scope. Keep something in the Project when it is specific to one workflow; lift it to shared when more than one Project benefits or the fact is about how your company refers to a concept. See Shared versus project scope for the heuristic and Project memories for the per-Project flow.