At DevDay (2026-09-29) OpenAI shipped reusable Codex Cloud environments: publish a project setup (repos, deps, tools, network secrets), then each task runs in its own VM workspace and can continue while your laptop sleeps. Docs: learn.chatgpt.com/docs/cloud and Help Center. Rolling out to Plus/Pro and workspace plans; saved VM state recoverable ~7 days by default. No invented SWE scores.

Key Takeaways

  • ✓Official: learn.chatgpt.com/docs/cloud; Help: Using Codex Cloud (recently updated)
  • ✓Flow: create/publish environment on web/desktop → Codex inspects GitHub repos & installs deps → start tasks from any supported surface including mobile; each task is isolated
  • ✓SiliconANGLE (Sep 29): Plus VMs are half the CPU/RAM of Pro/Business/Enterprise; no GitLab/self-hosted GHES yet; no computer/browser use in cloud environments
  • ✓Saved VM state recoverable ~7 days after last start/resume by default; Enterprise sharing covers setup, not other people’s tasks
  • ✓Legacy Code Review / Linear / GitHub integrations stay on Codex Cloud (Legacy); migration is opt-in
🧭

Finished reading? Check pricing & compare GPT-6 Sol

Compare 29+ dev plans & simulate token costs vs $20/mo subscriptions

🔬

In-Depth Technical Analysis

Why it matters

Local coding agents stop when the laptop sleeps. OpenAI’s DevDay (2026-09-29) Codex Cloud reusable environments turn repo setup, install scripts, tools, and network credentials into a publishable template so each task can run in its own cloud VM and continue from web, desktop, or mobile. Canonical docs: Codex Cloud and Using Codex Cloud; contemporaneous coverage: SiliconANGLE.

Architecture

A published environment binds GitHub repositories, install/start skills, outbound network presets, and network secrets (proxy injects real values for allow-listed domains). Each new task gets an isolated workspace; uncommitted work stays with that task across devices. Help Center: saved VM state is recoverable for about 7 days after last start/resume. Enterprise sharing exposes setup to teammates, not their tasks or repo ACLs. Code Review / Linear / GitHub integrations remain on Codex Cloud (Legacy) until you migrate.

Evidence

No official SWE-bench-style scores for this product surface. Documented limits: no GitLab / self-hosted GHES yet; no computer/browser use in cloud environments; Plus VMs are about half the CPU/RAM of higher tiers (SiliconANGLE). Validate on your own install success, resume reliability, and PR quality—do not treat marketing workflow demos as coding benchmarks.

Try it

In ChatGPT web/desktop: Work in → Cloud → create/select environment → connect GitHub → Get started → Publish → Start a new task (mobile can drive published envs). Prefer network secrets + tight egress. Codex Cloud is not covered by OpenAI’s BAA—do not process PHI. Pilot on a fork before migrating Legacy review workflows.

Action HubReady to adopt this in production?

Benchmark side-by-side against alternatives, or calculate monthly token cost vs subscription break-even.