Beth

So I used to do cursor and I'd have one terminal running Cloud Code and then the terminal running Codex.

But then I started, like, I just started forgetting that I was in Codex, not Cloud Code, because I was working in the same directory.

And I was just like, and I started confusing myself.

I'm like, oh, right, I'm in Codex, not Cloud Code.

So anyway, what I started doing is I'm using Codex and VS Code and obviously Cloud Code and Cursor to separate the two.

But I wanted to see the features of one over the other too.

What I found is

Matt Schumer wrote a really good post about this too, where I was finding is that Codex does a really, really good job with very more complex.

If you're planning to build a very complex app, and if you want to vibe code that, I would go with Codex.

Or if you wanted to use it as a coding assistant, not vibe coding, but I say it beats out Cloud Code significantly.

And then people are like, hey, how about Gemini?

It's like...

I, when I was testing Gemini and, and Codex Gemini had superior front end design.

And I think most people have seen that right.

Build this, build this, build this, you see it.

But again, back to, if you're building something complex, especially a complex backend, that isn't just a simple database.

You wanna go with Codex because Gemini has a tendency to kind of over deliver.

And it's like, that's not what I want.

Codex very, um,

for all those and i shared this in all the bunch of communities it it there is a difference between gemini and and gpt like codex and gpt 5.1 and if you have the opportunity to use them in conjunction with each other your outputs are going to be 10x but you have to kind of know when to use what like he mentioned like in codex so let's keep it in coding