Skip to main content
Phase 3. Memory ships alongside multiagent orchestration.
Memory gives an agent knowledge that outlives a single session. A memory store is a set of versioned documents you mount into an agent; the agent reads them for context and can propose updates, which you version like any other document.

​
Memory stores

A memory store is an independent, organization-scoped resource — like skills, it is unaffected by session deletion. The difference: skills are authored expertise you push; memory is knowledge that accrues from the agent’s work.
CLI

​
Mounting into an agent

TypeScript
Mounted documents load with the same progressive-disclosure discipline as skills, so a large memory store never floods the context window — the agent pulls only what a task needs.

​
Versioning

Every write creates a new version. An agent’s proposed update is a version you can review, so memory is auditable rather than a silent mutation.

Next: outcomes & graders

Score a session against a rubric.