Automating Codex – Non-Interactive Mode, OpenAI API, SDKs & GitHub Actions

Added: 2026-05-15

[00:00:01]Okay, so for Codex it has a configuration file that comes in the form of a tunnel. So it's literally config. tunnel and it can be in more than one location. There are easier There is either the global scope location where it sits in your home directory with dot Codex.

[00:00:19]Okay, and then there's the option where it's within your project and it's just a config. tunnel. Um and so those are the two locations that it can exist. We will double check triple check the project configuration file as I'm finding that Codex's conventions for naming stuff and placing them is not consistent. Let's take a look at some of the things that we can set. There's a lot of options so we won't go through all of it. But here you can see we can set what model it should be used, um specify the model catalog based on its JSON, you know, set the sandbox mode, whether we can do web search and if it's caching or turned off or if it's live, set its personality, set the reasoning effort, sandbox information.

[00:01:03]Um but most of the most of the time we're going to be going in here to meddle with your sandbox information.

[00:01:07]But there again, there's a lot of options. Uh but we'll cover what is relevant because there's a lot that isn't, okay?

[00:01:14]Hey, it's Andrew and in this video we're going to take a look at adding a configuration file. We've probably done this before. Um but let's just make sure that we absolutely know how to do it. Um and so what I'm going to do is we're going to go into our Hello World which we actually already have a tunnel file.

[00:01:29]What's interesting here is that I have it in a dot Codex folder called config but I think when we go back to our um uh docs it was saying that it could sit there in the in the directory directly.

[00:01:41]And there's so many places that it can load. So let me just go double check here so that we can uh take a look here. Well, it says dot Codex config tunnel and then one there at that level. Okay, so what we're going to do, even though we already have one, I'm going to make a new new folder and this will just be called um um uh simple math. Simple math, something simple here. And so, I'm going to CD into simple math.

[00:02:08]Simple math.

[00:02:13]Oh boy, that is a folder. Come on, let me in.

[00:02:17]Simple math.

[00:02:19]Oh, it's an underscore. That's why.

[00:02:23]And now that we're there, I want to go ahead and we'll go make a new folder here called codex.

[00:02:28]And then we'll make a new config.toml file.

[00:02:32]And what I want to do here is just change which model is being utilized.

[00:02:35]So, I can't remember what models are available to us. So, I'm just going to go ahead and type in codex.

[00:02:40]And we will see what models that we can use. So, here I right now we're on the GPT-5.4.

[00:02:45]I'm going to type in model.

[00:02:48]And we have uh four mini. So, I'm going to go up here.

[00:02:52]And we'll say GPT 5 4 5.4 mini.

[00:03:03]I'm going to match it based on what it says there. All right, save that file, close this out, clear, type in codex.

[00:03:07]And all I want to see is does it load that model? And so, there it goes. It loaded it in. That's as simple as it is.

[00:03:14]Um you know, that's all I really wanted you know is to make sure that you know how to set it and where to set it. Um but yeah, there you go.

[00:03:22]Okay, let's talk about non-interactive mode. So, codex has a non-interactive mode, also known as headless mode. Uh that's what Claude calls it calls there.

[00:03:30]So, I'm just trying to um normalize the information across providers here. Um but it allows you to execute requests without entering into interactive terminal. And so, here is a bunch of examples. Let's walk through them. I'll get my pen tool out here so I can point to the ones that we're on.

[00:03:45]But the first is just use codex execute, and you just provide it a prompt, and it will execute.

[00:03:52]We have the ability to pipe things. So, here we are piping out. We can pipe into, pipe out of with Codex. We can set ephemeral, so it will instantly forget.

[00:04:01]It's not going to create a session or continue on. We can set the permission level. So, here we have full auto mode.

[00:04:07]We can set the sandbox, which we cover in the sandbox section. We can ask it to output JSON here explicitly and then we can pass it to jq and do something interesting. We can pass our Codex API key, so we are not utilizing our subscription or if we just have different keys and we want to leverage multiple keys at the same time. We can resume a previous conversation.

[00:04:31]A very common use case for non-interactive mode would be GitHub actions. So, here you can see we're installing Codex and then running it and then running it here with very specific settings. Technically, with GitHub actions, there is a very specific GitHub action for Codex. So, when we do the GitHub action sections, if I make a video on that, we'll probably use the action instead of that, but if you need full control within any environment, if you're not even using GitHub actions, you're going to be using this mode, okay?

[00:05:02]Okay, let's take a look here at the non-interactive mode. So, I don't think it really matters what repo we're in, but I'm going to go ahead and maybe we'll go into our Hello World as that is a very simple application and a great place to check. I'm just going to go ahead and sync whatever I have here, but we'll go ahead and try it. So, we already have Codex installed, so I'm going to try Codex exec and I'll just increase the font here so you can see what is going on and sometimes it helps to do this. I can move this over. I'll just say, "Tell me what is in this repo or this project folder."

[00:05:37]Okay, let's see what we get back and if it works.

[00:05:42]Okay, and I'm not sure what the issue is, but it's possible that I haven't logged in a while, so whoops. Oops, oops, oops, oops, oops. Actually was working.

[00:05:53]We'll see we'll try that one more time.

[00:05:55]It was strange because it's showing an error. So tell me what's in this folder error.

[00:05:59]Snapshot or validation failed. Snapshot command exited. I don't know why it's complaining.

[00:06:05]But it's working.

[00:06:12]It's doing something.

[00:06:14]So that was a little bit confusing there that initial one. So at a glance, this is the minimal project. So it it definitely works. I don't know why we get that initial error, which is very, very confusing. But let's go up here and I'm going to say JSON.

[00:06:26]We'll say JSON. As they say, we can do this as for me. Tell me the project.

[00:06:31]Um, provide a JSON JSON structured report back.

[00:06:38]And for fun, we will also pipe this over into JQ and do period. And so we will hold on.

[00:06:49]And what's interesting is like it's going to stream the information.

[00:06:52]And so we're getting back JSON and we're getting it formatted. So here we can see the information back. It seems like it streams everything back, not just um not just the the single command there. That first one's kind of strange. It's kind of some kind of error that doesn't seem to matter. Shell snapshot validation failed. So does that doesn't matter. But here we're getting back all the input and it's showing us every single step.

[00:07:15]So this is really interesting. I thought it would just come back with the final result, but literally every single step that it's streaming out is coming back.

[00:07:22]That is really, really cool.

[00:07:24]As that's going to give us a lot of flexibility in terms of how to work with stuff. Also it tells us exactly how it works. So you can see turn.completed, um, you know, other item completed, stuff like that. And it might not seem obvious here because we don't really cover in the course, but like I have another course called cloud architect foundations. And when you know the internals here you know if you have to build more complex systems it helps you understand how to work with it but we don't cover that here because we are just learning how to use utilize this for our usage not necessarily build complex things. Is there anything else that we might want to test because I mean those are the two most common use cases.

[00:08:02]We might want to resume a conversation from prior. So I'm going to go here and just type in codex. I almost said Claude of course.

[00:08:10]And we'll type in resume and I just want to see what else there was here.

[00:08:13]So here we have can you fetch the weather from Calgary? I don't know if we have to type this exactly.

[00:08:18]And so I'm going to just copy this here just that there.

[00:08:21]And I'm just going to quit out of this.

[00:08:24]We'll say codex exec.

[00:08:26]Um.

[00:08:28]Last. So we'll say resume.

[00:08:32]Last. I think last means.

[00:08:35]Resume the last session.

[00:08:40]Okay.

[00:08:44]Uh we restricted this machine quite thoroughly so that's why it's not going to be able to pull it. As under our hello world at some other point we um.

[00:08:52]We were really aggressive with this configuration tunnel and that's why we are not able to do that.

[00:08:59]So it still works and so I think last just means continue the last conversation not because over here it looks like okay type in the name and so that's how you know which one to resume but really it's just resuming the last one.

[00:09:12]Okay. Could you do other stuff with that? I'm not sure. Um let's take a look at codex exec help.

[00:09:18]There's more information.

[00:09:21]And.

[00:09:23]Because the docs aren't always up to date right? And so it might just be here. So here it says provide a a previous session or ID or pick from the most recent one. So here we can provide the session ID I suppose.

[00:09:34]Um.

[00:09:36]So if we were just to go here and not put last Try this. Let's take this out of here.

[00:09:42]Do we get to choose?

[00:09:48]No, it doesn't. And so, that's not clear, right? So, it's saying like we get to choose. Obviously, we don't get to choose. Uh we got some uh colors here.

[00:09:58]I'm just seeing if there's anything else we missed. Tell to use it in a very specific directory.

[00:10:02]Um I mean, that could be really useful because maybe you're not running it where you actually are. So, you might want to do that. Change the model, yep.

[00:10:11]So, there's obviously more options here.

[00:10:14]But, of course, the man helps us out.

[00:10:16]The examples that showed here was from the docs. So, you can see the docs don't always match.

[00:10:21]Uh well, technically, this is documentation just in another way. So, just always make sure to check everything. But, there you go, okay?

[00:10:30]So, with OpenAI, we can interact with it on uh different uh layers or levels, if you will. Um and this is important to know because some things will only be uh available at certain levels. And so, the the lowest level is going to be the OpenAI REST API. Um and so, what's interesting here is that OpenAI does not have a generic um library.

[00:10:51]Um so, for example, if you're using uh Anthropic Claude, they literally have a library called the Anthropic SDK, which is specifically just a wrapper for uh their API. Um there's probably some uh third-party ones out there, but I mean, it's not hard to work with it directly.

[00:11:06]So, here's just an example uh of using uh JavaScript to interact with it. Um but yeah, we'll just make sure that we understand the layers. There's more layers that are abstracted with OpenAI versus Claude, and that was just the choice that OpenAI went with for whatever reason, okay?

[00:11:22]Hey, folks. It's Andrew. And in this video, we are going to learn how to um interact with the OpenAI uh REST API. So, I'm going to make a new here. We'll call it open AI rest. Um and we will CD back a directory and we'll go to open AI rest and we'll type in codex.

[00:11:40]And we just want to do a simple action.

[00:11:43]So I want to demonstrate uh using the open AI rest um uh directly. So can we do that using let's say Ruby? I really like Ruby, so we'll go ahead and do that. Um just create a simple Ruby script.

[00:12:05]You know, using HTTParty, I guess. Um and all HTTParty is is just a way to send out a query. Um so every language has one. I don't know what the other ones are called, but it's just basically a way of uh invoking it.

[00:12:18]We can also make a curl command as well uh to test it. But we'll go ahead here and take a look at what appears. But as far as I'm aware of, I mean there's probably an unofficial library, but there's no official library per se. So we will um see what we have here. And I'm hoping I'm in the right directory. When I was generating this, I thought I wasn't paying attention.

[00:12:37]So where did it Oh, no, I put it in the right directory. So here it is. It's going to bring in that open API key.

[00:12:45]And here it's going to do responses.

[00:12:46]It's going to use mini and it will take an input. So write one sentence about why direct rest APIs are useful. So that is fine. And so I'm going to need uh an API key here. So what I'm going to do is stop this here.

[00:13:00]I know how to run this. It's pretty darn easy. So we will um do a bundle install.

[00:13:09]Okay, I'll just make the instructions here.

[00:13:13]Okay, we got bundle install.

[00:13:15]And then once that's installed, we can run this. It'll just be bundle bundle exec Ruby open AI rest.rb.

[00:13:27]So that's what we will need to execute it. So, I just go need to go get a key.

[00:13:31]So, I'm going to go find one. We'll just type in OpenAI developers. I'm just doing this off screen so you cannot see what I'm doing just yet. And I'm over here and I'm going to get a new key.

[00:13:43]And we'll go ahead and this one is from a day before. So, we'll revoke that key.

[00:13:48]And I will create myself a new key. This will be test rest API.

[00:13:53]And I'm going to go ahead and create that key. We will copy that key. And now I need to set it. So, this is going to be uh export OpenAI uh API. It'll say OpenAI API key equals and then we'll paste it in. And we'll hit enter.

[00:14:13]And so now let's go ahead and see if we can run this and invoke it.

[00:14:21]And you know, the main thing here is that there's more models than what Codex is using, right? So, there are image models, there's all sorts of models. And so, if we want to have access to it, we'd basically having to use this API.

[00:14:33]Are useful because they engage Oh, so they're just Here is the prompt. So, it came right back here. And so, I can go back over to here.

[00:14:38]And we'll just change this to say um say, you know, give me uh study uh give me a bulleted list of studying tips to pass the JLPT N5, okay?

[00:14:55]I just took the N4 in December and I failed it. And so, I I need all the tips I can I can use here to pass, okay? So, we're going to go ahead and wait for it to generate out. And so, it comes back.

[00:15:06]So, here is a bulleted list. Learn hiragana, build a basic vocabulary, etc., etc. So, it works. Um and that's all I really wanted to show you. Maybe we can convert this into a curl. So, I'll go ahead and just say, "Hey, can you create a curl command uh from my open rest uh code?

[00:15:30]Okay, and we'll just wait for it to generate that out.

[00:15:35]Should be able to do it. We're still using the intelligent model not We're not I mean mini's fine as well, but we are using the one that's appropriate.

[00:15:42]And so here we have So we have equivalent if you want to behave more like Ruby script I don't care about that, but we'll go ahead and grab this here.

[00:15:53]I'll make a I'll go in here, so we'll go down here.

[00:15:57]Just paste it in.

[00:15:59]And so in theory this should just work.

[00:16:02]So go ahead and hit enter.

[00:16:07]And we're just hanging out here.

[00:16:13]And nothing's happening. Oh, there we go. It's back.

[00:16:18]Okay, and so there is our response cuz it's not streaming, right? So it's probably happening that entire time. And there you go. We just learned how to work with the rest API.

[00:16:28]Hey, this is Andrew. And so in this video in the open rest one, we ended up implementing the rest API directly. I forgot that they actually do have a SDK called open AI. I guess I got confused because there's open AI agents codex, and it's been a while since I directly used it.

[00:16:44]And so I did not realize I thought the SDK agents was what I was using before, but there actually is just one that wraps the rest API. And so we should go ahead and use that one. So I'm going to go ahead here and just say um I mean we did open AI rest, but we say mkdir open AI SDK here, and we'll go into here.

[00:17:07]Yeah, you can't remember everything here, folks. It's just There's too much going on. And so I'll go ahead and go enter in this, and I'll just say using the official open AI SDK. I would like to demonstrate calling a model like image generation.

[00:17:27]Okay.

[00:17:28]And now that I think about it, this is the primary way that I was working with with it before, but obviously like if you use agents, it's going to be way easier to build out agent agent interactions like tools and things like that. Whereas with this one, you'll have to do a lot of the work uh passing things along, but we will go ahead and and get this generated out here. Um I made a new folder here.

[00:17:56]Over here.

[00:17:57]Hopefully I CD to that correct directory. I kind of forget if I did or not.

[00:18:01]But we will give it a moment to generate.

[00:18:05]Okay, we are back. Let's take a look at what we have generated. And so it's fine what it is here. It's probably using the TypeScript library. Um it did add a node module, so that was really really nice.

[00:18:16]And so I want to go into our examples mjs.

[00:18:20]What the heck is an mjs file? I don't know what an mjs file is. What is an mjs file? I've never heard of an image mjs file.

[00:18:29]It is a JavaScript source designed for ECMA standard. Why did it Why did it do this of all things?

[00:18:37]Um OpenAI, sure.

[00:18:42]I mean like I guess as long as it works, but like it looks just like JavaScript though.

[00:18:47]Um but anyway, here we would be generating out an image.

[00:18:51]Uh does it specify what do you use?

[00:18:53]GPT-1? And so often the way this works is that you import it via OpenAI. It's going to be client images generate.

[00:19:00]Right? But it's very very low level. So what we'll do is we'll back out here and I believe I already have a key. I'm just pulling the same key, folks. Uh I show you in other videos, so I'm not going to show it again. I probably already reset here, but I'm going to just set it again out of habit. And so let's go ahead and do we'll npm install first.

[00:19:23]npm run start or npm start and let's see if that works. That's not there. Let's go over here and they call it generate image. So for some reason they got really creative here. So say run generate image and we will whoops, we will generate out that image.

[00:19:39]And so hopefully it's going to say where it places it. If we go back over to the code.

[00:19:45]Uh I mean it's going to export a base uh base 64 and we have an output file here.

[00:19:50]So it's generated image and so it should drop it right in this directory.

[00:19:54]So we'll give it a little bit of time here to generate.

[00:19:57]It says that it's done. We'll look at this a refresh here. We have an output.

[00:20:01]There's our image. Beautiful.

[00:20:03]What is the size of this image?

[00:20:08]I'm curious.

[00:20:10]It is I just don't want to commit a very large file to my repo here. So I'm just curious how large it is properties.

[00:20:16]It is 1.62 uh megabytes. Beautiful photo um too large for my taste. So we'll go ahead and we'll delete it, but I like it and so there you go. That is the OpenAI SDK.

[00:20:32]All right. Ciao ciao.

[00:20:36]Let's take a look here at OpenAI agents SDK which allows you to build agents using Python or TypeScript. Uh and so here's the example of the TypeScript one. So we are defining what an agent is uh and then we are calling it with a name and instructions. We wait for the results. Very straightforward. Um and there's many uh features within the agents SDK. So we got the agent loop guardrails, tool calls, MCP tool cards call sessions, human in the loop mechanisms, tracing, real-time agents.

[00:21:04]Um the thing that is confusing is that [clears throat] there's also the Codex SDK, which serves a different purpose.

[00:21:09]So, for whatever reason OpenAI just has separated this out, whereas when you use Claude, Claude has their own Claude Agents SDK. And so, it's like a combination of the Codex SDK and the OpenAI Agents SDK. So, I need to make it very clear of these separate layers, and then also the fact that OpenAI does not have a official REST API wrapper, one, okay? So, just distinguishing between that. And then it gets confusing cuz they have another layer, which is the app server, but we'll look at that in just a moment.

[00:21:43]Hey folks, it's Andrew, and in this video we are going to go ahead and create a very, very simple agent, so simple agent using the OpenAI um the OpenAI Agents SDK. I'm having this problem where sometimes >> [laughter] >> my bash terminal just becomes unresponsive. So, there's a few tricks to that, opening a new one here. So, we will see the into the simple agent. I don't know what hangs it up, I couldn't tell you why.

[00:22:08]Um but we'll go ahead and type in Codex here.

[00:22:11]And uh we'll just say using TypeScript can you create me a simple agent using the OpenAI Agents SDK. So, we'll let it go ahead and do that. I believe it's also available in Python, um but OpenAI Agents SDK should be good enough. And so, we will just wait a moment here.

[00:22:40]Okay.

[00:22:41]So, it shouldn't take too long.

[00:22:48]Okay.

[00:22:50]All right, it seems to be back. Uh and so, we'll go over into our simple agent, and we got a lot of code here. The only thing that's kind of frustrating is it doesn't generate out a git ignore.

[00:23:00]So, go ahead and do that.

[00:23:02]And I will just say node modules as node modules end up being quite the headache for us. Um well, I'm going to go ahead and stop that here, and we will go npm install.

[00:23:11]Once you learn a few languages, it becomes very, very easy. Um And so, we're going to scroll on down here.

[00:23:19]Okay. And we're going to take a look.

[00:23:21]So, we have simple TypeScript agent.

[00:23:24]We're importing the agents here. Um we're supposed to have the OpenAI key, which is fine. Um And here, it's asking about current time and date.

[00:23:35]And here, we can specify the OpenAI model. I kind of wish it defaulted to a specific model.

[00:23:44]Okay.

[00:23:46]I'm going to go back here. Can you make the agent default to uh GPT mini?

[00:23:53]I probably should tell what version of it, otherwise it's going to get it wrong, but uh we'll just let it do that there in a moment. And what I'm going to do is go get go ahead and get my API key. I was using this for another project, so I've shown you how to generate API keys quite a few times here. Um I'm not going to show you again in this video, so go back to the API key generation part, which will show you how to do it.

[00:24:13]Um and here, it's talking about five mini. Uh doesn't sound right.

[00:24:19]No.

[00:24:21]Is Well, well, I guess we'll find out.

[00:24:22]Maybe it will work. We'll see.

[00:24:27]Mhm.

[00:24:31]Okay. And so, now what I'm going to do, I'm going to go export here, OpenAI OpenAI API key equals this. And then, um what we will do here is run it. So, we'll say npm run watch.

[00:24:48]Oh, or say npm uh start.

[00:24:51]That's usually the standard thing. These are all over here in this. So, if you go here, npm start always npm start. And so, I'm expecting it to output time and date here.

[00:25:03]So, it says, "I'm an assistant here. I give concise stuff, tools I can use. So, current time parallel, what would you like to do?" And so, there we go. So, it's responding back, uh which is good.

[00:25:12]Let's go take a look at the source code here.

[00:25:16]And here you can see we have instructions.

[00:25:20]We have our model. We have the tool, a custom tool that we defined, which is really, really cool.

[00:25:26]Um and the only thing is that there's no continuous loop here. So, go down below, introduce yourself in two short uh sentences.

[00:25:36]And it's supposed to wait.

[00:25:39]So, I'm going to go over to here.

[00:25:42]Um the agent is um immediately exiting.

[00:25:49]And so, we aren't getting uh a feedback loop from the user input.

[00:25:59]Okay, so let that fix that.

[00:26:01]Let's go back to go look here. So, it says I've updated the readme document to the new behavior.

[00:26:06]I don't need that. I need it to actually change the functionality. And now it's accepting um read lines, so I can see here in the code that um it's going to do that and then run a turn. So, pretty clear. So, we'll go back over to here and we will start this.

[00:26:23]We will give it a moment here.

[00:26:26]Mhm.

[00:26:30]It's just doing the initial prompt here.

[00:26:32]So, can you tell me the time in Toronto?

[00:26:39]Okay, and so it's going to go ahead and try to use that tool.

[00:26:43]Not the best code, but it it's clear, right?

[00:26:49]The other thing is that we have have get current time function, but uh how would it know where to call, right? So, normally there'd be like a function defined somewhere here.

[00:26:58]It's kind of what I'm looking for.

[00:27:03]Mhm.

[00:27:07]Unless there's already a function called get current time.

[00:27:13]Oh, over here. It says now date. Okay, so it doesn't matter where you are, it's always going to do this. So, see how it says your host time is this?

[00:27:20]So, I say, you know, give me time in Calgary.

[00:27:27]So, it doesn't know where we are. So, this is just going to get on your our running local machine. So, I can't say Toronto, Calgary, that's not going to make any sense.

[00:27:34]Um but anyway, it's pretty straightforward.

[00:27:37]But you can see you get a a lot of batteries out of the out of the box here.

[00:27:41]I could literally make this into a 2-hour video, but I figured we'll just stop it here, and there you go.

[00:27:48]Okay, so we now have the Codex SDK, and this allows you to run Codex programmatically using TypeScript. Um I don't know if there's a Python library.

[00:27:57]I think there's just a TypeScript library. I don't understand why um you know, we're in the uh age of uh being able to generate anything and then we have the limited SDKs, um but you know, this is what they're doing. But over here we can see the TypeScript SDK, so we are defining Codex. We are setting up the thread, and we're asking it to make a result. So, what can Codex SDK do? It provides file system access, code editing, command execution, test running, repo awareness. And so, Codex SDK helps you build coding harnesses where Codex can be used alongside with the OpenAI SDK because they serve different purposes, right? And I know it's confusing, but we will uh keep working through this, okay?

[00:28:37]Hey, this is Andrew. In this video, we're going to take a look at implementing the Codex SDK. So, we'll go into a new folder.

[00:28:44]Uh and we'll just see what we get generated it I mean, like of course you can do this yourself, um but the reason I uh do this along with you is that in case something doesn't work we can fix it together. And so I keep typing that I I I figured I made it already, but I didn't. And so we'll CD into that and we'll open up uh this Codex directory. And so we'll just say um using can you give us an example of the Codex SDK um using the official library in this folder. We'll go ahead and let it generate out and wait a moment, okay?

[00:29:21]Okay, we are back and it says uh we have a minimal example running. Let's go take a look at the code for Codex. Uh so we'll give this a nice refresh here and there's my SDK folder, examples. Now it's following this MGS pattern. Sure, it's fine. I mean like again, I'm just used to being JS or TS, but that's totally fine. So here we have OpenAI.

[00:29:43]Mhm.

[00:29:48]That does not look right correct to me.

[00:29:49]So I'm going to go over and look up Codex SDK.

[00:29:53]Okay.

[00:29:56]And we will take a look here. So this is the Codex SDK.

[00:30:00]It does not understand what we were asking for. So we'll go down here. It's using the GPT Codex. All right, so yeah like you didn't use the uh Codex SDK. Okay?

[00:30:13]That's what we wanted. So we will let it go correct its mistake.

[00:30:20]Uh-huh. And we'll come back and see what we get.

[00:30:23]Okay, so we will um take a look at the code. Actually, before we do that, I'm just going to set the API key here. So I'm just going to stop it and we will um set it. So we'll say export Codex or not Codex uh OpenAI API key equals this and hit enter. Let's go take a look at what code we have now?

[00:30:43]So now we have the open SDK. So you're helping with a JavaScript repository, review of the code base structures, return a short title with three bullet points. So here we have Codex. It starts a thread. It runs the task. Very similar to the open AI agents. Um but you know, again, the documentation says one has less than the other one, but like does it though? Again, I just don't trust the docs from open AI because I've been finding things that are um not matching exactly. So but anyway, that's fine. We will just continue on here and I really think it'll take deeper uh deeper time working with these tools to really really know.

[00:31:23]We'll go ahead and we'll run this and see if that works.

[00:31:26]Again, we're just doing sanity checks, making sure that this stuff works as expected, right?

[00:31:31]Um and so here right off the bat we're getting information back and so it works. So there you go.

[00:31:43]We can use GitHub actions along with Codex. And so we saw earlier with the non-interactive um um mode that you could just, you know, put it into any kind of build server and utilize Codex, but they have their own built-in Codex GitHub action. And so you can just see here. I'm just getting my pen tool out here. Um that we can just call it directly provided a prompt file, an output file, set it sandbox. Um so definitely easy way to work with Codex.

[00:32:14]Um and GitHub actions. And you know, you could have it to react to stuff and do stuff based on whether you have pull requests or comments or things like that. Um so yeah, there you go.

[00:32:24]Hey folks, this is Andrew. In this video, what I want to do is implement a uh use case with um Codex with GitHub.

[00:32:31]So I'm going to go over and type in Codex uh GitHub actions as there's going to be some kind of GitHub action that we can utilize and so if we go over to here, this should be the open source one. So making sure that this is indeed the official one. It is over here. And so I just need a simple use case. I'm going to copy this over to here and we will CD back a directory and we'll just say Codex. Um and we'll say I need a simple example to show off uh GitHub actions with Codex uh reference here.

[00:33:07]Okay, so please create me a simple workflow and then we will verify that workflow in just a moment, okay?

[00:33:17]Okay, so let's take a look at what we have here.

[00:33:24]Hold on here. One second.

[00:33:26]Sorry, yep. So we'll go up into GitHub action or GitHub folder workflow demo.

[00:33:30]Let's see what we have. So we have what Codex should focus on in this repository. Give me a quick tour of this example repo. So it says workflow dispatch inputs focus.

[00:33:43]Okay, I'm not exactly sure. I mean folks, I made a GitHub actions course so you know, I know this stuff but like this usually is like I think a manual a manual one, right? So here uh you're generating a short demo report for GitHub actions.

[00:33:59]Look through this repository and produce a concise report.

[00:34:03]Keep it clear. Export it out as this file. Um Mm.

[00:34:10]Okay.

[00:34:12]So before we do that, I'm going to go ahead over to my repository here, wherever well, wherever it is. Up over here.

[00:34:18]And I'm going to go into my settings.

[00:34:21]And in here there should be a section for um secrets.

[00:34:28]And we will go to actions.

[00:34:30]And we'll set this at the repo level.

[00:34:34]And this will be OpenAI API key.

[00:34:38]And we will bring in that key. So, I'm looking for where that key is. I still have it.

[00:34:47]Uh or maybe I don't anymore.

[00:34:50]Which is fine. I can go make a new key.

[00:34:53]Making new keys is fun.

[00:34:55]So, go here. I'll just delete this old key. Revoke.

[00:34:58]We'll create ourselves a new key.

[00:35:00]GitHub key. And we will create that key.

[00:35:04]And then we will copy it. We will go over to here. We will paste it in. We'll hit add secret.

[00:35:09]Okay. So, now we have the secret for this repository, which is the Codex uh example repository.

[00:35:16]I don't know if this is really the right approach, but I'm going to do this anyway. So, check out the repository run Codex.

[00:35:22]And then generate report.

[00:35:24]Workflow dispatch inputs.

[00:35:27]I hover over, it will tell me how it works. You can create workflows.

[00:35:31]Run workflow button. So, that's what I was expecting this to be. Okay. So, what we'll do is we'll now go ahead.

[00:35:38]Add workflow. And we will now push this here.

[00:35:41]I usually don't do manual workflows.

[00:35:45]And I mean like it'd probably be more practical to have it like react to content and stuff like that, but it's fine. If you took my um Claude Claude course, you'll already have an idea of how that stuff works.

[00:35:56]And so, I'm going over to here.

[00:35:59]And we'll give it a refresh. And so, it is in here.

[00:36:02]We will go to actions.

[00:36:06]And I'm looking for where it Oh, here it is. Codex demo.

[00:36:10]And so, we can run this workflow.

[00:36:13]Oh, cool. You can even change the prompt.

[00:36:15]So, you can ask questions about it.

[00:36:17]That's kind of cool. And we'll run it and we'll see what results we get back, okay?

[00:36:21]All right. So, we're back. And let's take a look here.

[00:36:28]And so, here we can see three folders suggested next demo to run.

[00:36:33]Um, and so it generated out. So that's what we wanted to do. I wonder if it actually placed it in the repo cuz it might have dropped it right in here.

[00:36:41]Um Did it just generate it in place?

[00:36:47]I mean, I'm fine with that. I don't really necessarily need it anywhere else, but it is right here. Let me go down here for a second.

[00:36:53]It says codex demo summary.

[00:36:58]And then Oh, it just prints it out. Okay. So I'm thinking it didn't commit it to the repository.

[00:37:05]And it's just putting it out here.

[00:37:08]Cool. And so we go back over to our top layer here.

[00:37:12]Yeah, and I mean, that's fine. So it did exactly what we needed it to do.

[00:37:16]And there you go. Okay.