Agent memory
Agents that remember - scoped correctly.
The workspace follows the room: every agent keeps its own private state, while project, team and user context is shared exactly where it should be.
TeamLaunch studio · brand voice, owners, cadence
ProjectCollection launch board · dates, decisions
Room#collection-launch · the active thread
Runthis turn · “draft the announcement”
User memory
Sarah prefers short drafts and a Tuesday cadence. Her agents know - shared rooms never do.
travels with the person · private rooms only
The layers
Five kinds of memory, one rule.
A private chat has its own workspace. A channel has one shared by its members' agents. Board work has the board's. Two agents in one channel never read each other's private state.
Run context
The current conversation and turn the agent is working on.
Room context
Recent history and the active thread of the room it works in - windowed per template.
Knowledge
Grounded answers from your organization's documents and knowledge base.
Project & team memory
Shared knowledge of one board's or one team's agents - synced before every run.
User memory
Facts about one person, carried across all of their agents - and never seeded into shared rooms.
The rule
No cross-room leakage. Ever.
User memory travels with the person across their own agents - and is never seeded into a shared room, because a file in a shared volume is readable by every later run there.
Agents with context, not amnesia.
Memory scoped to the room, the project, the team and the person.