memory-extraction

Automate memory extraction by triggering a process at conversation end that detects valuable data, categorizes it into project-level and user-level memory, and writes structured YAML memory entries for cross-agent synchronization.

Automated routing applies predefined classification rules to detected information, directing it into project-level memory (_omp/memory) or user-level memory (openmemory) based on the extracted data's context and scope.

Yes, Ruby and AJV are required dependencies to run the scripts that extract key information from conversations, code changes, and deployments into structured memory files across agent workflows.

Trigger memory extraction deterministically at the end of conversations or when valuable information is detected, ensuring decisions, preferences, and code changes are automatically saved without manual intervention.

The best way to maintain cross-agent context is using an automated extraction workflow that captures conversation data, categorizes it by classification rules, and synchronizes YAML memory entries across agents.

Yes, you can synchronize YAML memory entries across multiple agents by routing extracted information into shared memory and project-level memory, enabling consistent cross-project collaboration.