codex - 💡(How to fix) Fix Codex Desktop: support importing ChatGPT projects and chats

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Root Cause

Codex and ChatGPT currently feel like separate workspaces. Users who have already spent months organizing work in ChatGPT projects need a migration path into Codex. Without this, moving to Codex means manually recreating projects, copying chat context, and losing the original structure.

This would make Codex much easier to adopt as a long-term technical workspace.

Code Example

codex import chatgpt-export ./chatgpt-projects.zip

---

ChatGPT Project -> Codex Project / workspace root
ChatGPT Chat    -> Codex Thread
Chat title      -> Codex thread title
Attachments     -> project/thread files or outputs
RAW_BUFFERClick to expand / collapse

Feature request

Please add an official way to export ChatGPT projects/chats and import them into Codex Desktop.

Use case

Many users already have a large amount of useful work organized in ChatGPT projects. When moving serious technical workflows into Codex Desktop, it would be very helpful to bring over that existing structure instead of starting from scratch.

For example, a user may have ChatGPT projects such as:

  • Gadgets
  • Useful for Mac
  • Finance
  • DevOps
  • Docker
  • TypeScript + Vue.js
  • Design / reference generation

The desired workflow is:

  1. Export selected projects and chats from ChatGPT
  2. Import them into Codex Desktop
  3. Preserve project names and chat titles
  4. Preserve chat history, files/attachments where possible, and useful metadata
  5. Allow Codex to create corresponding local projects/workspaces
  6. Optionally allow Codex to classify ungrouped chats into projects by topic

Requested behavior

Please add one or more of these:

  • ChatGPT UI export option for selected projects/chats in a Codex-compatible format
  • Codex Desktop import option for a ChatGPT export archive
  • CLI command:
codex import chatgpt-export ./chatgpt-projects.zip
  • Ability to import:
    • all projects
    • selected projects
    • selected chats
    • ungrouped chats

Import mapping

An import could map ChatGPT concepts to Codex concepts like this:

ChatGPT Project -> Codex Project / workspace root
ChatGPT Chat    -> Codex Thread
Chat title      -> Codex thread title
Attachments     -> project/thread files or outputs

For projectless or ungrouped chats, Codex could offer:

  • keep as projectless imported chats
  • put them under an "Imported from ChatGPT" project
  • classify them into existing/new projects by topic

Why this matters

Codex and ChatGPT currently feel like separate workspaces. Users who have already spent months organizing work in ChatGPT projects need a migration path into Codex. Without this, moving to Codex means manually recreating projects, copying chat context, and losing the original structure.

This would make Codex much easier to adopt as a long-term technical workspace.

Environment

  • ChatGPT projects in the ChatGPT app/web UI
  • Codex Desktop on macOS
  • Codex app version: 26.527.31326

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Codex Desktop: support importing ChatGPT projects and chats