Stronger task-thread continuity across related follow-up questions

What variant of Codex are you using?

CLI

What feature would you like to see?

I’d like Codex to maintain stronger continuity across an active task, instead of optimizing too heavily for the latest user message only.

In longer planning and architecture sessions, I often ask several follow-up questions that are all part of the same design decision. Right now, Codex often answers them one by one in isolation, and keeps shifting the proposed next step around the latest sub-question.

What I want instead:

- detect that several consecutive questions belong to the same active task
- merge related follow-up questions into one coherent decision when appropriate
- return to the current main task by default, unless the new question truly changes direction
- update execution plans as full deliverables, instead of patching one small section per turn

This is not mainly about verbosity. It is about continuity, task awareness, and better consolidation of related turns.

### Additional information

This is especially noticeable in real planning work.

Example pattern:
1. I ask about request IDs.
2. Then I ask about retention strategy.
3. Then I ask about identifier mapping.
4. All of these are part of the same implementation decision.

Instead of consolidating them into one finalized design update, Codex often answers each turn locally and changes the “next step” around the most recent message.

As a result:
- I have to repeatedly pull the conversation back to the active task
- I have to restate how several sub-questions relate to each other
- plan documents get updated incrementally in a fragmented way

A mode or heuristic that favors “complete the current task thread” over “respond locally to the latest prompt” would be a major usability improvement.