Meet the all new Codex Cloud
Read the Portuguese translation →
Author: OpenAI · Watch on YouTube
Video authored by the channel shown, not by IANIA; all rights belong to the creator. Transcript and summary generated automatically; the original-language content is preserved.
Original language: English
Original video: Meet the all new Codex Cloud · Channel: OpenAI · 03:10 · Watch on YouTube
Topics: AI agents, Software engineering with AI, AI developer tools
Summary
Section titled “Summary”The video introduces Codex Cloud environments through a task that keeps running after the user closes their computer. Tasks can be resumed or updated from a phone, including through voice, while the user works on other things. Users can create and publish named environments with repository setup, networking, environment variables, and secrets configured, then reuse them as snapshots for separate tasks and share them with a team. When a task finishes, the user can continue working on the cloud computer, create a PR, use code review, or ask Dot to handle the PR.
Key points
Section titled “Key points”- Tasks launched in the cloud keep running even after the user closes their computer.
- Users can return to a running task and add to it from a phone without interrupting it.
- Voice sessions let users kick off work while away from their computer.
- A chat-based onboarding flow helps configure a new environment for the selected repositories.
- Environment setup can include networking, environment variables, and secrets.
- Shared environments can let users override secrets inline or from their personal vault.
- Publishing an environment creates a named snapshot that can be reused to start separate tasks.
- Teams can use the same environment instead of repeating setup for each task.
- Completed tasks can be used on the cloud computer, sent through a PR or code review flow, or assigned to Dot for PR creation.
Chapters
Section titled “Chapters”| Start | Chapter | Summary |
|---|---|---|
| 00:02 | Tasks that keep running in the cloud | The user explains that a cloud task keeps running after they close their computer and can be resumed or updated from a phone, including by voice. |
| 01:02 | Creating a cloud environment | The user describes creating an environment for a project involving laser animations and configuring it through a chat-based setup flow. |
| 02:06 | Reusable environment snapshots | Published environments become named snapshots that can start multiple separate tasks and be used by the whole team. |
| 02:39 | PRs and code review | After the task returns, the user can work on the cloud computer, create a PR, use code review, or ask Dot to make a PR. |
Quotes
Section titled “Quotes”the task still runs. — 00:32
I can even use my phone. — 00:32
there’s a great chat-based onboarding flow — 01:34
So you don’t ever need to do that setup like over and over again — 02:06
I can still use this task on this cloud computer. — 02:39
Concepts and entities
Section titled “Concepts and entities”Codex Cloud, OpenAI, Astra, Dot, PR, secrets
Full transcript (original language)
Section titled “Full transcript (original language)”00:02 Oh, are you filming already? Let me wrap this up. One second. And because this feels like science fiction already, you know, make the lasers like animate, like, I don’t know, like the meaning of life. Okay, there we go. Boop! All right. What’s this video about again? Oh, right. Cloud environments. Sorry, this is awkward. Oh, wait. Actually, I don’t need to leave this open anymore because I kicked this task off in the cloud. Which means I can close this mad boy
00:32 and the task still runs. Wow, that feels so good. It’s so freeing. And I can pick that task back up whenever I want because it’s running in the cloud. I can even use my phone. I can just add to the running task without interrupting. And what I love, it even allows for voice. I can pop in my headphones and go for a walk and I can kick off a voice session. And everything. And that will just run and let me know when it’s done.
01:02 I have a hunch this might take a while. I’m pretty excited about this new environment that I just built. So I found this device and I’ll probably buy it. It lets you play animations with actual lasers. I had Astra figure out the format and generate a simulator. Turns out you can just laserify things. And again, because I never know when the spark of an idea might show up, I want to be ready and let it build while I do other tasks. Whatever that might be. So I use the cloud environment
01:34 setting right here to make a new one. When these get started, there’s a great chat-based onboarding flow where you give it the repos that you’re wanting. And the flow does research about what your repo might need for setup. And I’m talking about all sorts of advanced configuration, like what networking it needs. It can do environment variables and secrets. Now, if you’re sharing this, you can even allow a user to override it with their own secrets, either inline or from their personal vault.
02:06 And then once you publish it, you now have a named environment in which you can kick off new tasks. Now, what’s nice about this is it’s a snapshot. So you don’t ever need to do that setup like over and over again like we do, right? You can run multiple separate tasks and use this environment as the starting point. This just lets you dive into what you’re building and your whole team gets to use it, too. This is such a huge improvement from how we used to do things. Oh, it returned.
02:39 Classic. And as you can see, I can still use this task on this cloud computer. Now, I can have it create a PR and run it through that normal flow. Or I can use that brand new code review flow, which I love, BTWs. And there’s more. I can also just have Dot take care of that while I go run and buy that laser machine. Dot, can you go ahead and make a PR for our records?
03:10 Make sure that things look good and test and flag anything that you need me to approve. Don’t panic. Well played. Well played.