How To Upgrade ChatGPT Codex Fast
Let's learn how to use ChatGPT Codex📅 2025-10-22
Transcript
[00:00] Chat GBD Codeex has a massive upgrade, y'all. And when I say massive, watch this. We're going to be checking out a couple of new features here, such as the version feature, in addition, the code review feature, and lastly, how do we set up our settings and codecs to get the best outputs. So, make sure to strap in here because everything that you've been seeing on social media when it comes to codecs, this isn't hype. This is super cool. Welcome back. On today's video, we're going to be checking out Codeex. I'm going to be working handinhand with cursor AI as well. So you can see how we can actually functionally make both of these worlds
[00:31] come together. You can do it. But first, we have a very simple app here. This is a Reactbased app. This is just a simple text stack where we got a simple little front end. Nice little React app. We love React. And our little front end we can run at localhost 3000. Very standard stuff. Ask a AI model what I'm talking about if you don't know what I'm talking about. But first off, let's just run it. So this is the little dummy app we're working in today. We can count up and down. I know it's absolutely amazing. It should be a billion dollar product, right? Reset. Let's learn these codec features that actually really upgrades your workflow. So, first off, just make
[01:03] sure your GitHub is connected to Codeex. That's fundamental. It's not connected. You go to settings here, go to connectors, and connect it here. Essentially, another way to find this is if you go to your GitHub profile, scroll down, come down to applications, you can essentially tell CHD Codeex what it has access to. So, maybe you don't want all repositories, but you want specific ones. Identify that there. the top level here of course what even is a repository that's your different code projects right so this is an actual backing app this is a cloud skill that I created for you all that you can download everything like that now if you want a more
[01:33] in-depth video on GitHub check out this channel here did a 40-minute video on how to actually use GitHub because you'll notice in all these different IDE they're everywhere so I went ahead and selected a repository which is test app how do I know it's test app come over here you can see it's test app up here and I'm just going to start off with a simple task of make the UI dark so you can discover the first major upgrade here which is the versions. So in theory, we can do make UI dark, but give me three different versions of this code and hit enter. This feature is cool for front-end development as let's say you're developing a signup form and you're like, give me three different
[02:04] versions of this signup form and I can pick and choose. But to be honest with y'all, back-end development is where this seems a little bit better. Cuz think about it, anytime you do back-end development, right? So maybe we're coding in Python and we're doing a custom pipeline for a very specific action. There is multiple ways you can approach the end value point. For example, user provides PDF. We extract data from that PDF. But the way and means we extract data from that PDF can be different depending on what libraries we use, what dependencies we use. So
[02:35] using this version ability within codeex here, this seems powerful as in theory we could ask for three different versions of a custom pipeline in our back end and you choose the one that seems to be the best fit for your application. For now though, let's go ahead and wait for this to generate all these versions. I'm going to go ahead and click in. You can see it's like loading in version one, version two, version three. So once it's done, you'll notice three out of three versions. I click here. The original prompt was make the UI dark. And we have version one, version two, and version three. Now,
[03:06] yes, front end wise, there's not that much differentiation, but with code, as you can see, it's a little bit lighter here. with code and UI elements. We could approach it in the sense of do create a different version depending on what you want. Eg. Instead of having such a simple prompt of add dark mode UI, I could be like add dark mode UI and be super creative. Therefore, the AI's initial preferences when creating the request, you're going to get a bunch of different versions come out of it. So, let's say we find a version we like. So, I come over here. I'm like, you know what? Version two looks amazing. Create
[03:38] PR. I can simply click view PR when it's done. And we see the PR right here. here. So, I'm going to go ahead and just merge this for now. And we're going to go ahead and grab that over to cursor is I want to show you another ability here that's pretty cool. So, I'm going delete this branch. Come back over to test app. We're going to see merge pull request codeex add dark mode UI. Obviously, if we load it now in our local code, it's going to look the same. So, then coming over to cursor, we're going to say pull most recent branch from master. That's what we call the main branch here. Main, master, just different names. So, we're going to pull this code here from the
[04:09] cloud into a local computer and then I'm going to be able to reload this. It's going to get dark or it's going to have to rerun the server. npm starts. Reload is start. Nice. So, now let me show you the second major upgrade here. And that is going to be code review. This is cool y'all. So, I'm going to go ahead and say just so you can see how this works. Create a new branch. Call it this is cool. Make a PR and have the new branch change the title of the landing page. Eg. Let's just change welcome to React. PR in this context is pull request. and also make it have an error. Now, watch this. And I come over to settings
[04:40] actually y'all. So, you can see this specific mention here. Mention codeex at codex in your pull request. So, I'm going to go and put this here. I'm going to hit enter. And here's what's going to happen. We're going to create a new branch. So, we can create this pull request. And then obviously with this pull request, we're like, hey, can we come back into the master branch? But before we come back into the master branch here, we're going to mention at codeex in the description of the PR and it will automatically check it. So, we're currently in that new branch. This is cool. You'll notice that there is a functionally breaking error that's currently happening in the application. So then we come to the PR here and I'm
[05:11] going to just delete this right here. I'm going to say at codeex, hey, check out my code. Create pull request. And just functionally so you all know, it's very important you add the at@ codeex here so it knows to check it. Create pull request. And what's super cool so you know it's working is you'll see the little eye emojis. Codex is like, "Yo, let me check out your code. Let me see if it's good." And this is cool because of the fact that now when you work in teams, obviously you're going to have to check the code anyways to make sure it does look good. But this new codeex feature of code review just adds that extra layer of like insurance to make sure that the code you're pushing
[05:42] there's no errors. And what's even better is that I purposely put an error in this PR. So therefore, we're gut-eing codeex right now. Can it see the error? Now, if we want to see this actively looking over the PR, we come over to code reviews here and simply click this. And this is going to show us all the work it's doing when it's checking out the new code that's being pushed to this branch. And would you look at that? If you didn't know what you were doing and you try to push this PR, you can see there is two severe bugs. So I can either look at the bugs here and it'll be able to identify it to the left over here. Or alternatively, we go back to
[06:14] that PR. We scroll down. Look how detailed this is, y'all. It will not only just organize this beautifully. Like any of y'all that be pushing PRs, I know y'all PR's descriptions don't be looking this good. Okay, it will identify exactly where the errors are and on top of that how to fix it. If I come back over here and I'm like, "Oh, you're right, Codeex. My bad. Fix issue." And it'll fix it for me. You don't have to look at this like Corbin, do I have to run this every single time?
[06:45] But the way I would look at this is just like purchasing assurance. you might as well have Codex review the code. If its results come back and you don't agree, then just don't do anything with it. But if its results come back and you do agree, then you just saved yourself a lot of headache before you merged back into the main branch or your master branch and potentially break your entire application. That's no good. Neat. So good. So, while we let that fix that, let me show you some of your settings that you might care about. The first thing you might care about in your
[07:15] settings is these custom instructions. So we can leverage this like we could leverage maybe the custom instructions within Chad GBT or claude like the actual model itself but these custom instructions are specific to the codeex model and your development team. So for example in PRs do XYZ it will now follow that direction. So maybe within your company for front-end development with your PRs, you need images of the relevant new components you added. Add that there. Every single time you do a
[07:45] front-end change in the pull request, add a screenshot of that front-end change. This is just something standard we teach to our engineers and very standard that you'd want anyways for any type of front-end PR. Custom instructions important. The next thing that might be very frustrating if you don't set up is going to be the environment and your specific app. So mine's test app over here. This is where you can add environment variables. Now, if you're familiar with coding, you already know what I'm talking about here. But environment variables or secrets are fundamentally extremely important for a real application to
[08:15] actually work. Now, if you want an entire course made by me that is completely free and it's using YouTube's new feature like YT courses, I'll leave that in the description down below. Essentially, these are courses that I made that are just like lesson one, lesson two, lesson three. It's all on YouTube. It's all native and you can watch me build out a software from complete scratch and show you the value of environmental variables. In shortand what environmental variable is is that anytime you download something actually you wouldn't be able to get it from the cloud but essentially it's the local.qaV EMV.pra
[08:47] this kind of stuff. Make sure to watch my software series to understand what that means. and we need to get these kind of variables in this kind of codeex workflow so you don't run into errors that are like hey you know when you called openai's API key we don't have one you add that there looks like they might have finished my pull request are you done you done codeex can I go eat Chipotle now it looks like it's done in order to do that you're going to come over here to the fix critical bugs in app.js JS update branch viewpr. Let's see. And there we go. Fix
[09:18] closing div mismatches recent commit. Like I say, merge pull request and we'll be good to go. What you just saw there is massive. So make sure you leave a like. It is completely free. Codeex is no joke. What I suggest you to do is pair this with all the other tools you're already using. Codeex could now be your new little friend for PRs. Anytime you create a new branch, new feature, new anything for your applications, now just do the at@codex. Hey, Codex. Like, we essentially just created a nice little developer friend that is going to be more of a nerd than us. It's gonna be much more of a nerd.
[09:49] It's gonna be able to find all the situations and errors that possibly could occur within our PR. Leverage the custom instructions as well. If maybe errors aren't the fundamental thing you care about when reviewing a PR, but maybe it's optimization. Maybe in the custom instructions, you put is the way I'm coding out this custom pipeline the best way? Give me suggestions, codeex, and you get those in your PRs as well. But as you already know with these style of videos, I'll see you in the next. Did Chadbd Codex just give us an additional software engineer for our team that basically will check all of our code, which was very annoying in the past because I never wanted to check my code
[10:20] anyways. So now we can have AI check my code automatically by doing at Codex codeex. Nice. And I go eat Chipotle