Codex CLI Adds Instant Conversation Forking
CodexCodex CLI 0.157.0 introduced an f keyboard shortcut that instantly forks a conversation that is currently open in another Codex surface, branching it into a new session while preserving in-progress drafts and any queued prompts. The feature lets developers try an alternative approach or ask a side question without disturbing or losing the original session's state. It builds on Codex's existing thread-management tools, following earlier additions like /side conversations, thread pinning, and paginated thread history.
Key Takeaways
- A single "f" keystroke now forks any conversation open in another Codex surface, instantly branching it into a new session.
- Drafts and queued prompts carry over to the forked conversation, so no in-progress work is lost when switching contexts.
- The feature targets a common workflow pain point: trying an alternative approach without disturbing the original session.
- It shipped inside Codex CLI 0.157.0, alongside GPT-6 Sol and Luna support and a default fullscreen terminal UI.
- Early adopters on the OpenAI Developer Community forum flagged intermittent reliability issues with fork-related commands right after the update.
- The shortcut extends Codex's growing thread-management toolkit, following earlier additions like
/sideconversations and persistent thread history.
Sources & Mentions
2 external resources covering this update
Fork a Conversation With One Keystroke
Codex CLI 0.157.0 added a simple f shortcut that forks a conversation open in another Codex app surface into a brand-new session. Instead of manually starting a fresh thread and losing track of what was in progress, a developer can now branch off mid-task and keep working on an alternative path, while the original conversation stays untouched.
What Gets Preserved
The fork keeps whatever was already in flight: any unsent draft text sitting in the composer, and any prompts that had been queued up but not yet sent, both carry over into the new forked session. This matters because previously, switching to a different line of exploration risked losing that in-progress state entirely.
Why It Matters
Codex users frequently want to try a different approach to a problem, or ask a quick side question, without derailing the main session they are already invested in. The f shortcut turns that into a one-key action rather than a multi-step workflow of manually copying context into a new thread. It extends a pattern Codex has been building out over recent releases, including the /side ephemeral-conversation command and persistent, searchable thread history, into a faster, more direct interaction.
Rollout Notes
The feature shipped as part of Codex CLI 0.157.0, the same release that brought GPT-6 Sol and Luna model support and made the fullscreen terminal UI the default view. Shortly after release, some users on OpenAI's developer community forum reported inconsistent behavior with fork-related commands, which is typical for a feature in its first days of general availability.
Other Changes in 0.157.0
The release also shipped a handful of smaller fixes: voice conversations now persist correctly across thread switching, unsent answers are recovered into the composer when a turn ends, proxy routing was corrected for realtime and web search connections, file uploads gained a longer retry window, and network policy enforcement was tightened across redirects.