Skip to main content
Multi-Agent Memory gives all agents in a workflow access to shared memory, so knowledge discovered by one agent is available to others.
The user runs a multi-agent workflow; all agents read and write shared memory under one user id.

Quick Start

1

Simple Usage

2

With Custom Embedder


Configuration Options

MultiAgentMemoryConfig SDK Reference

Full parameter reference for MultiAgentMemoryConfig
Precedence ladder:

How It Works


Configuration Options

Full list of options, types, and defaults — MultiAgentMemoryConfig

Common Patterns

Pattern 1 — Project-scoped research memory


Best Practices

Set user_id to a unique project or session identifier to prevent memory from bleeding between unrelated workflows. Without user_id, all workflows share the same memory namespace.
Tasks run in order by default. Place information-gathering tasks first and synthesis/writing tasks later so downstream agents have full context from upstream agents.

Isolating collections per agent

When several agents share one rag_db_path, give each a distinct collection_name so they coexist and can be reset independently.
collection_name defaults to "memory_store". See Memory Configuration.

Advanced Memory

Single-agent memory configuration

Multi-Agent Planning

Plan tasks before executing them

Multi-Agent Hooks

Intercept task lifecycle events

Learn

Continuous learning from conversations