Skip to content
Memory

Agents remember. You decide what stays.

What matters carries from one conversation to the next, for the right person, team or run.

A nurse on a night shift, looking out of a hospital window
MemoryUser

Prefers handover notes as short bullet points.

  • Learned from a conversationTuesday
  • Changed onceHistory
KeepForget

Memory with manners.

Kept where it belongs, recalled when it helps, gone when asked.

  • Scoped to the right place.

    An org, a workspace, a store, a user, an agent or a single run.

  • Between conversations.

    Learned from what was said, recalled when it helps.

  • Forgets on request.

    Delete a memory, or let retention rules expire it.

The details.

  • Learned from conversationsMemories are extracted as agents talk.
  • Memory documentsWrite down what an agent should always know.
  • Full historyEvery change to a memory is kept.
  • Retention rulesDecide how long memories last.

Where Memory sits.

One stack, from the agent to the ground it runs on.

Runs where you run.

From the public cloud to networks sealed from the world.

  • Scoped recall
  • Full change history
  • Forget on request

Questions.

What does Memory keep?

What agents learn from conversations, and the memory documents you write for them.

Who can recall a memory?

Only its scope: an org, a workspace, a store, a user, an agent or a run.

Can a memory be deleted?

Yes. Forget it on request, or set retention rules that expire memories.

Can I see how a memory changed?

Yes. Every memory keeps a full history of its changes.

An engineer replies in a dayTalk to us Docs, SDK and APIStart building