The Wire · Showcase
CODEX FIXES GITHUB RATE LIMIT BOTTLENECK IN INSTALLER
By RepoJournal · Filed · About OpenAI
The standalone installer now reuses GitHub metadata across four separate lookups, eliminating rate limit failures that were blocking valid releases.
Codex's installer was hammering GitHub's unauthenticated API four times per install: once for the latest release, once to find the platform package, once for the checksum manifest, and once for asset digests [1]. When the shared rate limit exhausted, legitimate installs failed silently because the shell installer suppressed metadata errors while probing for assets. The fix collapses these into a single metadata request, eliminating the whole class of 403 failures.
In parallel cleanup, the team removed lingering `git-cliff` configuration that outlived its usefulness by three years [2]. The TypeScript CLI tooling that relied on it vanished in #2048, the generated changelog got replaced with GitHub Releases in #2780, and the current Rust workflow builds release notes from commit messages. Nothing in the repo referenced it anymore.
On the feature side, Codex now exposes remote plugin versions alongside local ones [3], letting plugin marketplaces advertise versions independently of what's installed locally. The app-server schemas are already regenerated and ready. Separately, feedback attachments now get correct MIME types instead of always being labeled `text/plain` [4], preventing Sentry consumers from corrupting gzip archives during UTF-8 decoding.
Action items
- → Upgrade to the latest Codex installer build to eliminate rate limit install failures openai/codex [immediate]
- → Verify feedback attachment handling in your Sentry pipeline if you're using path-backed uploads openai/codex [plan]
- → Test remote plugin version display in your marketplace integration openai/codex [monitor]
References
- [1] fix(install): reuse GitHub release metadata ↗ openai/codex
- [2] chore: remove unused git-cliff configuration (#31066) openai/codex
- [3] [codex] expose remote plugin versions ↗ openai/codex
- [4] Fix MIME types for path-backed feedback attachments ↗ openai/codex
FAQ
- What changed in OpenAI on July 4, 2026?
- The standalone installer now reuses GitHub metadata across four separate lookups, eliminating rate limit failures that were blocking valid releases.
- What should OpenAI teams do about it?
- Upgrade to the latest Codex installer build to eliminate rate limit install failures • Verify feedback attachment handling in your Sentry pipeline if you're using path-backed uploads • Test remote plugin version display in your marketplace integration
- Which OpenAI repositories shipped on July 4, 2026?
- openai/codex