Codex cannot attach to repo when default CI pipeline is failing

Resolved 💬 2 comments Opened Oct 30, 2025 by XoxRumbleLorexoX Closed Jan 17, 2026

What version of Codex is running?

0.50

What subscription do you have?

Plus

Which model were you using?

gpt5-codex-medium

What platform is your computer?

Darwin 25.1.0 x86_64 i386

What issue are you seeing?

Codex refuses to list this repository whenever the default GitHub Actions workflow is present and failing.
Even after reconnecting integrations, the environment picker returns:

Failed to load repositories

This persists until the CI pipeline either passes or the workflow file is removed.

<img width="791" height="135" alt="Image" src="https://github.com/user-attachments/assets/6233da63-a9b9-479e-970f-4cdd2693837b" />

What steps can reproduce the bug?

🧩 Steps to Reproduce

  1. Push the current workflow file to the repository:

.github/workflows/ci.yml

(The workflow runs automatically on the main branch.)

  1. Allow the workflow to fail — it currently breaks during the Install dependencies step.
  1. Open Codex → Environments → New, and select the XoxRumbleLorexoX organization.

---

What is the expected behavior?

_No response_

Additional information

✅ Expected Behavior

Codex should list the repository regardless of CI status, allowing environments to be created even when the pipeline fails.

---

💡 Additional Notes / Suspected Cause

It appears Codex may be filtering out repositories whose most recent workflow run has failed.

If this behavior is intentional, there should be a way to override it or at least display a warning rather than completely hiding the repo.

Otherwise, Codex should surface all repositories even with failing CI pipelines to avoid unnecessary blocking of environment creation.


---

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗