Repository navigation
🐛 - fixagents official Codex installer endpoint returns HTTP 404 and blocks fresh reviews #680
Description
Is there an existing issue for this?
- I have searched the existing issues.
Which actions are affected?
Issue, Pull Request, Commits
Which platforms are affected?
Linux, macOS
Description
The official standalone installer endpoint configured by Copilot 3.10.2 currently returns HTTP 404. This blocks a fresh private Codex installation before the requested capability starts. It is a real infrastructure dependency failure, not a code finding, and it blocks the current consumer reconciliation review.
The official documentation still advertises the same endpoint: https://learn.chatgpt.com/docs/codex/cli . The failure was observed on ubuntu-runner-2 in GeckoCV and reproduced read-only from the maintainer machine and a separate web fetch. This evidence establishes current unavailability; it does not establish permanent retirement of the endpoint.
A correction must retain the private installation root, credential-free installer environment, bounded HTTPS downloads and executable ownership validation. Investigate a bounded fallback to a reviewed immutable copy of the same official installer in openai/codex; do not use an untrusted mirror, inject the runner's credentials, or bypass native review. No new public configuration should be required.
Reproducing the issue
- Run a fresh Copilot native review using provider codex and the 3.10.2 runtime manifest.
- Observe GeckoCV ✨ - Auto Close Issues #21, head 34c3077f55364b97755dfd5fc730e0bce0583d0b: https://github.com/vypdev/geckocv/actions/runs/40031573641/job/120680835466 .
- Independently request https://chatgpt.com/codex/install.sh over HTTPS with a 30-second bound and no credentials; it returns HTTP 404 as of 2026-10-23 22:15 UTC.
- Confirm that no current-head native review evidence can be produced; the PR must remain unmerged until a complete review succeeds.
Expected: obtain the official reviewed installer through a bounded trusted route and perform the native review; if no trusted source is available, fail closed with an actionable network diagnostic.
Validation must cover unavailable primary endpoint plus valid official fallback, rejection of untrusted/oversized/invalid fallback data, exhaustion of trusted sources, and continued credential isolation. Verify an actual fresh installation and rerun the blocked current-head review after the cause is fixed.
copilot Version
3.10.2
Relevant Log Output
Agent runtime codex provisioning failed (official-download-exit-22).
The codex runtime is unavailable or its official installation failed.
Error code: configuration.unsupported
Additional context and comments
Found while performing the authorized runner alignment and consumer health audit. GeckoCV #22 is already merged with all applicable checks successful and complete zero-finding review; this failure occurred on the subsequent master-to-develop reconciliation #21. No tags, releases, deployment dispatches or runtime trust exceptions are authorized by this bug report.
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Activity
[-]fix(agents): official Codex installer endpoint returns HTTP 404 and blocks fresh reviews[/-][+]🐛 - fixagents official Codex installer endpoint returns HTTP 404 and blocks fresh reviews[/+]efraespada commentedon Oct 24, 2026
El mantenedor ha autorizado expresamente recuperar #680 mediante la rama manual
bugfix/680-codex-installer-recovery, creada desde eldeveloprevisadod1ad9f126d71a4e869632d20de27c944efcf6bc1.La creación automática falló antes de crear la rama: run 40033060064,
official-download-exit-22. Se conserva el árbol de trabajo principal y la corrección se prepara en un checkout aislado.Reconciliación: publicar commits normales en esa única rama, enlazar la PR a esta issue y mergear en
developúnicamente tras todos los checks aplicables correctos, revisión completa del head vigente y cero findings pendientes. La recuperación no cambia las ramas protegidas directamente, no fuerza historial y no publica versiones ni mueve tags. La publicación de otra versión requerirá autorización aparte.vypbot commentedon Oct 24, 2026
Issue closed — historical progress
Current status: closed as completed.
The last estimate is retained below as history. Closure does not certify a new percentage, tests, or branch alignment.
Action required: none for this closed issue. If work continues, reopen the issue; a fresh assessment can update this same card.
Last assessment before closure (historical)