›_ Codex Issues
Codex Issues / #40086

Codex Cloud creates detached work checkout with no Git remote

Open 💬 2 comments Opened Aug 22, 2026 by elcartero07205-bit
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

Summary

Codex Cloud tasks are not receiving the requested Git checkout or remote even though the GitHub app has access to the repository and the branch is selected in the UI.

Reproduction

  • Repository: elcartero07205-bit/ultron (private)
  • Selected branch: codex/ar2c-os-isolated-bridge
  • Reproduces in both an existing environment and a newly created environment.
  • The fresh environment successfully installs all Python 3.12 dependencies from requirements.txt; this is not a package setup failure.

Expected

A cloud task should check out the selected branch and configure a usable origin remote.

Actual

Each task opens on local branch work at 8f0eaf7a08efae7f0aa8863c5d4a976cd72113bf. git remote -v returns no entries, only refs/heads/work exists, and the requested PR branch is absent. The task therefore cannot fetch, commit to, or push the PR branch.

Evidence

Fresh-environment read-only verification task: task_e_6a896a99be288325a85a331e1c32e7d3

It confirmed Python 3.12.13; all declared dependencies installed; offline pip install --dry-run --no-index -r requirements.txt succeeded; AR2C test modules collected successfully (21 + 90 tests). The only remaining failure is the missing Git remote and branch provision.

No credentials, secrets, or application data were used.

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 6 days ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #39778

Powered by Codex Action

tlmader · 4 days ago

I observed the same checkout shape in a separate Codex Cloud task:

  • the task opened on local branch work;
  • git remote -v returned no entries;
  • the expected base branch was absent from both local and remote-tracking refs; and
  • repository verification that depended on comparing against that base could not proceed.

This matches the observable failure reported here.

A potentially separate handoff problem occurred in the same cloud image: a bundled MCP helper failed during startup with ModuleNotFoundError: No module named 'mcp' while importing mcp.server.fastmcp. That may be independent, but I am noting it in case tool/image provisioning and the detached checkout are correlated.