ChatDev 2.0 + MemorySync

Overview

Install chatdev-memorysync inside a ChatDev 2.0 (DevAll) checkout and `type: memorysync` joins the platform’s memory registry — usable from workflow YAML and the web console’s store-type dropdown, activated automatically by a .pth hook that no-ops outside ChatDev. The store is engineered against the in-tree Mem0 store’s failure modes: user_id is a REQUIRED config field (Mem0’s demo hardcodes a shared id so every operator shares one partition); recall runs under a hard 1.2s budget and fails open with status-bearing logs (Mem0’s SDK call has NO timeout — a slow backend stalls the whole agent turn — and its bare error logging makes quota, auth, and network failures indistinguishable); retrieved items carry the row’s real created_at (Mem0 stamps everything time.time(), corrupting ChatDev’s own time-decay scorer, which weights age at 0.7); agent outputs persist role-labeled (Mem0 throws them away); deterministic seeds make retried writes converge (Mem0 re-extracts duplicates). similarity_threshold is honored on real scores and multimodal attachment overviews are recorded. Memories flow to and from every other MemorySync surface.

Setup status and requirements

Supported version

chatdev-memorysync 1.0.0 (PyPI)

Last setup review

2026-08-24

Permissions

A MemorySync API key with read and write scopes.

Limits

Requires a ChatDev 2.0 (DevAll) checkout (Python 3.12).

Capabilities

• Config-driven: type: memorysync in YAML + the web console dropdown — zero code
• Automatic .pth activation; safe no-op outside ChatDev (subprocess-tested)
• user_id REQUIRED — no shared demo partitions
• Hard 1.2s recall budget, fail-open with status-bearing logs
• Honest created_at timestamps — plays fair with ChatDev’s decay scorer
• Both sides persist, role-labeled; server-side gating handles noise
• Deterministic idempotency seeds — re-runs converge
• similarity_threshold honored on real scores; attachments recorded

Quick Start

graph:
  nodes:
    - id: writer
      type: agent
      config:
        memories:
          - name: user_memory
            top_k: 5
            retrieve_stage: [gen]
  memory:
    - name: user_memory
      type: memorysync
      config:
        api_key: ${MEMORYSYNC_API_KEY}
        user_id: customer-42

Use Cases

Explore More