Summary

• Skip mem0migrations vector store initialization when MEM0_TELEMETRY=false
• Applies to both Memory (sync) and AsyncMemory classes
• No behavior change when telemetry is enabled

Description

The mem0migrations vector store was always initialized in Memory.__init__() and AsyncMemory.__init__() regardless of the MEM0_TELEMETRY setting. This collection is used exclusively for anonymous telemetry (storing a user identity for event tracking).

When MEM0_TELEMETRY=false, the vector store was created but never used — capture_event() already returns early when telemetry is disabled. This caused unnecessary overhead:

• Remote vector stores (Qdrant Cloud, Pinecone, etc.): unnecessary network connections and collection creation on user's paid services
• Local vector stores (FAISS, Qdrant local): unnecessary directory creation and index initialization

The fix wraps the telemetry vector store initialization behind an if MEM0_TELEMETRY: check. The existing hasattr guard in capture_event() (telemetry.py:69) already handles the case where _telemetry_vector_store doesn't exist.

Closes #4200

Type of change

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

• Unit Test

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• My changes generate no new warnings
• New and existing unit tests pass locally with my changes