Startups·29 September 2026·1 min readTechnical readSource-backed

OpenAI Updates Codex With Reusable Cloud Development Environments and New CLI Voice Capabilities

OpenAI announced updates for its Codex software engineering agent during Dev Day on Tuesday.

WIREUNWIRED BRIEF

OpenAI announced updates for its Codex software engineering agent during Dev Day on Tuesday. The primary addition is reusable, persistent, and configurable cloud development environments accessible from any device, allowing teams to share a workspace with approved settings and permissions while helping tasks start more quickly. Additionally, the refreshed Codex CLI supports voice-directed tasks, a new /agents view for tracking multiple tasks, improved prompt editing, session resumption, worktrees, and a cleaner terminal user interface.

Codex integration with the ChatGPT desktop app now provides a new code review experience for GitHub pull requests and GitLab merge requests, including automatic reviews. For security, OpenAI introduced Codex Security Cloud to scan entire GitHub repositories on demand, on a regular schedule, or upon new commits, which investigates findings, removes duplicates, and prepares fixes in the cloud while incorporating models from OpenAI’s Daybreak Blue cybersecurity initiative.

Furthermore, OpenAI revealed API updates featuring a new Decisions API utilizing Luna for real-time decision-making and an updated Agents API supporting computer use and Amazon’s Bedrock Managed Agents for building AWS-based OpenAI agents.

WHAT WIREUNWIRED ADDS

Plain-language context

WireUnWired turns the supplied report into a clearer brief, preserves the original publisher and author details, and adds relevant context without hiding where the information came from.

Useful next steps

Relevant WireUnWired coverage is connected so one story can lead into the larger technology context.

A WireUnwired summary is already available. You can still write your own brief below for the reader community.

Think you can explain this story clearly?Sign in to write a brief →

SOURCE & ATTRIBUTION

TechCrunch

Original author: Sarah Perez

Original publication: 29 September 2026 22:45

Read full story on TechCrunch ↗

RELATED STORIES

ABOUT THE AUTHOR

WireUnwired Editorial TeamView all stories →

READ FASTER

Use the prepared WireUnwired prompt with your own AI account.

Show prepared prompt

You are the senior WireUnwired technology editor.

Write a source-grounded news brief of about 175 words (acceptable range: 140-200). Your job is to make the reader understand more than they would from a headline or raw feed item. Do not merely paraphrase every sentence in order.

EVIDENCE RULES
Use the supplied source packet as the factual basis. Do not invent facts, numbers, quotes, motives, causation, technical details, or future outcomes. Clearly attribute claims, allegations, forecasts, and company statements. If a detail is missing or disputed, say so or leave it out. Never describe repeated claims as independently verified solely because they appear in multiple places.

EDITORIAL THINKING — DO THIS SILENTLY
Identify the central development, the strongest supported facts, what is genuinely new, who or what is affected, the practical/technical significance, useful context, and any material uncertainty. Only include context supported by the supplied source packet or explicitly provided WireUnwired context.

ARTICLE STRUCTURE
Write 3–4 short paragraphs. Use 4 when the source supports enough useful information; use 3 for genuinely brief stories. Do not force a fourth paragraph merely to hit a word count.
Paragraph 1: state exactly what happened, who is involved, and the most important confirmed detail.
Paragraph 2: add specific evidence and details—numbers, dates, product names, technical changes, research methods, or results where present.
Paragraph 3: explain why it matters in practical terms and define any essential technical concept in plain language.
Paragraph 4, when justified: explain what changed, what remains unknown, or what concrete next step to watch. If no further development is reported, do not invent one.

WRITING STYLE
Use simple, natural English for an intelligent non-specialist. Prefer active voice, concrete verbs, and varied sentence lengths. Keep most sentences below 22 words. Explain necessary technical terms at first use. Avoid jargon chains, academic phrasing, corporate filler, dramatic adjectives, clichés, vague claims of a “major shift,” and repeated facts. Do not repeat the headline in the opening sentence. Do not pad copy just to hit the target length; every paragraph must add a new fact, context, or explanation.

OUTPUT CONTRACT
Return only clean prose paragraphs. No title, heading, bullets, JSON, markdown fences, field labels, source list, self-reference, or explanation of your process. If the supplied material is too thin to support the requested brief, give the most useful concise account the evidence supports rather than inventing details.

STORY TITLE:
OpenAI Updates Codex With Reusable Cloud Development Environments and New CLI Voice Capabilities
SOURCE:
TechCrunch
ORIGINAL URL:
https://techcrunch.com/2026/09/29/openai-gives-codex-reusable-cloud-environments-that-work-across-devices/

SOURCE EXCERPT:
OpenAI is expanding Codex with reusable cloud development environments, a revamped CLI with voice controls, new code review tools and a security-focused product for scanning repositories and preparing fixes.

Last updated 29 September 2026 22:55

Original sourceTechCrunch ↗