Team memories
How a team agent's learning becomes shared context
During a thread, a team agent learns that enterprise refunds require Finance approval. Once saved, that correction can guide the agent's future runs. It doesn't become guidance for every team agent until an Owner or Editor reviews and promotes it.
Learning starts with one agent and earns its way to the team
An observation can help the agent that made it immediately. It becomes team guidance only after an Owner or Editor reviews and promotes it.
Team memories are the reviewed policies, decisions, conventions, and facts that team-owned agents can use across their work.
Agent memory or team memory
A team-owned agent can draw from its own memories and the team's shared context. Keep learning with one agent when it belongs to that role; promote it when other team agents should rely on the same guidance.
Team memories
Reviewed context that team-owned agents can retrieve according to their knowledge settings.
This agent's memories
Context that belongs to one team agent. It can help that role without changing what the rest of the team relies on.
Manage shared context
Team memories live on the team's Workspace memories page. The list groups memories by owner and can be filtered by category, agent, audience, pinned, or archived.
Every team role can read shared memories. Owners and Editors add, edit, archive, and organize them; only Owners delete them permanently. See Team roles for the complete permissions matrix.
How learning becomes shared
The agent saves what it learned
Learning from a team agent starts in that agent's own memories. The new context can help the same role again without changing guidance for the rest of the team.
An Owner or Editor reviews it
They confirm that the memory is accurate, durable, and useful beyond the agent that learned it.
They promote it to Team memories
The same memory moves into the team's shared context. The originating agent can still use it, and promotion doesn't create a duplicate.
When the team already knows a policy or decision, an Owner or Editor can add it directly with + New workspace memory instead of waiting for an agent to surface it.
Promote or move a memory
Use the memory's actions menu to change who owns it. Both actions stay inside the team workspace.
Make reviewed learning shared
Move an agent-owned memory into shared context after it has been reviewed. The originating agent keeps access through the team memory.
Narrow shared context to one agent
Give a team memory to one agent when the context no longer belongs in shared guidance. Earlier agent links are cleared.
Neither action creates a copy or moves context into someone's personal library.
Personal context stays personal
A team-owned agent uses the team's context and its own memories, not the personal memories of whoever starts the run. A personal agent shared with the team keeps the same knowledge access it already had; sharing it doesn't open the team's memories or another person's private context.
Content history is not ownership history
Version history records edits to a memory's content. It doesn't record ownership changes such as Promote to Team memories or Move to an agent. Check the memory's current location to see who can use it now.
Related guides
- Memories explains memory fields, retrieval, editing, archiving, and the full ownership model.
- Knowledge access controls which memories an agent can retrieve and where it saves new knowledge.
- Manage learning behavior controls when an agent may suggest or save new memories.