Codex Cloud tasks are being provisioned without a Git remote or GitHub authentication.

What version of the Codex App are you using (From “About Codex” dialog)?

Versione 26.818.21641

What subscription do you have?

Premium

What platform is your computer?

WIndows 11 home 64bit

What issue are you seeing?

When I start a Cloud task selecting DANTE_AI_SCOUT → master, Codex correctly accesses the repository, edits files, runs tests and creates local commits. However, the resulting worktree has no origin remote and gh auth status reports no authenticated GitHub host.

As a result, Codex cannot push the completed work or create pull requests.

The issue persists across new Cloud tasks after disconnecting/reconnecting GitHub and granting the Codex Connector access to all repositories.

PR creation previously worked normally with the same account and repository, so this appears to be a Codex Cloud GitHub provisioning/integration issue.

What steps can reproduce the bug?

1. Open Codex and create a new Cloud task.

1. Select the GitHub repository and branch in the Codex UI:

Cloud → DANTE_AI_SCOUT → master

1. Start the task. The Codex UI correctly shows DANTE_AI_SCOUT and master as the selected repository and base branch.

1. In the newly provisioned Cloud task, run:

git remote -v
git branch --show-current
git config --get remote.origin.url
gh auth status

1. Observe that:

• git remote -v returns no remotes.
• git config --get remote.origin.url returns no value.
• The internal branch is work.
• gh auth status reports that no GitHub host is authenticated.

1. Try to complete a normal Codex development task that creates a local commit and then create a pull request.

1. Codex successfully edits the repository, runs tests and creates the local commit, but cannot push the branch or create the PR because the Cloud worktree has no GitHub remote or authentication.

The issue is reproducible in completely new Cloud tasks.

I also:

• disconnected and reconnected the GitHub integration;
• reconfigured the ChatGPT Codex Connector on GitHub;
• changed its repository access to "All repositories";
• created a new Codex Cloud task after reconnecting.

The problem still occurs.

Previously, the same Codex/GitHub workflow on the same repository successfully created pull requests.

What is the expected behavior?

_No response_

Additional information

_No response_