{
  "video_id": "vQebObsd_Cw",
  "channel_slug": "techwithtim",
  "channel_handle": "techwithtim",
  "title": "I Deployed an AI Programmer. It Never Sleeps",
  "duration_seconds": 1437.0,
  "url": "https://www.youtube.com/watch?v=vQebObsd_Cw",
  "upload_date": "",
  "transcript": "I'm willing to bet you've probably seen\nsomething like this. Someone walking\naround with their laptop screen half\nopen and you know that if they're a\nprogrammer, they're waiting for their\nagent to finish running. I know that\nthis has been me many times. Even the\nother day at the airport, I was walking\naround with my laptop screen open\nlooking like a complete idiot because I\nneeded my Claude Coder Codex agent to\nfinish running. Now, this is a problem\nthat doesn't need to exist because you\ncan actually run agents in the cloud if\nyou configure them correctly and that's\nwhat I'm going to show you how to do in\nthis video. I'm going to show you how we\ncan set up Codex so that it's running\n24/7 in the cloud so we never need to\nhave our laptop screen half open walking\naround looking like a complete idiot.\nSo, effectively, what I'm going to show\nyou in this video is how you can run\nlong-running agentic coding tasks in the\ncloud self-hosted using your existing\nsubscriptions. This means that you can\nbe on the go and that you can actually\ntrigger a task to run from your phone.\nYou can reconnect to it from your\nlaptop, but the important part is that\nif that screen closes, your task to keep\nrunning, which means if you're sleeping\nor if your Wi-Fi goes out or if you're\nin an area where you just can't open\nyour laptop, you can still trigger these\nagentic tasks to run and you can\nactually run them on a schedule, which\nwe'll look at a little bit later. Now,\nfor this video, we're going to use\nCodex. The reason for this is that\nCodex, in my opinion, is currently the\nbest agent out there. Specifically,\nwe're going to be using Codex CLI. This\nis something that can run in a headless\nenvironment and that we can execute from\nour phone, which I'll show you later.\nNow, Codex is currently leading in many\nof the different benchmarks out there.\nIt can actually run faster than Claude\nCode and, more importantly, is\nsignificantly cheaper to use, especially\non a subscription basis in terms of the\nusage that you get. It's practically\nunlimited if you're not running it, you\nknow, in 20 different sessions 24/7. So,\nI promise we'll get into the setup, but\nI just want to emphasize why this is\nworth doing. Now, if you're going to run\na coding agent on your own computer,\nyou're going to run, you know, like\nClaude Code or Codex CLI or just Codex\nor whatever, you do need your computer\nto be open and that's because it's using\nyour local execution environment or your\ncompute to actually run a terminal\ncommand or modify a file or whatever it\nis that's going on. Now, this is fine in\nmany situations when you're actually\ngoing to be actively on the computer,\nyou're working on something, you're\nworking with it kind of turn by turn,\nand every prompt you give is taking, you\nknow, a maximum of a few minutes.\nHowever, if you want to do a task that's\ngoing to take 8 hours or you want to run\na task every day at a certain time or\nyou just want something to run for a\nsuper long period of time, but you're\nnot able to actually have your computer\nopen or needs to be in your backpack or\nwhatever, obviously this doesn't work.\nAnd even if you could run it on your\nlaptop, if you lose internet, if you\nlose battery, if you close it, if for\nsome reason it turns off or restarts or\ngoes to sleep or whatever, you're going\nto lose all of that progress, which\nobviously is very inconvenient. So, the\nsolution here is to have a VPS or\nvirtual private server where you can\ndelegate long-running tasks. It doesn't\nmean you're not going to run stuff\nlocally on your own computer. When you\nwant to do something and you need to\nclose the lid of your laptop or you know\nthat it's not going to be available for\nthe next 8, 10, 24 hours, whatever, you\ndelegate it to the VPS. So, the basic\nidea is in this video I'm going to show\nyou how to spin up a VPS, how to install\nCodex CLI on it and authenticate with\nyour existing subscription, and then how\nyou can control it from your phone or\nfrom your laptop, however you want to do\nit, so you can delegate those\nlong-running tasks and have everything\nhandled securely, privately on that\nvirtual private server. This way,\nanytime you need something that's going\nto take a few hours, you want to run\nsomething on a schedule, do it on the\nVPS and then the active work you do on\nyour own computer so you separate things\nout. Now, there's three main reasons why\nthis works. First, a virtual private\nserver doesn't go to sleep, it's\navailable 24/7 in a secure environment\nwith a hardwired connection so the\ninternet just doesn't go out. You keep\nall of the data because you're\nself-hosting everything and you can keep\neverything in a secure environment. And\nimportantly, you also have data center\nspeeds. So, if you're going to be in a\nlow internet environment, which I know I\nam a lot when I'm traveling, you can\njust use the virtual private server and\nget significantly faster speeds for\ndownloading something, uploading\nsomething, getting a data set, training\na model, whatever it is that you need to\ndo. So, anyways, that is kind of the\nquick brief here and why this is worth\nsetting up. Now, let me show you exactly\nhow to do it. Now, the first thing we're\ngoing to need here is a virtual private\nserver or VPS. But, you can get any VPS\nthat you want, but for this video, I'm\ngoing to be using Hostinger because they\nhave some of the best virtual private\nservers on the market. They are the most\nreliable and they're a long-term partner\nof this channel, meaning I can give you\nguys an additional discount. So, I would\nrecommend going with the KVM 2 plan if\nyou want to follow along with me here,\nbut you can see all of the options they\nhave. I'll leave a link to this in the\ndescription. I'm going to go with KVM 2.\nAnd then from here, what I'm going to do\nis deploy and provision my virtual\nprivate server. Now, because I have a\npartnership with Hostinger, if you go\nhere and apply the code Tech With Tim,\nyou'll get an additional 10% off as long\nas you're using a 12-month or 24-month\nsubscription plan here, which gives you\na massive discount. So, regardless, pick\nyour plan, pick the duration of what you\nwant, apply the discount code. You can\nchoose the region that you want to have\nthis applied in. My case, Indonesia\nbecause that's where I'm located right\nnow. And then you can choose OpenAI\nCodex where it's automatically going to\ndeploy this and install some of the\ndependencies for you, which will save\nyou a lot of time. Hostinger also has a\nlot of other one-click deployments if\nyou want to have a look at them. But, of\ncourse, for this video, we need Codex,\nso we'll apply that and then go ahead\nand press on continue. Now, if you're\nfollowing along with me here, it may ask\nyou to generate a root password for the\nserver. If it does that, you can just\ngenerate a random one and then copy it\nobviously, save it, and make sure you\ndon't leak it to anyone else. I will\ndelete this server afterwards. So, I'm\ngoing to go ahead and press on next. I'm\ngoing to add the malware scanner because\nit's free and obviously just good idea\nto have on the VPS. And then press\nfinish and it's going to take a minute\nor two here to provision the VPS. Once\nit's done, I'll be right back. I'll show\nyou how we can connect to it and then we\ncan proceed to the next step. Okay, so\nmy VPS is now deployed. And what I can\ndo is go to the VPS dashboard here to\nview all of the different controls and\nyou can see that I have Codex deployed.\nNow, at this point, I'm going to assume\nthat you have some virtual private\nserver. Whether you're using Hostinger\nor not doesn't really matter. What we're\ngoing to need to do though is find the\nIP address of our server so we can SSH\ninto it and start configuring a few\nthings before we connect it to our phone\nand before we start setting up scheduled\ntasks, all of that kind of stuff. So,\nwhat I'm going to do is just copy this\nright here, the SSH command under root\naccess. Also, right make sure you have\nyour root password from before. If you\nforgot it, you can change it right here.\nAnd what I'm going to do is open up a\nterminal. So, you can see I've got a\nterminal open on my computer here. Let\nme just clear this and make it a little\nbit larger so you guys can see it. And\nwe're going to paste the command SSH\nroot at and then the IP address of our\nserver. Again, if you're using a\ndifferent VPS provider, make sure you\nget the IP address, you get the\nusername, which is typically root, and\nthen you know the password uh for\nsigning in. So, let's go ahead and press\non enter. We're going to go yes and just\nsay okay, we can connect to this host,\nand then we're going to paste in our\npassword. When you paste the password,\nyou won't see anything here, it will be\ninvisible. So, just paste it and then\npress enter. Okay, so you can see that\nI'm now signed in to my virtual private\nserver. You'll see that if you see root\nat and then some name here, in this case\nit's SRV, that's just what Hostinger has\nnamed So, now what we need to do is just\nverify that Codex is installed. If it's\nnot, I'll show you how to install it in\ncase you didn't use the one-click deploy\nfrom Hostinger. We're then going to need\nto sign in with our account so we can\nstart using our existing subscription or\nwe can use an API key if we want, but\nthat's going to be quite expensive. Then\nafter that, I'm going to show you a few\nquick setup steps just to make this work\nreally well. Then we're going to connect\nit so we can trigger it from our phone\nand I'll show you overall how this\nworks, automations, all that kind of fun\nstuff. Okay. So, first things first, you\ncan attempt to run the Codex command.\nNow again, if you used the one-click\ninstall option from Hostinger, it should\nautomatically be installed for you. But\nif it's not, what you're going to want\nto do is the following. I'll leave this\nlink in the description. It's just the\ndocs from Codex and you'll see that\nthere is a setup command here. So,\nthere's a curl, you can just copy this,\npaste this as the command and run it and\nthat that install the Codex CLI for you.\nOnce it's installed, you may need to\njust reconnect to the server again so\nthat your path updates because sometimes\nthe path variable needs a second to\nrefresh. We're not going to talk about\nthat too much in depth, but if you\ninstall it and the Codex command doesn't\nwork, then just refresh the terminal.\nSo, just close it and re-SSH back in and\nit should work. So, from here, we should\nbe able to trigger the Codex command.\nFrom here, we're going to go to sign in\nwith device code or if you have your own\nAPI key, you can use this, but it's\nprobably going to be better to use your\nexisting ChatGPT subscription. So, I'm\ngoing to go sign in with device code and\nwhat it's going to say is go to this\nlink. Okay, so we're going to copy this\nand just paste it in our browser and\nthen we're going to paste this code\nright here from the terminal. So, let's\ncopy this, go back. Okay, we're use my\nemail here and we're going to paste this\ndevice code and then it should allow us\nto be signed in. Okay, so let's paste\nthis and press on continue. Okay, so\nfrom here, it says that we're signed in\nnow and we can go ahead and press on\nenter. From here, we're just going to go\nyes, continue, that's fine and you'll\nsee that we've now open up Codex and\nwe're able to start triggering\nsomething. So, we can say, you know,\nhello world and it will start giving us\nsome input. Now, I'm not going to give\nyou a full tutorial on how Codex works\nhere. There's a lot of different slash\ncommands that you can use. I'd recommend\ntriggering the fast mode here even\nthough it's going to use more usage,\nit's going to run a lot faster and if we\nkeep going, you can see there's a lot of\nother stuff that you can run and that\nyou can do. Okay, so Codex is now\nworking. We have it running on our\ncomputer. If we want to exit out of\nthis, we can hit control C on our\nkeyboard. That should quit out of Codex\nand we can type clear just to clear\nwhatever's in the terminal so we can\nhave kind of a fresh screen. Now, what I\nwant to do next is I want to show you\njust how to connect to GitHub because\nit's going to be very useful to have\nCodex connected to GitHub so that it can\ncreate repositories for us, do pull\nrequests, trigger automations, etc. So,\nif you don't already, I would suggest\nthat you create a free GitHub account.\nYou can do that just by going to\ngithub.com. You don't need to pay for\nanything and then what we're going to do\nis the following. So, first we're going\nto go to our little avatar here, and\nwe're going to go to settings. Now, from\nsettings, we're going to scroll all the\nway down to our developer settings, and\nwe're going to create an API key that we\ncan use in our virtual private server to\nconnect to our GitHub account. You can\nactually even give Codex its own GitHub\naccount if you want, but I like to\nconnect it to mine and just restrict the\naccess that it has. So, what I'm going\nto do is go to personal access tokens\nhere and go to fine-grained tokens. From\nfine-grained tokens, we're going to go\ncreate new token, and what I'm going to\ndo here is just name this What are we\ndoing here? You know, Codex VPS, okay?\nFor the expiration, I'm just going to go\nno expiration, so we don't need to\nchange it. I'm going to go all\nrepository, so it can access all of my\nrepositories, and I'm going to start\nsetting the permissions that I want\nCodex to have. Now, if I want this to\nhave the ability to create and delete\nrepositories, I need to trigger\nadministration. And if I want it to be\nable to edit contents of the repository,\nso make it commit or view it, I need to\nadd contents. Also, I want it to be able\nto make pull requests, I need to add\npull requests. There's a lot of things\nhere, but for most of you, you're\nprobably just going to need these. Now,\nfor all of these, I would suggest you go\nread and write. Again, be careful, but\nwhat this is going to do is allow it to\ncreate, read, delete whatever\nrepositories. Contents, same thing. This\nwill allow it to create contents, make\nbranches, etc. And then for pull\nrequests, this will allow it to pull\nrelated comments, assignees, etc. Now,\nthis is one you might want to be careful\nwith because if you put it to read and\nwrite, it can delete repos. So, if you\njust want to test it to start, make this\nread only, which I will do right now.\nBut if you want it to be able to make\nnew repos for you and stuff, then you\nwould have to go to read and write.\nOkay. So, from here, we're going to\ngenerate token, but we're going to do\nthat in 1 second after we install a tool\ncalled GH in our virtual private server.\nThis is essentially a GitHub tool that\nCodex will be able to use to do GitHub\nrelated commands. Let me show you how it\nworks. Okay, so from our terminal, we're\ngoing to run the command apt install\ngh-y,\nokay? So, exactly like I have on screen\nand go ahead and press on enter. It's\nthen going to install GH, which is\nGitHub effectively, which will take a\nsecond. And if we want to test if this\nis working, we can run GH. Now, after\nthat, we're going to type GH and then I\nbelieve the command is uh not log in, it\nmight be like Okay, so sorry, it's GH\noff and then log in, okay? And then what\nwe're going to do is authenticate with\nGitHub. So, to do this, we're going to\npress github.com\nhttps and then we're going to use our\nGit credentials, okay? And we're going\nto paste an authentication token. So,\nthen what we're going to do is go back\nhere. We're going to generate this\ntoken. Make sure you don't share it with\nanyone and we're just going to paste it\ninside of here, okay? So, we're going to\npaste our authentication token that we\njust generated from the previous step.\nNow, you'll see it's logged in. You can\nsee I'm logged in as Tech With Tim. So,\nnow that I'm logged in, my Codex should\nhave the ability to actually do things\nrelated to GitHub. And if we just want\nto test that, we can type Codex like\nthis and we can just tell it. We can\nsay, \"Hey, you have access to the GH\ncommand and you want to use the username\nTech With Tim. Can you just tell me a\nfew repos that you have access to just\nto verify that the GitHub command is\nworking?\" And by the way, if you're\nwondering what I'm using to dictate\nhere, I'm using a really cool tool\ncalled WhisperFlow. It's free to use. I\nhave a long-term partnership with them,\nso I'll leave a link to it in the\ndescription. You can see I am an\nabsolute power user and it is the best\nvoice dictation or AI voice dictation.\nIt actually has some really cool\ninsights now where you can see exactly\nwhere you're using it, the streaks. Very\ncool, very good and you can see that I\ncan speak at 260 words per minute as\nopposed to my normal typing speed, which\nis a lot slower than that. So, anyways,\nI'm going to go ahead and press on enter\nhere and it's just going to go and try\nto use this GH command and let's make\nsure that it works. Okay, so you can see\nthat it's giving me a whole list of\nrepos here that it has access to,\nprivate and public, which means this is\nworking and GitHub is now installed,\nactive and we can move on to the next\nstep. Okay, so the next thing we're\ngoing to do is trigger this from our\nphone, which means we'll essentially\njust be able to control the virtual\nprivate server and use Codex CLI from\nour mobile device and I'm going to walk\nyou through how to do that. Now, the\nfirst thing we need to do here is\ninstall a tool called tmux, okay, or t m\nu x. What this is going to allow us to\ndo is persist an SSH session even when\nwe're not connected to the virtual\nprivate server. The reason why we're\ngoing to need this tool, we need to run\nthis command that I have right here, is\nbecause if we connect to the virtual\nprivate server and we do something, so\nwe say, \"Hey, Codex, go do this thing,\nrun CLI.\" And then we close the\nterminal, by default whatever was\nhappening is going to be kind of quit\nout of her, it's going to be, you know,\nstopped, right? So, what tmux will allow\nus to do is run what's called a\npersistent session. So, even if we\ndisconnect and we're not currently on\nthe virtual private server, whatever\nwe're doing will keep running in the\nbackground, which is super important and\nkind of the whole point of this video.\nSo, we're just going to install tmux\nlike this, apt install tmux -y. I'm\ngoing to quickly show you two or three\ncommands that you need to be aware of\nand then I'm going to show you how we\ncan set this up from our phone, which is\nreally easy. So, once you have tmux\ninstalled, you should be able to run\ntmux like this, okay? Now, when you just\nrun tmux, let me just um exit out of\nthis by typing exit, what it's going to\ndo is bring you into one of those\npersistent shells. Now, if we want to\nview all of the shells that are\ncurrently active with tmux, we can type\ntmux ls. We can see nothing is running\nright now because I had started a shell,\nbut then I exited out of it, which by\ndefault is going to close it. Now, what\nwe can do instead though is we can run\ntmux new -s and then we can give this\nshell a name. So, in this case I'm going\nto call it Codex. Now, when we do this,\nit's going to bring us again into a new\ntmux shell here. We can run anything\nthat we want, so we can run, for\nexample, Codex like this and let's just\nsay\nhello world. And now what I'm going to\nshow you is that if I close this virtual\nprivate server session and then try to\nre um kind of enter into it, I can get\nback into the shell without having any\nof this information lost. So, let me\nshow you what I mean. I'm just going to\nquit out of my terminal. Let's reopen\nthe terminal and re SSH back in. Okay?\nLet me just get the password. Okay, and\nfrom here what I can do now is type tmux\nls. You can see the codex is still\nrunning and then what I can do is type\ntmux attach. If I just type tmux attach\nby default it's going to attach to the\nmost recent shell, which is going to be\ncodex. Now, if I want to attach to a\nparticular shell because you can have\nmultiple running, then I can do\n-t, sorry, and then codex. And what this\nis going to do now is bring me back into\nthat shell. Now, again, if you're not\nsuper familiar with virtual private\nservers, you may not know why this is\nimportant, but this again allows us to\nhave this persistent shell so that it\ncan be stored and running in the\nbackground no matter what. Okay, so for\nnow we're going to leave this shell\nrunning on my computer and we're going\nto move over to our mobile device where\nI'm going to show you how we can now\nconnect to the virtual private server so\nwe can trigger tasks on the go from our\nphone. Okay, so from our phone here,\nwhat we're going to do is go to the App\nStore and we need to download what's\ncalled an SSH client. Now, you can use\nanything that you want, but the app that\nI'm going to recommend here is called\nTermius, okay? It says modern SSH\nclient. It's free. You don't need to pay\nfor anything, but you need some kind of\nSSH client. You can do this on Android.\nMaybe they have the same app. If not,\nyou're just looking for any SSH client,\nokay? So, what we're going to do is just\nopen up this application and effectively\nwhat we're going to do is just go and\nsign in to our virtual private server\nfrom our phone. So, what I can do here\nis press on the plus button. I can go\nnew host and I can start putting in this\ninformation. Now, for the label, I'm\njust going to call this codex\nOkay, CLI. For the IP or host name, I'm\ngoing to use the same one that I was\nusing on my computer. So, that's\n187.77.121.81.\nIf you're wondering how do you find this\nhost name, you can see it up here on my\ncomputer. I'll hopefully have this on\nthe screen as well. It's the same thing\nthat we were SSHing into from our\ncomputer. And if you go back to\nHostinger, you can actually see it right\nhere or from wherever you deployed your\nvirtual private server. If we keep\ngoing, what we'll be be to do is use\ncredentials so we can set our username.\nThis is going to be root, and then the\npassword is going to be the same\npassword that you used previously as the\nroot password for the server. Okay, so\nI've got all of those details in.\nThere's not really anything else that we\nneed to do here. We can just go ahead\nand press on enter, and then wait a\nsecond here, and it should start\nconnecting to this server for us. So, if\nI press on it now, it's going to say,\n\"Hey, do you want to trust this device?\"\nI'm going to go, \"Yes, I do want to\ntrust this.\" And then it's going to\nbring me right into my server. Now, from\nhere, if we want to change what this\nlooks like, you can see in this app,\nthere's a little button, so I can change\nlike do I want it to be light? Do I want\nit to be dark? I think it's going to be\neasier for you guys to read it in kind\nof this light mode here, this yellowy\ncolor theme. And we can make the text\nsize larger as well. One second.\nUm let me move this here. Okay, so\nthat's pretty much it. You can set, you\nknow, how you want it to look, and then\nfrom here you can type anything just\nlike you would if you were on your\ncomputer. So, what we want to do now is\nwe want to attach to that tmux session\nthat we were running here, so that we\ncan start using codex. And if we don't\nhave an existing session, we should just\nmake a new one, so that again, if we\ndisconnect and reconnect, we're not\ngoing to lose that task. So, what we can\ndo is type tmux, and then same thing, ls\nif we want to view what we have running.\nWe can see that we have codex, and it's\ncurrently attached. So, I can do tmux,\nokay, and then I'm going to go attach\nlike that, -t, and then codex like so.\nAnd you'll see that I'm now inside of\nhere. It's kind of glitching out on my\ncomputer because, um what do you call\nit? I'm connected on my phone. But you\ncan see that if I type hello or\nsomething, it's appearing on my computer\nas well as on my phone. Now, I know it\nlooks a little bit weird, and that's\njust cuz we're attached from two\nsessions at the same time, but you can\nsee now that I can trigger a task. I can\nask it to write code. I can get it to do\nsomething from my mobile device. And\nthen again, importantly, if I like close\nthe session here on my computer, and I\ngo back to my phone, you can see it's\nstill running, and it's still going to\nbe able to execute the various tasks.\nAnd then again, if we quit out of this,\nso let's get out of our session, and\nlet's go back in, you can see that it\nwill bring us back here and then if I\nwant to just completely close out of\nthis, I can press on it, press close and\nthen if I reconnect here, so give this a\nsecond to reconnect. Same thing, we can\ndo tmux\nand then attach and then we'll be back\nin the Codex session where we can start\nasking it to do anything that we want.\nAnd I'm going to change the color theme\nhere so it's a little bit easier to read\nbecause it looks like it's like messing\nup here. Okay, so this one looks good.\nAnd then we can start triggering various\ntasks. So just give you an example of\nsomething we can do here, I'm just going\nto paste in a URL. This is one of the\nGitHub repos I have access to and I'm\njust going to say, \"Hey, can you review\nall PRs in this repo?\" And I know I'm\nkind of spelling some of this wrong but\nthat should be fine. Let's go ahead and\npress on enter and let's see if it can\ngo and review those for us. Okay, so you\ncan see that it's reviewing all of the\nPRs right now. It's giving me all of the\nresponses and it's saying which one\nshould be approved, shouldn't be\napproved, etc. And now we're good to go\nand the same thing, we can close it,\nreopen it, go on our laptop, you get the\nidea. Now where this is going to become\nsuper useful is actually when we start\nrunning automation. So I want to show\nyou that now. I am going to go back to\nthe computer but keep in mind everything\nthat I do on the computer, you could do\nit from your phone as well. It's just\neasier for you guys to see on a bigger\nscreen. Okay, so I'm back on the\ncomputer, you can see I've reattached to\nthe tmux session where we are running\nfrom our phone and now we can continue\nworking. Now like I mentioned, I want to\ntalk about automations. Automations are\njust things that can run on a particular\nschedule. Now unlike Claude Code, Codex\ndoesn't have any built-in kind of\nscheduling feature although I'm sure\nthey're probably going to add that in\nthe future but if we want to set that up\nto run on our VPS, it's very easy and we\ncan create something called a cron job\nwhich is a huge advantage of having this\nvirtual private server. Now effectively,\nall we have to do is just tell Codex to\ndo this for us and say, \"Hey, every day\nI want you to do XYZ. Maybe I want you\nto review all of the code in my codebase\nand tell me if there's any security\nvulnerabilities. Maybe I want you to\nreview all of the PRs and automatically\nreject or approve. Maybe I want you to\nwrite a change log of anything that's\noccurred in this repo. Maybe I want you\nto update all of the readme files,\nwhatever, okay? So, what I'm going to do\nis just the following. I'm going to say,\nI want to set up a simple automation\nthat runs every single day using the\nCodeX CLI. I need you to create a cron\njob. This is the key term that you want\nto keep in mind, by the way, cron job,\ncuz that's what you want it to ask it to\ndo, that runs CodeX CLI on the repo that\nI just sent you above and reviews all of\nthe PRs and then creates a markdown file\nthat's uploaded to the repository that\nincludes the status of those PRs and if\nthey should be approved or not. This is\na silly automation, like it doesn't\nreally make sense to run this, but I'm\njust giving you an example of something\nyou could do. Where I'm saying, \"Hey,\nset up an automation. I want you to use\nCodeX CLI. I want you to create this\ncron job and execute this.\" Now, the way\nthat this is going to work is there's\nthis command called CodeX exec. And if\nyou run this, it's going to not bring\nyou into a CodeX session, but it will\njust execute whatever you ask it to do.\nSo, I can say CodeX exec and then like\ndo this thing. And it will just execute\nit and do it. So, we can set up a cron\njob that will do that for us. And I'm\njust going to go yes and don't ask for\nthese commands uh cuz it's asking us to\napprove this. So, effectively, what it's\ngoing to do is say, \"Hey, on this\nschedule that's going to be set up on\nwhat's called a cron job, which can run\non kind of an automated timing, run\nCodeX exec, which is going to trigger\nthis thing to happen, right? Where CodeX\nCLI is going to go and run this task and\nthen complete whatever it is that we\nasked it to do.\" So, you can see that\nit's currently creating this cron job,\nwe're just putting under a cron tab. It\nasked me just to approve the command,\nwhich I did, and you can see now that\nthe entry is installed and it's going to\nstart running this process. So, it's\ngoing to tell it, \"Okay, run this.\" And\nagain, the advantage of the VPS is\nyou're in an isolated environment, so\nit's not going to mess up your own\ncomputer. If it actually makes a\nmistake, you can always shut it down,\nit's not a huge deal. So, it's just\nrunning all of these cron um you know,\nterminal commands for us and it should\nset this up and then we will have that\nautomation running every single day.\nOkay, so just doing a dry run now to\nmake sure this is going to work. I'm not\ngoing to bore you guys and go through\nthis whole process. I just wanted to\nshow you that setting up these\nautomations is a good way to really\nutilize this VPS and have it running in\nthe background even when you're not\nmanually triggering tasks to execute.\nAnd again, the reason why you want\nsomething like this is so that if you\nwant something that's going to take a\nlong time to run, you just delegate it\nto the VPS, and you don't rely on you\nhaving a computer open. Again, you guys\ncan set up all these automations, you\ncan have it trigger, you can set up, you\nknow, MCP servers, and you can do really\ncool stuff using CodeXCLI, which is\ncurrently kind of the leading agent and\nharness for coding related tasks. So,\nthat's it, guys. I'm going to wrap up\nthe video here. If you enjoyed, make\nsure to leave a like, subscribe to the\nchannel, and I'll see you in another\nvideo.\n>> [music]",
  "transcript_chars": 30180,
  "ingested_at": "2026-06-19T16:31:39.451346+00:00",
  "source": "channel",
  "yt_meta": {
    "view_count": null,
    "like_count": null,
    "channel_id": null,
    "categories": null,
    "tags": null
  }
}