Problem
Adding memories one at a time is inefficient for bulk ingestion (e.g. importing a knowledge base, backfilling from another system). No batch primitive exists in the Protocol — callers must loop and pay per-call overhead.
Proposed Solution / Alternatives
Add batch_add to the MemoryBackend Protocol. Backends that support native batch operations can override for efficiency; others get a default sequential loop. Enables future bulk workflows without requiring every backend to implement batch logic from scratch.
Problem
Adding memories one at a time is inefficient for bulk ingestion (e.g. importing a knowledge base, backfilling from another system). No batch primitive exists in the Protocol — callers must loop and pay per-call overhead.
Proposed Solution / Alternatives
Add
batch_addto theMemoryBackendProtocol. Backends that support native batch operations can override for efficiency; others get a default sequential loop. Enables future bulk workflows without requiring every backend to implement batch logic from scratch.