I’ve been reading the DevDay 2026 recap the morning after the Fort Mason keynote — same habit I have with any big AI launch: skip the slogans, find the one change that would actually change how I work. For the Codex track, that change is Codex in the cloud: reusable development environments you can start from a computer, a phone, or a browser, and keep running after you shut the lid.
People have been calling this week “Codex Day.” OpenAI didn’t. What shipped sits inside OpenAI DevDay 2026 (Tuesday, 29 September 2026, San Francisco) — their “biggest yet,” with more than 20 major announcements across ChatGPT, Codex, models, and new builder tools. This post sticks to the cloud piece. I’ll cover the refreshed CLI, desktop code review, Sol, Ultrafast, and Security Cloud in follow-ups so each one stays readable.
What Codex Cloud actually is
OpenAI’s line is simple: run Codex wherever you need it. The useful part for me is the reusable environment. Instead of spinning a fresh setup for every task, you keep an approved workspace — settings, permissions, the boring team defaults — and send work into it from more than one device.
If a long agent run is chewing through a repo, I can leave the desk. The task doesn’t have to die with the laptop battery. That sounds small until you’ve watched a local session die mid-refactor because school pickup started.
Docs pointer OpenAI published with the recap: learn.chatgpt.com/docs/cloud. Product surface: chatgpt.com/codex.
Who gets it (and what the recap doesn’t say)
Access listed in the recap: Plus, Pro, Business, Healthcare, Education, and Enterprise.
What the recap does not publish: cloud-minute caps, concurrency limits, or an add-on price sheet. I’d treat “available on these plans” as eligibility, not as “unlimited.” Before I budget a team rollout, I’d check the live cloud docs and the plan admin screens — not a screenshot of the keynote slide.
Why I’d care this week
Most coding-agent demos still assume you’re glued to one machine. Cloud environments flip that: the agent keeps a stable home, and you check in when you can. For a parent who’s also shipping code, that matches real days better than “leave the laptop open on the balcony.”
I’d try one concrete path first:
- Pick a small, low-risk repo task (docs tidy, test fix, dependency bump — not production secrets).
- Start it in Codex Cloud with the team’s approved settings if you have them.
- Close the laptop for 20 minutes. Come back on phone or another browser and see whether the run is still coherent.
- Only then move a real PR-shaped task into the same pattern.
Watch this first
OpenAI’s product video is clearer than another screenshot wall:
If you want the full stage context, the DevDay 2026 keynote is the long cut.
What I’m not claiming yet
I’m not saying Codex Cloud replaces a careful human review. I’m not inventing minute prices or SLA numbers OpenAI didn’t publish on the recap. And I’m not renaming DevDay into a separate “Codex Day” product holiday — that’s shorthand, not OpenAI’s label.
What I’d do next
If you already pay for Plus or above, open Codex Cloud docs, run one boring task end-to-end with the laptop closed once, and write down what broke. That note is more useful than another AGI headline.
