Updated 1 minute ago

Share this article

Related News

OpenAI refreshes Codex CLI for voice and agent oversight; the underlying features predate DevDay

Sep 29, 2026

OpenAI refreshes Codex CLI for voice and agent oversight; the underlying features predate DevDay

OpenAI's DevDay recap highlights voice steering and a new /agents view in Codex CLI. Its release history shows voice, subagents and worktrees arrived earlier, so the practical news is how those workflows are being brought together.

OpenAICodexCodex CLI

Codex Cloud adds reusable team environments; phone access was already here

Sep 29, 2026

Codex Cloud adds reusable team environments; phone access was already here

OpenAI's DevDay Codex update turns a tested repository setup into a published environment for separate cloud tasks. Teams need to check what that setup shares, and what still belongs to each task or user.

OpenAICodexCodex Cloud

OpenAI Ultrafast brings GPT-6 Astra to the API and Codex, with two different cost rules

Sep 29, 2026

OpenAI Ultrafast brings GPT-6 Astra to the API and Codex, with two different cost rules

The new speed tier is available for GPT-6 Astra, but API token prices and Codex usage multipliers are different decisions. OpenAI’s published maximum-speed figures also have different bases.

OpenAIGPT-6 AstraUltrafast

Codex Code Review puts pull requests in the desktop app; automatic reviews still need setup — Source: OpenAI. Figure: OpenTools Team. Code Review workflow and publication boundaries.Source image

OpenAI DevDay

Codex Code Review puts pull requests in the desktop app; automatic reviews still need setup

By OpenTools Team

OpenAI's DevDay Code Review update brings summaries, diffs and review questions into the ChatGPT desktop app. GitHub review is generally available, GitLab support is in preview, and cloud first passes depend on repository connections and settings.

The new desk is for reading a change before sending feedback

OpenAI's September 29 DevDay recap introduces a Code Review experience in the ChatGPT desktop app for changes across projects. A reviewer can read a summary, inspect a diff and ask Codex about a possible issue before sharing feedback on a GitHub pull request or GitLab merge request. That matters most when the review problem is understanding the change and its context, rather than merely generating a comment: the current Code Review guide places the PR description, changed files, comments and checks together, with Summary and Changes views for inspection.

The guide also describes a personal inbox for GitHub PRs assigned to the reviewer or their team, a marker for files viewed at the displayed revision, and a Stack view for related dependent PRs. Those are workflow affordances, not evidence that Codex found a bug or approved the patch. OpenAI says the DevDay experience is available on all plans, while the guide calls GitHub code review generally available and GitLab merge‑request support a preview. A team should not treat the two providers' support and setup as identical.

A cloud first pass is separate from an in‑app conversation

The DevDay recap says Codex can take an automatic first pass in the cloud while the developer is away. The Code Review guide narrows that promise: GitHub automatic reviews need the Codex connector, repository permission and an enabled review policy. The GitHub integration instructions distinguish an @codex review request in a PR comment from automatic reviews configured in settings. A cloud first pass can run while the reviewer is away from the desktop app. The GitLab route has separate environment and webhook requirements, so GitHub setup advice should not be copied over wholesale.

There is a consequential publishing boundary. Asking Codex questions in a PR chat or running a review there does not itself post comments, approve a PR or merge it. The guide says a draft comment remains private until it is shared, but posting in the review surface's Summary or Changes sends that comment to the source provider immediately; Submit review sends the selected Comment, Approve or Request changes decision. Automatic cloud comments can appear on GitHub and in Code Review. Reviewers should inspect each finding against the latest diff and tests rather than mistake an AI first pass for a completed human decision.

GitLab is a real route, with a different maturity and permission path

OpenAI includes GitLab merge requests in the launch, but its GitLab review guide labels the integration beta. It supports @codex review and policy‑driven automatic reviews after a GitLab connection and the required activity path are configured. GitLab.com needs a project environment for reviews; self‑managed and Dedicated instances have additional workspace‑admin connection, service‑account and webhook options. The guide also says GitHub‑style desktop repository controls such as Create pull request are not part of the GitLab beta. Those caveats belong beside a headline about cross‑provider review.

The most useful rollout question is therefore which job the team wants Codex to do. The desktop surface helps a person inspect and discuss a change; a configured cloud policy can add an initial review to selected PRs or MRs; and the reviewer remains responsible for checking findings and deciding what to share. The Codex tool record covers the durable product and points to the OpenAI organization. This is a dated Code Review feature update to that product, not a new model, a benchmark result or a second Codex listing.

Sources

1.openai.com (openai.com)
2.learn.chatgpt.com (learn.chatgpt.com)
3.learn.chatgpt.com (learn.chatgpt.com)
4.learn.chatgpt.com (learn.chatgpt.com)

Tags

OpenAICodexCode ReviewDevDay 2026Developer tools