Quick summary: Group Chat memory moved from a shared, ambiguous model to per-companion control. Each member can now use private memory or a selected Memory Group, and a later release fixed an editing issue that could reset those assignments.
The original rollout separated each member’s memory
The v5.8.0 release added memory saving inside Group Chats and allowed a separate Memory Group for each companion. The changelog explicitly says memories were no longer shared between members by default. That distinction matters because a group conversation can contain companions with different histories and different privacy needs.
A user can connect one companion to an existing storyline while leaving another on private group-only memory. The current Wiki describes this as a per-member setting, not one global switch for the entire group.
AI Video Gallery
A preview of selected portrait videos and AI character images.
Private memory and shared groups solve different problems
- Private memory: information stays inside that group conversation for the selected companion.
- Shared Memory Group: the companion can carry relevant memory between the group and other chats assigned to the same group.
- Mixed setup: different companions in the same group can use different scopes.
Use the comparison of private chat memory and shared Memory Groups before linking an established storyline. The assignment is per companion, so labels should describe the storyline rather than the room as a whole.
The later edit fix addressed a specific failure
The v5.11.0 notes describe a major bug where editing a Group Chat could reset individual member memories. The same release says affected groups were fixed and hidden memories should become visible again. This was a correction to stored configuration, not a promise that every recall problem was eliminated.
After editing a group, open its settings and verify each member. When the saved scope is missing or recall changed unexpectedly, follow the diagnostic path for member memory that reset after a group edit.
What users should check before continuing a storyline
- Confirm the correct companions are in the group; changing membership requires a new group in the current workflow.
- Check the memory scope shown for every companion rather than assuming one selection covers all members.
- Keep an important storyline on a clearly named Memory Group and avoid creating near-duplicate groups.
- Test recall with one precise fact per companion before writing a long scene.
Why the update matters beyond bug fixing
Per-member memory makes Group Chats more controllable, but it also adds configuration that users can misread. the current Group Chat setup for members, images, calls, and memory explains the live workflow. SecretOpedia’s Secrets AI group-conversation update analysis keeps the historical rollout separate from current instructions.
The current documentation adds one important operational limit: once a Memory Group is assigned to a companion in an existing Group Chat, that assignment is locked. A different storyline may therefore require a new group rather than repeatedly editing the old room. This protects continuity but makes the initial scope choice more consequential.
the earlier Multiple Chats and Memory Groups release analysis explains where shared scopes came from. For wider plan context, the Secrets AI review’s evaluation of group features and memory controls helps determine whether the added setup complexity is useful for the reader’s intended workflow.
Official sources checked July 12, 2026: Changelog, Group Chats, Multiple Chats, Memory System.
