Problem
ChatGPT already supports “Branch in new Chat” and “Branch into Work mode," but there is an important destination missing: Projects.
Ideas often emerge in conversations where they do not originally belong. This is especially common during exploratory, research, creative, or highly associative workflows.
For example, I may be having a general conversation about OpenAI updates when one response develops into an important idea for an ongoing research Project.
I do not want to move the original conversation or stop it. I want to branch from that specific response and continue the new conversational thread inside the relevant Project.
Proposed feature
Add another destination to the existing Open new branch menu:
Open new branch
- Branch into Work mode
- Branch in new Chat
- Branch into Project → [Select Project]
The new branch would:
- Preserve the conversational context up to the branching point;
- Leave the original conversation completely unchanged;
- Create a new conversation inside the selected Project;
- inherit that Project’s instructions, files, and context;
- remain independently continuable from that point;
- clearly show its origin, e.g. “Branched from: [original chat]”, with a link back to the source conversation.
Why this is different from “Move to Project”
Moving a chat reorganizes an existing conversation.
“Branch into Project” would instead allow a new line of thought to be captured at the moment it emerges, while the original conversation continues normally.
This is particularly useful for users whose work is associative: an important idea may emerge while discussing something completely different. The user should not have to interrupt the conversation, manually create a Project chat, copy context, and reconstruct why the idea mattered.
The conversation itself already contains that context.
Why it fits the existing UI
Most of the interaction model already exists. ChatGPT already presents an Open new branch submenu with different destinations. Projects would simply become another destination for a branch.
Conceptually:
Conversation A → response → continue Conversation A
↳ Branch → Project X → continue there
This would make Projects substantially more useful as persistent knowledge/work spaces rather than requiring users to know in advance where every useful conversation is going to lead.
Related UX improvement
Branched conversations should also be visually identifiable and traceable in history. A branch icon, “Branch” badge, parent-chat link, or similar indicator would make branches much easier to recover and understand later.