ChatGPT integration

I'd love to be able to move a codex session over to ChatGPT to brainstorm and use web search features and so on in a nice UI when I'm just trying to research a task and experiment with ideas. And then bring the result of that (or of a chat I started in ChatGPT) into codex CLI easily so that I can then prompt it to take action based on that context.

Ideally this would be seamless with the macOS app.

Why do you love this discussion-less thread so much? You keep shutting down discussion to link your favorite thread. I guess it's easier than actually working on the solution.

@ChazWinterYT

@ChazWinterYT, we generally use upvotes to inform prioritization on the Codex team. If there are a dozen open issues that all speak to roughly the same feature, it dilutes the signal. This thread already has many upvotes, so if you'd like to discuss this feature, please comment in this thread rather than creating a new one.

Note that now my biggest use case for this would be to seamlessly bring the 5.2 Pro model in for helping with a Codex session, or for brainstorming with Pro first and then bringing that to Codex (so, either direction)

Bringing chats and projects from ChatGPT to Codex and vice-versa is essential. Right now the only way to do that is manually transcribing everything to bring it back and forth as context. Not ideal (and very time consuming) but it works.

I thought that once I am logged-in, Codex (VSCode ext.) would have access to my past ChatGPT chats and projects, but it doesn't. I have a full project where I am designing something new technically and ChatGPT offers me the kind of brainstorming (voice included) that Codex can't, that's why I use both and constantly switch back and forth but the UX would be much better if they are able to work together.

That's why both are needed to work more closely together IMHO.

Bringing chats and projects from ChatGPT to Codex and vice-versa is essential. Right now the only way to do that is manually transcribing everything to bring it back and forth as context. Not ideal (and very time consuming) but it works.

I thought that once I am logged-in, Codex (VSCode ext.) would have access to my past ChatGPT chats and projects, but it doesn't. I have a full project where I am designing something new technically and ChatGPT offers me the kind of brainstorming (voice included) that Codex can't, that's why I use both and constantly switch back and forth but the UX would be much better if they are able to work together.

That's why both are needed to work more closely together IMHO.

Yes. I agree, i also brainstorm in ChatGPT but have no way of having that context in codex seamlessly. Did you manually copy and paste between them to include the context in codex?

Just merge the memory/context of all of your products already. As users, we are here for the extended, long-form intelligence and memory that ChatGPT gives us. The fact that Codex, Images, ChatGPT and Pulse aren't just modalities of a common memory is a recipe for falling behind. Asking ChatGPT or a Pulse suggestion to go off and create a prototype is just natural. You shouldn't need upvotes to put this as number 1 on the feature sheet.

If this gets implemented, it would be nice if it didn't automatically happen, but was something I could opt into on a session-by-session basis.

+1
Interesting proposal! — I’d love this integration too!!

This would be especially helpful when I’m away from my dev setup (e.g., on the go, or even while traveling) — I often want to research and brainstorm in ChatGPT’s UI first(nice UI/UX, web search, etc.) , then later hand off the resulting context to Codex to execute when I’m back at a terminal/IDE.

I tried a workable stopgap with what we have today.
The ChatGPT → Codex direction is partially doable in a semi-automated way:

export your ChatGPT data (Select Settings → Data Controls → Export Data.)
extract the text for a single target conversation from conversations.json (easy with a small script),
and then paste/feed that text into Codex as context.
(cont...)

Adding a concrete use case here instead of opening another duplicate.

Uploaded Codex CLI feedback thread ID: 019d9a46-fe44-7491-91dc-7690b2298431

What I want is not just generic integration, but an intentional handoff flow in both directions:

start in ordinary ChatGPT when I am still exploring / researching / shaping the problem
promote that conversation into a Codex thread without manual copy/paste cleanup
keep a durable link between the ChatGPT discussion and the Codex thread
later query progress, summaries, and artifacts back from that same shared object

I am not asking for raw transcript mirroring. An explicit handoff capsule would be a much better design:

selected context
goals / constraints
linked artifacts
one durable reference that both ChatGPT and Codex understand

Related public discussion:
https://community.openai.com/t/feature-request-native-chatgpt-codex-thread-bridge/1379162

i can't beleive there is no movement on this.... hope it is soon. copy / paste is brain-dead.

Still no progress???

Still no progress???

they announced that the codex app is going away and will be consolidated into chatgpt. so wait for that to see.

yeah instead of integrating chatgpt into codex, codex should be merged into chatgpt. this will increase the codex usage more and agentic AI will be on default for all chatgpt app users.

they announced that the codex app is going away and will be consolidated into chatgpt. so wait for that to see.

Hopefully when they merge the two apps, they will have figured out how to merge the history, something they've not been able to do for 9 months according to this thread.

Adding a related reference, not an official OpenAI solution and not a proposed Codex PR: a friend pointed me to this independent MCP bridge that explores a similar workflow: https://github.com/velhud/PatchBay
It seems to cover part of this workflow: ChatGPT can coordinate local Codex CLI workers and receive reports/diffs/results back in the chat.

Still no progress???

they announced that the codex app is going away and will be consolidated into chatgpt. so wait for that to see.

like I said - it happened today

Solved in today's update now that they've replaced ChatGPT with Codex:

And so the monkey's paw finger curls... ChatGPT Work quota is shared with Codex quota 😔

@ignatremizov

@ignatremizov Chats are not though. nothing changed

Big +1. I'm constantly doing this. There should be a very easy way of saying to Codex:

Look at this ChatGPT conversation thread, perhaps emphasizing last messages. I want to implement what's described here ...

Currently I'm creating a shared link for the ChatGPT conversation thread, which I then give to Codex. But I think that's really not ideal, because then Codex attempts to curl the chat thread, which probably is not in an ideal format for it to consume. There really should be an easy way for Codex to consume ChatGPT conversations, with the ability to prioritize certain messages (so it doesn't fill context)

Ohh I see can you tell something about a recent task where you faces this problem??

Navigation Menu

Repository navigation

ChatGPT integration #2153

25 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

ChatGPT integration #2153

Description

Activity

ChazWinterYT commented on Jan 8, 2026

etraut-openai commented on Jan 8, 2026

aehlke commented on Jan 8, 2026

itsjavi commented on Jan 27, 2026

ashe0047 commented on Jan 27, 2026

mpettit2253 commented on Jan 27, 2026

raphaelrk commented on Feb 8, 2026

kt-devoss commented on Feb 9, 2026

25 remaining items

EARTHTOEDWARD commented on Apr 17, 2026

shawnholt commented on May 7, 2026

LeonardoDaviti commented on Jun 2, 2026

aehlke commented on Jun 3, 2026

LeonardoDaviti commented on Jun 4, 2026

chipverifpro commented on Jun 21, 2026

math-wil commented on Jul 8, 2026

aehlke commented on Jul 9, 2026

aehlke commented on Jul 9, 2026

ignatremizov commented on Jul 9, 2026

aehlke commented on Jul 10, 2026

Vishnu0007-svj commented on Jul 10, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions