ag2-memorysync

MemorySync for AG2 (the classic AutoGen ConversableAgent framework, pip install autogen): an automatic memory loop — recall injected before every reply, both sides persisted, zero extra code per turn.

pip install ag2-memorysync

Quick start

from autogen import ConversableAgent
from ag2_memorysync import MemorySyncCapability

assistant = ConversableAgent("assistant", llm_config=...)

memory = MemorySyncCapability(
    api_key="ms_...",              # or MEMORYSYNC_API_KEY
    user_id="customer-42",         # required — who these memories belong to
    session_id="support-chat",     # scopes the transcript
)
memory.add_to_agent(assistant)     # that's the whole integration

From then on every incoming user message is persisted and enriched with recalled context, and every outgoing reply is persisted — through AG2's own hook system (process_last_received_message + process_message_before_send).

Why this one

Semantics worth knowing

• The reply is never stalled and never broken. Recall blocks at most recall_timeout (default 1.2s); persistence is fire-and-forget off the hot path. Outages and quota exhaustion degrade to "no memories this turn".
• Turns store verbatim under the ag2::<session> transcript scope with deterministic idempotency seeds — retries and multi-agent echoes converge on one stored row.
• Tool/function messages are never persisted.
• register_memory_tools(memory, caller=..., executor=...) adds search_memory + save_memory tools (the caller needs an llm_config, as usual for AG2 tools).
• memory.flush() waits for in-flight writes (shutdown/tests); memory.close() flushes and releases the HTTP client.

Configuration

Development

pip install -e . "autogen[openai]" pytest
python -m pytest tests -q      # 22 tests through REAL ConversableAgent chats

The suite includes a reproduction of zep-ag2's documented multi-agent double-store scenario (we store once) and a chat driven from inside asyncio.run() (no deadlock).

License

MIT