Why is the Homebrew cask update delayed after a new Codex release?

[dncks1525]

Question

The latest Codex release on GitHub is 1.3.1, but the Homebrew cask still appears to be on 1.3.0.

I understand that users can download the latest version directly from GitHub, but since Homebrew is a supported installation method, it would be helpful if the cask were updated promptly after each release.

Answer requested

Could you clarify:

1. Whether the Homebrew cask is updated automatically as part of the Codex release process.
2. If not, who owns updating the cask.
3. Whether users should wait for the Homebrew cask update or use the GitHub release directly in the meantime.
4. Whether there is an expected delay between a GitHub release and Homebrew availability.

Thanks.

[vekovius]

I think there are two slightly different package lines worth separating here:

• codex Homebrew cask: currently points at the CLI release tarballs from openai/codex
• codex-app Homebrew cask: points at the desktop app build feed and uses a separate 26.x style version

For the CLI cask, Homebrew currently has codex at 0.130.0, while the latest stable GitHub release is rust-v0.131.0. The cask has a livecheck block using GitHub latest releases:

livecheck do
  url :url
  regex(/^rust-v?(\d+(?:\.\d+)+)$/i)
  strategy :github_latest
end

So Homebrew can detect that a newer release exists, but the cask file still has to be bumped in Homebrew/homebrew-cask. In practice that means there can be a delay between the GitHub release and brew install --cask codex picking it up.

The previous codex 0.130.0 cask bump landed on May 9, and rust-v0.131.0 was published on May 18, so this looks like normal cask lag rather than a separate Codex install issue.

If you need the newest CLI immediately, I’d use the GitHub release directly. If you want the normal Homebrew-managed install, I’d wait for the cask bump.

[dncks1525]

Thanks for clarifying