Feature Request: Version Control for Codex Threads

What variant of Codex are you using?

Codex app for macOS

What feature would you like to see?

Summary
Introduce version control for Codex conversation threads so users can revert not only the generated code but also the conversation state that produced it.

Problem
When iterating with Codex, the conversation context strongly influences the generated code. If a later prompt introduces mistakes or an unhelpful direction, reverting the code alone is often insufficient because the conversation history still contains the prompts that led to the undesired state.

Currently, users must either:

• manually reconstruct earlier prompts, or
• restart a new conversation thread.

This breaks iterative workflows and slows down experimentation.

Proposed Solution
Add a versioning system for Codex threads that allows users to:

• revert a thread to a previous state (prompt + response history)
• branch from an earlier point in the conversation
• view a timeline of conversation states similar to commits

Example capabilities:

• “Revert thread to this step”
• “Create branch from here”
• “Compare thread states”

Possible UI ideas

• commit-like checkpoints for conversation turns
• a timeline or tree view of thread history
• ability to fork a conversation branch

Example workflow

1. User builds a feature with Codex across multiple prompts.
2. A later prompt causes the model to refactor the code incorrectly.
3. User selects a previous conversation step.
4. The entire conversation state (not just the code) is restored or branched.

Benefits

• safer experimentation
• faster iteration cycles
• easier debugging of prompt-driven development
• improved reproducibility of code generation sessions

Additional Note

This concept may also benefit ChatGPT more broadly, especially for coding workflows where conversation context acts as an implicit development environment.

Additional information

_No response_