Skip to content
Ren Docs
Book a demo

Memory stores

A memory store gives an agent durable recall across sessions: preferences, decisions, conventions, accumulated knowledge. Without it, every session starts from a blank slate.

You could use file stores for this, but memory stores are built for retrieval: they support semantic search and selective loading into context, so an agent can recall what’s relevant without dragging everything into the prompt.

Memory scopes

Memory stores come in three scopes, each answering “who needs to remember this?”:

  • Org memory is shared across the whole organization. Company-wide knowledge: style guides, architectural decisions, team conventions. Every agent can read it.
  • Pod memory is private to one person’s workspace. Personal preferences, task history, notes only your agents see.
  • Project memory is scoped to a project. Domain-specific context: what a codebase looks like, what conventions a repo follows. Visible to every agent in that project.

New organizations and users get a default memory store automatically, so agents have somewhere to write from the first session.

How agents use it

When a session starts, Ren resolves the relevant memory stores (the org default, your personal default, and any attached to the project) and makes them available in the sandbox. Small stores can be loaded directly into the agent’s context; larger ones are queried on demand, keeping the context window lean while still giving full access.

A memory store can be shared across projects, and a project can mount several. So an org-wide store might be attached everywhere, while each project also keeps its own domain-specific store.

Memory stores vs. file stores vs. vault

  • File stores are a shared drive for artifacts: code, documents, datasets.
  • Memory stores are an agent’s long-term memory: retrieval-optimized recall.
  • Vault is a safe for secrets: API keys, tokens, credentials.

Put an API key in the vault, a codebase in a file store, and the things an agent needs to remember in a memory store.

CLI commands

Terminal window
ren memory-stores create --name "Team Conventions"   # create a store
ren memory-stores list                               # list stores in your org
ren projects memory-stores add <projectId> \
  --memory-store-id <memoryStoreId>                  # attach to a project