Feature Request: Branch conversation from a previous message

What variant of Codex are you using?

CLI

What feature would you like to see?

Feature Request: Branch conversation from a previous message

Description

When iterating on prompts or requirements in a Codex conversation, users often refine the same idea multiple times (e.g., v1 → v2 → v3 → v4).

Currently, there is no built-in way to return to an earlier message and continue the conversation from that point with the same context.

Users must manually copy an earlier prompt and resend it, which breaks the natural conversation flow and loses the structural relationship between versions.

Problem

Example workflow:

1. Requirement v1
2. Requirement v2 (revision)
3. Requirement v3 (revision)
4. Requirement v4 (revision)

If the user decides that v2 is the best starting point, there is no way to continue the conversation from that message directly.

This makes iterative exploration of ideas difficult.

Expected Behavior

Allow users to:
Select any previous message in the conversation
Start a new branch from that message
Continue the conversation using that message as the context

Possible UX

Examples:

Branch from here
Continue from this message
Create new conversation from this point

Benefits

Better support for iterative prompt design
Easier experimentation with multiple solution paths
Cleaner workflow for requirement refinement
Reduced manual copy-paste

Related Concepts

Similar patterns already exist in:

Git branching
Document version history
ChatGPT message branching

Summary

Add the ability to branch a conversation from any previous message, allowing users to explore alternative directions without losing earlier context.

This would significantly improve workflows for prompt engineering,
requirement iteration, and technical discussions with Codex.

Additional information

_No response_