Quick Start
Configuration Options
MultiAgentMemoryConfig SDK Reference
Full parameter reference for MultiAgentMemoryConfig
| Option | Type | Default | Description |
|---|---|---|---|
user_id | str | None | None | Scope memory to a specific user or project |
embedder | Any | None | None | Embedder configuration (e.g., {"provider": "openai"}) |
How It Works
| Phase | What happens |
|---|---|
| 1. Store | First agent saves discoveries to shared memory |
| 2. Retrieve | Subsequent agents access all stored context |
| 3. Build | Later agents build on earlier agents’ work |
Configuration Options
Full list of options, types, and defaults —
MultiAgentMemoryConfig| Option | Type | Default | Description |
|---|---|---|---|
user_id | str | None | None | Shared user/project identifier for scoped memory |
embedder | Any | None | None | Embedder configuration for semantic memory |
config | dict | None | None | Memory provider configuration |
Common Patterns
Pattern 1 — Project-scoped research memory
Best Practices
Always set user_id for project isolation
Always set user_id for project isolation
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.Order tasks to build context
Order tasks to build context
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.
Related
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

