Skip to content

codex: use package release asset#268453

Open
sluongng wants to merge 1 commit into
Homebrew:mainfrom
sluongng:sluongng/codex-package-asset
Open

codex: use package release asset#268453
sluongng wants to merge 1 commit into
Homebrew:mainfrom
sluongng:sluongng/codex-package-asset

Conversation

@sluongng

@sluongng sluongng commented Jun 8, 2026

Copy link
Copy Markdown

Switch the Codex cask from the bare codex-#{arch}-#{os}.tar.gz
release asset to codex-package-#{arch}-#{os}.tar.gz.

The bare asset only contains the Codex binary. Codex also publishes a
package asset containing the package layout used by the CLI to discover
bundled resources:

  • bin/codex
  • codex-package.json
  • codex-path/rg
  • codex-resources/zsh/bin/zsh

Without that layout, enabling Codex's forked-zsh shell backend can fail
at startup because no packaged zsh fork is available for the install.
The package asset keeps those resources private under the Caskroom while
only linking bin/codex as the public executable.

I tested the package asset locally through a temporary cask tap and
codex doctor recognized the install as a brew package layout with
resources.

This fixes Codex startup failures when users enable the forked-zsh
shell backend from the Homebrew cask.

The current cask installs the bare codex-#{arch}-#{os}.tar.gz asset,
which only contains the Codex binary. Codex 0.137.0 also publishes a
codex-package-#{arch}-#{os}.tar.gz asset containing the package layout
that the CLI expects for bundled resources: bin/codex,
codex-package.json, codex-path/rg, and codex-resources/zsh/bin/zsh.

Use that package asset and link bin/codex as the public executable.
Keep the bundled zsh and rg private inside the package root so Codex can
discover them through its install context without exposing extra PATH
entries or replacing Homebrew's ripgrep dependency.
@sluongng

sluongng commented Jun 8, 2026

Copy link
Copy Markdown
Author

I don't think CI failures are related to my change here 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants