Sites source repository credential returns 401 on git push
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
Unknown — “About Codex” is not available in my app.
What subscription do you have?
ChatGPT Plus
What platform is your computer?
No response
What issue are you seeing?
I cannot deploy an existing ChatGPT Site because Git authentication fails.
A newly issued Sites source repository write credential is accepted by the Sites integration, but git push immediately returns HTTP 401.
Environment:
- Codex desktop app on macOS
- ChatGPT workspace: ROOTS
- Sites plugin status: Connected
- Sites Building and Sites Hosting: Enabled
- Permission: Interactive, Write
I disconnected and reconnected Sites and restarted Codex, but the problem persists.
No credentials, tokens, repository write URLs, or secret values are included in this report.
What steps can reproduce the bug?
- Open an existing ChatGPT Sites project in Codex.
- Connect the Sites integration with Interactive and Write permissions.
- Save a new source version and obtain a newly issued repository write credential.
- Attempt to push the source repository.
- Git push immediately fails with HTTP 401.
- Disconnect and reconnect Sites, restart Codex, and try again.
- The same HTTP 401 error occurs.
Session ID is not available.
What is the expected behavior?
A newly issued Sites source repository write credential should authenticate successfully and allow the saved source version to be pushed and deployed.
Additional information
The BrandMate code and database changes are complete, but the production deployment is blocked by this authentication failure. The issue persists after reconnecting the Sites integration and restarting Codex.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by reproducing the Sites integration flow in the Codex desktop app, using the listed permissions and a newly issued repository write credential, then inspect where the immediate HTTP 401 is surfaced. Done means a saved source version can be pushed and deployed after reconnecting or restarting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, macos
- Domain
- authentication, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100