Feature Request: Restore the independent conversation toggle for Legacy Memory / Disable background profile synthesis

I am writing to request the return of the toggle that allows users to maintain strictly independent conversations while using the Legacy Memory system.

The current system automatically runs background profile synthesis (cross-chat memory compilation) across separate conversations. This makes chats dependent on each other, causing data bleed and context contamination across unrelated workflows.

For users managing distinct projects, clients, or tasks, the loss of true chat isolation severely disrupts productivity. Relying on “Temporary Chats” is not a viable long-term solution, as users still need to save individual histories without having them blended into a single global profile.

Please restore the option to keep individual conversations completely insulated from the global background memory system.

Hey Kyle_Marks, welcome to the forum!

I agree that would be a valuable addition. Thanks for taking the time to share your idea and explain the use case.

I'll pass this feedback along to the product team so they can review the request and decide whether it's something they'd like to implement.

Avinash