Please give users a reliable way to isolate conversations and projects from one another while still allowing access to Saved Memory.
If full thread isolation is not available, conversations from one project should at minimum never influence conversations in another project. Project instructions, uploaded files, corrections, decisions, and conversation-specific context should remain confined to the project or thread in which they were established.
Saved Memory should remain available across projects because it contains information the user has deliberately chosen to preserve. However, ordinary conversation history and project-specific context should not cross project boundaries unless the user explicitly permits it.
At present, users may have to move conversations into and out of projects configured with Project-only memory simply to minimise cross-project leakage as much as possible. This is tiring, inefficient, and often not practical at all. It wastes time, disrupts established workflows, and forces users to manage conversations manually just to prevent unrelated context from contaminating other projects.
Cross-project leakage can introduce unrelated information, assumptions, or instructions into the wrong conversation. This reduces reliability, creates confusion, and forces users to repeatedly correct context that should never have crossed over.
Users should be able to choose between:
-
An isolated conversation or project that uses only its own history, instructions, selected files, and Saved Memory.
-
A shared-context mode for users who intentionally want information carried across conversations or projects.
At the very least, project boundaries should function as hard context boundaries by default, with Saved Memory treated as the only account-level context shared between projects unless the user explicitly chooses otherwise.