OpenAI tagged rust-v0.135.0 of Codex on GitHub at commit 4daceea. The release page does not include a changelog in the provided source, so the update is mainly a version and commit reference for the Codex Rust branch.
OpenAI has tagged a new Codex release for its Rust branch: rust-v0.135.0. The release points to commit 4daceea869704f9f35e0a3949fc34711ef978a4e on GitHub, according to the release page.
The tag was published in the openai/codex repository on GitHub. The page lists the release under the project’s Releases section and links directly to the tagged tree and commit.
A tagged release is a named version of software that teams can pin, test, and compare. Here, Codex is OpenAI’s code-focused tool, and the Rust branch is one of its release lines. The news matters because version tags are how operators know when a build has changed, even if the release note does not spell out the differences.
If you use Codex-like agents in production, pin them to a specific tag instead of tracking a moving branch. Before upgrading to rust-v0.135.0, compare the tagged commit against your current version and run your usual regression prompts, tool-call tests, and permission checks. Keep a changelog in your own deployment notes, because the upstream release page here does not describe behavior changes.
No changelog text or feature summary is included in the source provided here. The release page mainly shows the version label, the associated commit hash, and GitHub’s tag comparison tools for moving between rust-v0.135.0 and earlier Codex tags.
That means the release announcement itself is thin. For readers tracking Codex builds, the useful detail is that the Rust line has advanced to rust-v0.135.0 and can be pinned or compared against earlier versions using the repository’s tag and compare views.
GitHub’s release page also exposes a long list of prior Codex tags, including rust-v0.134.0 and many earlier alpha and stable builds. That makes the repository useful for teams that need to inspect version history, compare behavior across releases, or keep an internal deployment on a specific tag.
The release references a single commit rather than a detailed note about model behavior, bug fixes, or security changes. In practice, that means anyone using this Codex branch will need to inspect the tagged commit itself or compare it against the previous release to see what changed.
For automation teams, the main operational signal is version control. If you run Codex-based tooling in a self-hosted or controlled environment, a tagged release like this is the point where you would decide whether to test, pin, or roll forward to the new Rust build.
The source does not say whether rust-v0.135.0 changes prompts, tool use, authentication, sandboxing, or output quality. It only confirms that a new tagged release exists in the openai/codex repository and identifies the exact commit attached to that tag.
