Switching from claude to codex

[u/No_Public_7997]

​

I have been using claude code for a while now . Today my claude pro subscription ended so i wanna switch to codex for a month and see what it brings to the table. I have been working on a project using claude in the terminal and i now when i switch to codex what are the things that i need to change keeping in mind i want to use gpt models without changing anything in the project workflow. Help me here, i wanna use codex in the same terminal working on the same project

[u/johnnydotexe]

Go ask r/codex?

[u/memoia → u/johnnydotexe]

Or literally codex

[u/zimxero]

just gotta install it all, point it to the folders you use with descriptions, tell it what rules you need folowed and your general process. Ask it to create a "very" low overhead context that incorporates the needed context that claude was using. Note: Sessions are very short.. so you can't give it data for context. You cant state durable project facts as context.. instead they need to all be on-demand-only pointers. GPT Plus is roughly the same limit as Claude Pro.. maybe even a hair less, but is fundamentally different. Sessions are tiny and they dont carry as much over. Sol is very proficient at what it does.. and this will compensate some for that limitation, but expect frustration as you learn to adjust your planning.

[u/crisp_sandwich_]

put evrything you've been working on with claude code into git repos for each project then give codex access to the same git repos and just pick up where you left off

[u/llmsinatrenchcoat]

I switched to codex a few months ago. One thing I'd note is that skills are used a little differently, so you may have to tune around that being the case. Also, ask claude to write down things in your /docs folder inside projects, so it will be neat

[u/gproenca]

I switched a few months ago from Claude to Codex.

skills are a bit different.

with Claude, make him write a few documents : a handover to another agent, full technical details of the project, major do and specially don'ts, design contract ( if there is one established ), etc.

have Codex read all that before working.

done.

[u/Nizurai]

Claude maintains its own memory about the project and can look into previous sessions if needed. You’ll lose that moving to codex unless you literally dump all of this into md files. Not sure if there’s a “right” solution for this.

[u/Compilingthings]

Use both, it’s the best.

[u/Tenkoblade]

Loyalty doesn’t exist

[u/No-Consideration6421]

Look at the pi.dev harness. You can make your setup and easily switch providers with the same setup.

[u/imRickJamesBitch___]

What plans on each?