Taking memory shares back, and private sessions stay private
You can now revoke a memory share, and private conversations distill into their own scope instead of the whole org.
- You can take a shared memory back without deleting it. Revoke one share or all of them at once. The memory's author or an org admin can do this.
- Facts distilled from a private conversation now stay in that conversation owner's scope. Before, they became org-wide memories anyone in the org could recall. New orgs get this by default; existing orgs keep the old behavior until they change the distill_scope setting.
- Recall and think take an optional as_of time and answer from what the org held as current at that moment. This covers semantic and episodic memory.
- Orgs still on org-wide sharing see constraints shared with a single team in the org's constraints list again, as they did before targeted sharing.
- When a team, project, or user that a memory was shared with is deleted, or a member is removed from the org, those share rows are now cleaned up.
Sources: #1100, #1099, #1086, #1091, #1098.