OpenAI gives Codex reusable cloud environments that work across devices
- ID
- 29908
- Status
- summarized
- Published
- 30 Sep 2026, 1:15 AM
- Fetched
- 30 Sep 2026, 7:23 AM
- Provider
- TechCrunch
- Category
- technology
- Original URL
- https://techcrunch.com/2026/09/29/openai-gives-codex-reusable-cloud-environments-that-work-across-devices/
- Source URL
- https://techcrunch.com/feed/
Summary
- Score
- 6.5
- Created
- 30 Sep 2026, 7:24 AM
- Tags
- Audience
- developersvibe_codersai_agent_userssaas_founders
What happened
At its Dev Day on Tuesday, OpenAI announced that Codex cloud development environments are becoming reusable and persistent rather than one-off remote sandboxes, accessible from a computer, a phone, or the cloud, with shared team settings and permissions. The refreshed Codex CLI adds voice-directed task start/control, a new /agents view for delegating and tracking multiple tasks, and improvements to prompt editing, session resuming, worktrees, and a cleaner terminal UI. Codex also moves into the ChatGPT desktop app as a code review surface that summarizes changes and can run automatic reviews before feedback is posted to GitHub pull requests or GitLab merge requests, alongside unspecified security and API enhancements.
Why it matters
The persistent-environment change is the one with real consequences: if Codex environments carry approved settings and permissions and are shared across a team, then credentials, dependency versions, and network access now live in a long-lived workspace instead of dying with each task — so a small team needs a deliberate answer to who owns that config and what it can reach. Voice control plus the /agents view also means one person can supervise several parallel tasks from a phone, which changes how you scope work (smaller, independently verifiable units) rather than how many tools you install. Note the text gives no pricing, region availability, or Malaysia-specific detail, so treat rollout and access as unconfirmed.
Discussion angle
Persistent shared Codex environments with approved permissions versus throwaway sandboxes: what should live in a reusable environment for a 3-5 person team, and what should never be baked in — compare notes on whether the convenience outweighs the blast radius.