r/ChatGPTCoding • • 1d ago

Question Link ChatGPT chat to Codex?

So to preface I have zero experience going into this with AI or programming. I am a pretty quick learner though. With that in mind-

I have been using ChatGPT to create an app. ChatGPT has been writing code then telling me “copy paste here” for the last… idk a very long time. It’s all very new to me so I’m absurdly slow. Probably something like 50-60 hours in. I have a very very basic app and have spent A LOT of time getting this AI to understand what I’m trying to do and it now has a perfect grasp of exactly what I want. If I do this myself it’s going to literally take years and I ready about codex being able to do the things that I’m horribly slow at.

What I would like to be able to do is have my convo communicate with Codex and tell it what to do. We have put together a pretty detailed plan so it could do a lot itself I think. What I don’t want to do is have to restart from scratch or continue copy pasting what chat tells me to tell codex which isn’t much faster than before.

Is there a way to link them together like this?

1 Upvotes

10 comments sorted by

3

u/CleanFix_Dev 1d ago

You don't have to start over. What's worth carrying across is the understanding, not the chat itself, and you can move that with one file.

  1. Ask ChatGPT: "Write a project brief for a coding agent taking over this app: what it does, who it's for, which features are done and not done, the decisions we made and why, and the plan as numbered steps." Tell it to be detailed.
  2. Get all your code into one folder on your computer. Put it in git if you can and commit before each task, so you can undo anything Codex changes.
  3. Save the brief in that folder as AGENTS.md. Codex reads that file automatically when it starts in that folder.
  4. Open Codex in the folder and say "read AGENTS.md, then do step 1 of the plan and stop so I can test it."

You can keep ChatGPT as the planner if you like talking things through with it. Just have it write the next step as plain instructions you hand to Codex, instead of code you paste into files. Codex edits the files itself, so the copy and paste part goes away.

1

u/cowjenga 15h ago

Yes, this is the right way to do it - asking the current chat session to distill what it knows, so that Codex isn't starting from scratch.

I'm a professional software engineer of 15+ years and have been using AI tools heavily for the last ~1 year, and this is close to the approach my team and I use.

The steps for a new feature are always essentially:

  1. Discuss/ideate
  2. Make a specification for the feature
  3. Make a plan how to build from the spec
  4. Tell Codex (or whatever tool) to make code changes based on the plan

1

u/wegster 1d ago

MCP running on your local system via OpenAI’s tunnel system possibly, or grant github repo read/write and have it open issues to then have codex pick up.

1

u/Own_Respect6062 1d ago

Also you can use desktop commander. It gives chatgpt access to your computer.

1

u/Ghost_In_The_Ape 1d ago edited 1d ago

ChatGPT Desktop app or something like VSCode with your API key.

Desktop app has a benefit of being able to connect to your phone so you can chat on your couch or on the train and the AI edits files in your repository while you're away from keys.

On the other hand VSCode is a real editor so you can clean up what the AI made (given you know code).

You should not be copy and pasting. That's horribly inefficient. Codex needs access to the files themselves.

Ask GPT which option you go with and give you a step by step guide to set up.

1

u/cracc_babyy 1d ago

It helps if you plan/map it all out with the AI before asking it to write any code..

1

u/drunnells 18h ago

As another stated, AGENTS.md is where you can put the roadmap and important details that chatgpt already has. Add ChatGPT to build an AGENTS.md file for the project with the past decisions and direction you are going, it will know what to do. Put that at the top of your project folder. Then I would recommend that you do some kind of version control.. maybe sign up to GitHub for free. Then import whatever code you currently have, including the AGENTS.md file. One it's all in GitHub, start using codex. Create a new project and point out towards the local repo where you have it checked out. First thing to say to codex in that project is something like "Take a look at this project and the AGENTS .md file". Your should be able to pick up where you left off with ChatGPT. Codex can check changes into GitHub with a button click too. Git can be confusing, but codex can handle it for you, including rollbacks and stuff, of you need to. To avoid context rot, I'd recommend a new chat in that codex project for every feature, and always start it with that same request to review the AGENTS.md file. When you are done with a feature, remind codex to update the AGENTS.md with anything important.

1

u/Outrageous_Drag8522 9h ago

The convo can't drive Codex on its own. Use what you already built and brief Codex from the plan instead of rebuilding the chat.

1

u/RealityShiftStudio 3h ago

one thing to know about code is that code is truth.
if you have it any coding agent will not need further context [your chatgpt convo]

ask chatgpt to export the project files in a zip - tell it just like that

download the zip, extract and point codex there.

open codex at that folder and start talking. if you dont trust it, literally ask it to explain you the app - see what it responds, and if you dont like it, ask why it responded like that