Codex in JetBrains IDEs

It's really important for us that Codeex works anywhere you like to code. For many of you, that place is your Jet Brains IDE. So, we're super excited to announce that one of our most requested features is finally here. Codex now works in Jet Brains. You can now collaborate with Codex directly within Jetrains IDEs using your Chat GPT subscription API key or your Jetrains AI subscription. And with me, I got Glabb from Jet Brains who's going to give us a quick tour of codecs in Jetrains. We know developers use our products on complex problems and that's where Jet Brains and Codex really shine. So I wanted to show you Codex work on real projects inside my IDE. It's a multiplatform Cotlin codebase for our conference. It runs on mobile, web and even desktop. I'll show you how Codex helps with debugging and feature implementation on that scale right within your IDE. So um let's start

probably with uh with the fact that you don't need to use Jet Brains AI subscription to log to Codex. You can use your code uh JGBD account to login or add the API key to do that. So I'm going to log in um in uh in my codeex account uh which is already done. And then I want to first of all ask uh what this project is about probably right. — It makes sense. — Yeah. — Good way to start. So we can see codeex beginning to look at different files reading the file system. — Exactly. Yeah. So it collects some context and understanding of what does the project do? So as you can see it's our cotlin conf app. By the way you're welcome. Uh and uh so yeah it runs on Android, iOS, desktop and web. uh using the framework called compost

multiplatform. So I will try to build this project right now to see how it actually looks like on iOS. — Cool. — Um — so this is compiling it for iOS and then — it compile it compiles the project uh for iOS using gradal technology. Um we we're using the intelligj tools for that but as you can see there are some errors right. So and I will uh I will probably need the help of codeex to uh to solve that. Uh so what I do is I'm just simply copy and pasting everything that is red here right and uh asking codeex to help me uh solving that. So we can now see codeex is jumping through different tasks looking at the files that might be impacted based on the stack trace. — Exactly. And you see what exactly Codex does. So it provides some reasoning on the certain actions that it does. It shows the files that it read and so on. — And this is the same codeex that I get when I run like codec cli or if I use it in a different — exactly the same codeex just because um inside jet brains we run evaluation to make sure the quality of CLI codex is exactly the same as the one that uh users receive inside a system. It's amazing. All right. It looks like it did some file changes here. — Yeah. So, actually uh we can take a look on on the exact changes to make sure that the actual mask makes sense. Um you see the codex has finished that it work and we can try to build the project again. Right. — Fingers crossed. See if it builds. — These are just warnings so it's not a problem. And it builds. — All right. Does it run? — Developers usually don't like uh dealing with the belt issues and it's quite difficult to understand what exactly is happening when uh the project is building. So Codex does an amazing job understanding what exactly needs to be done here. — Yeah, we didn't really have to give it any guidance. It just exactly lines around. We figure things I didn't even need to read through the errors that are here, right? So yeah, the app is working. Um and uh now

I guess it's time to give Codex a little bit more complex task, right? Um we know that the biggest problem for all the mobile developers is localization, right? So just because it's quite a mundane complex task that does not involve a lot of kind of visual changes but at the same time it is extremely important. Um pro probably the best task to give to an agent. Right. — Sounds great. — Yeah. I have a problem that I going to base here and um I'm going to ask uh create a localization to Spanish — for the conference app that we have. — Awesome. Let's fire it off. While uh the while Codex is working, we still can oversee what kind of uh what kind of files it looks at, what kind of reasoning behind looking these files when it runs the bash commands, we can see what kind of commands it runs at the

same time. So different de different developers have different tolerance towards what agent does, right? So and uh this is something that we uh consider inside uh inside our integration where user can select different types of um — access modes to agent right. So we can restrict agent to from editing any file. So it would be just read only extremely suitable for understanding complex code bases or let's say search when uh user just doesn't know where the certain file is located. Agent mode uh allows to run commands but at the same time it requires user approval uh for every command. So that some quite sensitive commands would be user reviewed and full access which I currently have actually allows agent to run any command they want apart from the riskiest ones and um and change the code files. — Awesome. And then you can see are you able to like click on the actual like files that it's checking out? — Yeah. So you can take a look at the file. So it opens in ID. So you can uh take a look at what exactly is uh is written in this file as the changes come. — That's awesome. And like I think one of the things that's interesting is like it looked like Codex was doing a lot of research across the codebase. So that like if you have a complex codebase, it's going to go and first understand all the context without because we didn't give it any guidance, right? We just sort of like say here's the problem. But now it's sort of like locked in and it's just like hammering out code change after code change. — Exactly. It's like you uh put a developer that does not know a thing about this codebase to a task. So f the first thing they do is to research the code, right? So agent here exactly mimics this actions. doing the research. It's not changing anything just because they don't know yet about the codebase, but so once the research is done, the code changes are coming. — Amazing. It feels like it's like everything is still very much right inside your IDE. So

— exactly. — You don't have to change any of your behaviors that you're used to. — Uh so, it's just a sidebar, right? So uh while agent is working you can even close this tab and start a new conversation I know asking about something else or you can continue uh continue working on the files that you worked with. So the work of an agent parallel is paralleled with the work that developer does and it does not intervene with that. So developer does not need to wait for agent to stop to finish working to continue their work. They are kind of coexist elegantly in parallel. So now it's running a shell command here. So it looks like it's running gradal. — It's it tries to compile everything. Yeah. — And this is like one of the interesting things about Codex. Codex always tries to val verify its own work. So being able to then tap into the build tools and using them — and that's an amazing part, right? So just because just writing code is not enough. You need to make sure that the code actually works and reiterate on that if it doesn't. And as you can see, some of the commands are skipped and it's done. You see, so the codeex listed the files that were changed, right? So we can take a look at the uh lines that were actually updated or removed. Um we can see them in a commitment to window that they are uncommitted yet. So we uh we can push them to the repo. But first of all, let's make sure that it actually works and uh rerun the app uh to see whether the localization actually takes place. Cool. And for that, we're just using the same tools that we're used to in the ID already. — Exactly. Yeah. — So, it's building, starting up the iOS simulator. — It starts the simulator and I'd expect the app to be already in Spanish. — Cool. Let's see. Oh, yeah. I can see like your simulator is set to Spanish already. — Set it to Spanish just because the app going to take the localization from the system. So, if uh everything went fine. So the app would be already in Spanish

Spanish and that's how Codex is natively integrated in our products. What I showed you was all done in intelligy but it also works in other jet brains products like PyCharm Webtorm or Rider. Thanks Glenn. These are just a few of the things that you can build with codecs inside Jet Brains. To get started go to openi. com/codex or choose codeex inside the AI chat of your Jetrains ID of choice. Thank you and we can't wait to see what you build.