mem0-pin

Pin a memory by searching for it with search_memories or providing its ID, then calling update_memory to prepend a [PINNED] marker to the memory text. The marker travels with the memory content so pruning logic can recognize and skip it.

Use the pin workflow to mark critical memories like architecture decisions or security constraints. Pinned memories carry a [PINNED] text marker and pinned metadata, protecting them from removal during dream consolidation pruning.

Yes. Call add_memory with the text prefixed by [PINNED], metadata set to pinned true and confidence 1.0, and infer disabled. Then call get_event_status with the returned event_id to retrieve the new memory ID.

Call get_memory to read the current content, remove the [PINNED] prefix from the text, and call update_memory with the cleaned text. The memory then returns to normal pruning eligibility.

The pin marker is stored inside the memory text itself, so it depends on the consolidation process respecting the [PINNED] prefix. If the memory text is rewritten by other operations without preserving the marker, the pin protection is lost.