Add an exit path from local Codex threads to cloud Chat

What variant of Codex are you using?

Desktop App (macOS) with local projects, MCP servers, and Work/Codex

What feature would you like to see?

Summary

Please add a one-click way to preserve a local Codex thread as a standard cloud Chat conversation, ideally within the same Project.

Option A (Preferred): Duplicate to Chat

Add a "Duplicate to Chat" action that:

• Creates a new cloud Chat containing the complete conversation history.
• Keeps the original local Codex thread unchanged.
• Associates the new Chat with the same Project.

Option B: Convert to Chat

Allow a local Codex thread to be migrated into a standard cloud Chat while preserving its history.

Why this matters

Local Codex conversations often become long-running project documentation containing design decisions, troubleshooting history, implementation notes, and accumulated context.

Today there is no supported way to continue that work in standard ChatGPT without manually recreating the conversation.

Users need an exit path when they:

• Reach Work/Codex usage limits.
• Decide to stop using Codex.
• Want to continue in the browser or on another device.
• Want their work preserved as part of their cloud Chat history.

A "Duplicate to Chat" action would preserve the local-first architecture while providing a seamless transition back to standard ChatGPT without losing accumulated context.

Background

I initially believed I was continuing the same project conversation because both ChatGPT and Codex surfaced the work under the same Project. It wasn't obvious that I had transitioned into a local-only conversation until I later discovered the thread was no longer available as a standard cloud Chat.

The separation makes sense, but there is currently no supported way to intentionally move back from a local Codex workflow into a standard cloud Chat once a conversation has become valuable project documentation.

This request is specifically for an exit path—not a change to the local-first architecture.
This request comes from using Codex for long-running ServiceNow development with MCP servers and local projects, where individual conversations evolve into valuable project documentation rather than short-lived coding sessions.
This would be similar in spirit to "Export to Chat" or "Duplicate to Chat"—a deliberate, user-initiated action rather than automatic synchronization.

Additional information

_No response_