›_ Codex Issues
Codex Issues / #25387

Codex Desktop: support importing ChatGPT projects and chats

Open 💬 2 comments Opened May 31, 2026 by Sereja3578
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

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

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 2 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #25385

Powered by Codex Action

cormierconsulting · 1 month ago

Just dropping this comment out of the entertainment value of their own system "agreeing" about a better solution for projects and managing them including importing them from gpt classic. it even linked me right here.

`The feature I'd love to see

Rather than just "Import Projects", I'd take it a step further:

Clients
│
├── Client A
│ ├── Kubernetes
│ ├── Redis
│ ├── Proxmox
│ ├── LoadBalancer.org
│ └── Development
│
├── Client B
│ ├── Infrastructure
│ ├── Development
│ └── Meetings
│
├── Personal
│ ├── Home Lab
│ ├── Finances
│ └── Travel
│
└── Archive

Each folder would contain:

Projects
Chats
Files
Memories scoped to that client
Shared instructions
Connected repositories
Connected cloud drives

That would make ChatGPT feel much more like a true knowledge workspace.

Even better

I'd love to see Projects gain metadata like:

🏢 Client
📁 Matter / Engagement
🏷 Tags
⭐ Favorites
📦 Archive
👥 Team sharing
🔒 Separate memories per project

As a consultant, I'd want to switch into Propago and have ChatGPT automatically know:

the Kubernetes cluster,
Proxmox hosts,
naming conventions,
Redis topology,
coding standards,

without that context bleeding into another client's workspace.

That kind of client isolation would be a huge productivity boost.

Interestingly, there are already public feature requests asking for official import of ChatGPT projects/chats into the new desktop/Codex experience, because many people have years of organized work they'd like to preserve rather than recreate.

Given the amount of backlash over the rollout, I wouldn't be surprised if OpenAI improves the organization story fairly quickly. The biggest complaints right now aren't about the new AI capabilities—they're about discoverability, navigation, and the lack of a smooth migration path for long-time users.

As someone who's done a lot of consulting, I also think a simple client → project → conversation hierarchy with optional tags would scale much better than a flat list of Projects. It would make switching contexts between companies far less error-prone and much easier to manage over time..`