Codex Build

Custom Apple Silicon macOS distribution of OpenAI Codex, maintained as a thin patch layer rather than a source fork.

Status

The repository builds the latest stable upstream Codex release for Apple Silicon macOS with a small, drift-detecting patch set:

• the existing mention search excludes hidden paths while continuing to honor Codex's normal ignore-file behavior; both mention v1 and v2 share this path;
• the native update prompt remains enabled, but release checks and accepted updates stay on celados/codex-build;
• the Computer Use MCP server is skipped because custom-signature startup has not been proven compatible. Other plugin MCP servers remain enabled.

Install or update the latest release with:

curl -fsSL https://raw.githubusercontent.com/celados/codex-build/main/install.sh | sh

The installer checks the target binary's version before downloading an artifact. Re-running it at the latest version is a no-op. Downloaded artifacts use a temporary directory that is removed on exit; the installer does not keep a version cache to prune.

Binary pairing

Releases ship codex and codex-code-mode-host in a single archive, and the installer writes both. Codex resolves the host from its own directory and the two exchange an IPC schema that upstream extends without bumping the protocol version, so a host from a different upstream tag fails every tool call before it reaches a shell. The CLI embeds no V8, so there is no in-process fallback to absorb the mismatch. The installer records the pair's version in .codex-code-mode-host.version beside the binaries, replaces a host it cannot account for, and installs the host before codex so an interrupted run never leaves a new codex next to an old host.

Build policy

macOS artifacts are checked daily and built only when the latest stable upstream tag changes. They are built and smoke-tested on the Celados Apple Silicon Mac mini runners. Linux may perform source and patch checks, but is not a supported macOS cross-compilation environment. A manual workflow dispatch can force a rebuild of an already released upstream tag.

Downstream changes belong in patches/. The upstream checkout and Cargo output will live in the ignored sources/ directory so persistent runners can reuse incremental build state without committing upstream code.

The code-mode host links V8. The v8 crate's default prebuilts ship no sandbox-enabled aarch64-apple-darwin archive, so scripts/fetch-v8.py points Cargo at the pair Codex publishes on its own rusty-v8-v<crate_version> tag, verifies the checksums, and caches them in the ignored .v8-cache directory. Building V8 from source is not part of this pipeline; if upstream renames those assets the download 404s and the build fails loudly.

build.sh --check --upstream-ref <tag> validates every structural seam without rewriting source. A full build temporarily applies the patches, embeds a custom SemVer, signs the binary ad hoc, runs the hidden-path regression check, and restores the upstream checkout on exit.

Grok Build remains an independent release repository at celados/grok-build. Keeping the two repositories separate prevents their repository-wide GitHub latest releases from corrupting each other's updater channel.