[ChatGPT Work] Cloud Work Git remote returns HTTP 401 because no non-interactive credentials are provisioned

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

N/A — ChatGPT Work (Cloud Work) via ChatGPT Web and Windows Desktop

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Windows 11 x64 — Microsoft Windows NT 10.0.26200.0

What issue are you seeing?

ChatGPT Work Cloud Work can no longer authenticate to its platform-managed Git remote at git.chatgpt-team.site.

Local Git operations are normal. The repository is healthy, the working tree is clean, and the local commit history is intact. However, all remote Git operations fail because the Cloud Work environment appears to have no non-interactive Git credentials available.

Example error:

fatal: could not read Username for 'https://git.chatgpt-team.site': No such device or address

Credential diagnostics show:

• GIT_ASKPASS: not set
• SSH_ASKPASS: not set
• credential.helper: not configured
• ~/.netrc: absent
• ~/.git-credentials: absent
• no Git http.* authentication configuration

GIT_CURL_VERBOSE=1 git ls-remote origin shows that network connectivity is working:

• Proxy CONNECT succeeds with HTTP/1.1 200 OK
• TLSv1.3 succeeds
• HTTP/2 succeeds
• git.chatgpt-team.site is reached successfully

The Git service then responds:

HTTP/2 401
www-authenticate: Basic realm="artifacts"

Request identifiers:

cf-ray: a3d7b9aefcb76b54-DFW
date: Sat, 19 Sep 2026 09:57:17 GMT

Git then fails because the Cloud Work environment has no username/password credential available.

The repository remote is managed by ChatGPT Work. I did not manually configure a PAT, SSH key, username/password, credential helper, .netrc, or modify the remote URL.

What steps can reproduce the bug?

Feedback ID: no-active-thread-01a0b936-5bae-7e03-bfa1-4079ce389bc7

What is the expected behavior?

ChatGPT Work should automatically provision the non-interactive credentials required to access its platform-managed git.chatgpt-team.site remote.

git fetch, git push, and Site deployment should work without asking the user to manually configure a PAT, SSH key, username/password, credential helper, .netrc, or other authentication mechanism.

Additional information

Troubleshooting already attempted without success:

• Rebuilt the Cloud Work execution environment
• Reset Cloud Work cache
• Opened the same repository in another Work session
• Logged out and back into ChatGPT Web
• Logged out and back into ChatGPT Windows Desktop
• Retried Git authentication after both login refreshes

The local repository remains healthy:

• working tree is clean
• local Git history is intact
• local branch is ahead of origin/main by one commit
• local Git operations work normally

The issue only occurs when accessing the platform-managed remote.

GIT_CURL_VERBOSE confirmed:

• proxy connection succeeds
• TLS connection succeeds
• git.chatgpt-team.site is reachable
• server responds HTTP/2 401
• www-authenticate: Basic realm="artifacts"

Request identifiers:
cf-ray: a3d7b9aefcb76b54-DFW
date: Sat, 19 Sep 2026 09:57:17 GMT

No manual PAT, SSH key, credential helper, .netrc, .git-credentials, or remote URL changes have been made.

No repository file or test is named. Start by tracing how Cloud Work provisions credentials for the platform-managed Git remote and reproduce the failure with the documented credential diagnostics and git ls-remote command; done means non-interactive fetch, push, and Site deployment work without manual credentials.