Enable Cross-Conversation Referencing of Personal Threads in ChatGPT Teams
Summary
Allow the assistant to access and reference a user’s personal (non-project) conversations within the same ChatGPT Teams workspace, but only when explicitly requested and only by the user who owns those conversations.
Problem
Currently, personal and project threads in ChatGPT Teams are completely siloed. This limits continuity and flexibility for users who work across exploratory and structured spaces.
A user might generate useful research, frameworks, notes, or experiments in personal chats, but cannot reference or reuse them within a structured project thread unless they manually copy and paste that information each time.
This breaks the natural creative flow and creates unnecessary friction, especially for power users who depend on the assistant across multiple domains.
It should be noted that moving a personal conversation to a project doesn’t fix the problem as memory is silo’d at the conversation level in a workspace not at the project level. So it doesn’t matter whether the conversation is in or out of the project, the ability to access the conversation’s memory is still impeded.
Use Case / Context
I often develop ideas, prompts, or drafts in personal conversations before formalizing them in project work. For example, I might explore tone, draft phrasing, or define principles privately before applying them to a shared book project.
Today, I have to copy-paste that material manually into a new conversation and restate the context — losing time and continuity.
Allowing optional, scoped access to my own non-project threads within the same workspace would eliminate this problem without exposing anything to other team members.
Requested Behavior
This capability must be strictly user-owned and scoped — meaning that only the originating user can access, request, or authorize referencing of their personal conversations. No assistant memory or access should be shared with other users, workspace admins, or projects unless explicitly and individually granted.
- Add a feature that enables the assistant to:
- Access a user’s personal conversations within the same workspace
- Only when the user explicitly requests it (e.g., “use the tone guidelines I drafted in my personal thread from last week”)
- And only for that specific user’s own conversations (not anyone else’s)
Optional safeguards:
- A toggle or permission gate that users can enable/disable for this behavior
- Option to name/tag personal threads for easier retrieval (“Reference my ‘Tone Experiments’ thread”)
Implementation Notes (Optional)
This request does not require exposing personal chats to teammates, admins, or assistant memory across users. It simply adds contextual continuity for the same user, operating across different spaces in the same account.
This would mirror how:
- Notion allows users to pull in personal notes into shared pages
- Google Drive allows inserting personal documents into team folders (without moving them)
Visual Example
Impact / Priority
High.
This is a quality-of-life improvement for power users who rely on ChatGPT Teams for:
- Writing workflows
- Research + synthesis
- Prompt development
- Ideation + iteration
Without this, the platform discourages cross-pollination of ideas and splits creative flow across disconnected contexts. Enabling scoped self-referencing would make ChatGPT significantly more usable and intuitive for project-minded professionals working at scale.