When a conversation starts in normal Chat and later needs Work or Codex, ChatGPT currently creates a separate workspace or conversation.This creates several practical problems.
First, the new Work or Codex session may not fully carry over the entire conversation history, decisions, uploaded files, instructions, and context from the original Chat.
Second, the user has to manually summarize or transfer important information from the previous conversation.
Third, the sidebar becomes cluttered with multiple entries that are actually part of the same project or task.
I would like ChatGPT to keep one continuous conversation thread and allow the execution mode to change within that same conversation.
For example:
Chat → Work → Codex → Chat
Only the capabilities or execution environment would change, while the full conversation history, uploaded files, prior decisions, instructions, and project context remain intact.
A typical workflow could look like this:
-
Start in normal Chat to discuss an idea, strategy, technical issue, or business decision.
-
Switch the same conversation to Work when web browsing, file handling, document creation, or multi-step execution is needed.
-
Switch the same conversation to Codex when programming, debugging, terminal work, or software development is required.
-
Return to normal Chat afterward for discussion, review, or further planning.
The important point is that this should all remain inside one continuous conversation instead of creating separate chats.
Ideally, the sidebar should also show only one conversation for that project, even if the user switches between Chat, Work, and Codex multiple times.
This would reduce duplicated chats, eliminate manual handoffs, preserve context more reliably, and make ChatGPT feel like one unified assistant rather than several separate tools.
A related improvement would also be helpful:
If a user discusses a product issue or feature idea with ChatGPT, the user should be able to say something like:
“Submit this discussion as product feedback.”
ChatGPT could then prepare the exact feedback text, show it to the user for review, and after explicit approval, submit it directly to the product feedback system.
This would make feedback more accurate because the full context has already been discussed and refined inside the conversation.