codex-0.147.0-patch.2

codex-0.147.0-patch.2

• Upstream: openai/codex@rust-v0.147.0 (be6e8eac029b183056b7e4402879f15d2c85f61b)
• Versioning: patch overlay release from patches/manifest.toml
• Binaries: codex, codex-responses-api-proxy, codex-code-mode-host

Why this release exists

Upstream 0.147.0 promoted features.code_mode_host to a stable, default-enabled
feature and removed the in-process code-mode runtime.
codex now resolves a sibling codex-code-mode-host next to its own executable,
and code mode fails closed when that binary is absent —
features.code_mode_host = false does not restore a fallback, it selects
DisabledCodeModeSessionProvider, which rejects every session.

codex-0.147.0-patch.1 predates release.yml building that binary, so its
package warns Code Mode is unavailable because failed to spawn code-mode host …
on startup.

Artifact provenance

These tarballs are assembled by hand rather than produced by a full CI run:

• bin/codex and bin/codex-responses-api-proxy are the CI-built binaries from
  codex-0.147.0-patch.1, unchanged.
• bin/codex-code-mode-host is upstream's own release binary from
  openai/codex@rust-v0.147.0.

That mix is safe for this release: no carried patch touches codex-rs/code-mode*,
codex-rs/code-mode-host, or codex-rs/install-context; the host binary does not
link codex-protocol; and both sides negotiate the same ClientHello/HostHello
ProtocolVersion::V1 handshake from the same upstream tag.

.github/workflows/release.yml now builds and packages codex-code-mode-host
itself, guarded by the release-binaries flake check, so the next CI release is
self-contained.

Enabled patches

• stream-reasoning-live
• tui-notification-sound
• webp-image-input
• token-usage-breakdown
• plan-mode-default
• timed-queue
• auto-thread-name
• tui-status-line-command

Each archive ships a SHA-256 sidecar naming the archive itself, so
shasum -a 256 -c <archive>.sha256 works from the download directory.