A Major Codex Pain Point (Very Urgent!) (Before context auto-compaction is triggered, users cannot start a new conversation based on the current one)

What variant of Codex are you using?

App

What feature would you like to see?

A Major Codex Pain Point (Very Urgent!) (Before context auto-compaction is triggered, users cannot start a new conversation based on the current one)

1. Current problem: frequent auto-compaction seriously hurts long-running tasks

The context capacity of a single Codex conversation is still too limited. Long-running tasks can easily trigger auto-compaction. Auto-compaction not only takes a noticeable amount of time, but after multiple rounds of compaction, the conversation context becomes increasingly complex, messy, and noisy. This seriously affects Codex’s efficiency and quality when continuing unfinished tasks.

1. Starting a new conversation manually loses important context

If the user manually starts a new conversation, all previously accumulated context is lost, including task background, key decisions, project constraints, user preferences, and unfinished plans. The user has to explain a large amount of information again, which significantly increases communication cost and breaks task continuity.

1. Suggestion: support “start a new conversation based on the current conversation”

Please add a button under the input box, such as “Start a new conversation based on this conversation”. The user should be able to use it at any time. When starting the new conversation, the user can describe the next task or plan, and Codex should automatically extract only the context that is closely related to that future task, along with valuable long-term context, and carry it into the new conversation window.

1. Only migrate relevant context, without triggering auto-compaction again

When starting a new conversation based on the current one, Codex should only migrate context that is relevant to the user’s next task. It should not perform another auto-compaction step. This would prevent unrelated noise from being carried into the new conversation and make the new conversation clearer, more focused, and better suited for continuing the task.

1. Auto-compaction should not be a hard-triggered mechanism

Please add an “Auto-compaction” toggle under the input box. Auto-compaction should only be triggered automatically when this toggle is enabled. Users should also be allowed to temporarily turn it off. When it is turned off, even if the context is close to the limit, Codex should not auto-compact automatically. Instead, it should preferably prompt the user to choose whether to start a new conversation based on the current one.

1. Expected benefit

This feature would allow users to continue tasks smoothly in a new conversation window while preserving truly valuable context, including user preferences, writing style, relevant historical discussion, project constraints, and future task plans. It would also avoid the noise accumulation caused by repeated compaction in old conversations. Overall, this would significantly improve Codex’s continuity, efficiency, and work quality when handling long-running, complex, and multi-stage tasks.

Additional information

_No response_