v1.2.2.dev3 — Fix memify user propagation

Release Date: 2026-07-07
Changes: v1.2.2.dev3 → fix-memify-user-propagation

Summary

This patch fixes how Cognee assigns user identity when converting content into stored memories. It ensures memories keep the correct user ownership to prevent misattribution and permission problems.

Highlights

• Memories now retain the original user's identity when created (fixes misattribution).
• Reduces risk of cross-user data leakage and permission mismatches.
• Internal ingestion logic tightened so user metadata is propagated reliably.

Improvements

• Corrected the memify flow so each memory (a stored record that Cognee uses for later search and recall) inherits the originating user's identity, ensuring queries and user-scoped filters behave correctly.
• Improved handling of user metadata during ingestion so missing or ambiguous user fields are less likely to produce incorrect results.
• Clearer failure behavior: when user metadata is absent, the system now preserves a traceable state instead of silently assigning the wrong user (so debugging is easier).

Security

• By ensuring user identity is preserved during memory creation, this release reduces the chance of accidental exposure of one user's data to another user via misattributed memories.

Bug Fixes

• Fixed a bug where memify (the process that converts an item, such as a message or document, into a stored memory) sometimes dropped or overwrote the originating user's identity, causing memories to appear under the wrong user or under no user.
• Fixed edge cases in imports/syncs where user assignment could become null or default to a system account instead of the real user.

Technical Changes

• Refined the internal memory ingestion pipeline to centralize user propagation logic so all ingestion paths consistently set the user field on created memories.
• Code-level cleanup around how user metadata is validated and passed through the memify step.

Compatibility

— The Cognee Team · 2026-07-07