Git features silently disappear when Xcode license acceptance blocks git
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)?
26.908.70816
What subscription do you have?
Pro 20x
What platform is your computer?
Darwin 27.0.0 arm64 arm
What issue are you seeing?
After an Xcode upgrade, many or most Git-related features in the Codex/ChatGPT desktop app were missing with no explanation. For example:
- I could not choose a branch or worktree to work from.
- The Pinned summary was nearly empty.
The app did not display an error explaining that Git was unavailable. I only discovered the underlying problem by running git status in a terminal, which displayed:
% git status
You have not agreed to the Xcode and Apple SDKs license. You must agree to the license below in order to use Xcode.
Press enter to display the license:
...
This left the app looking as though Git features were missing, with no indication of the cause or how to recover.
What steps can reproduce the bug?
- Upgrade Xcode to a version that requires accepting a new Xcode and Apple SDKs license, leaving the license unaccepted.
- Open a Git repository in the Codex/ChatGPT desktop app while the system
gitcommand is blocked by that license requirement. - Attempt to choose a branch or worktree, and inspect the Pinned summary.
- Observe that Git-related features are missing or nearly empty, with no explanation in the app.
- Run
git statusin a terminal to see the Xcode license prompt.
These steps describe the circumstances in which I encountered the issue; I have since accepted the license and have not recreated the unaccepted-license state.
What is the expected behavior?
The app should detect when the git command cannot run and display a clear, actionable error explaining why Git-dependent features are unavailable.
For this case, it should surface the Xcode license error and ideally explain that the user can run sudo xcodebuild -license in a terminal to review and, if they agree, accept the license.
A visible error should distinguish a Git/toolchain failure from a repository with no branches, worktrees, or other Git information to display.
Additional information
Workaround
I ran:
sudo xcodebuild -license
I then typed agree and pressed Enter. After accepting the license, the git command started working as expected.
The apparent trigger was an Xcode upgrade requiring acceptance of a new EULA before CLI tools, including Git, could be used.
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
Start at the Git integration entry points that load branches, worktrees, and the Pinned summary, then reproduce the failure with git status blocked by the Xcode license. Trace how that command failure is handled and make sure the app distinguishes it from an empty repository state. Done means the interface shows a clear, actionable license or Git availability error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, macos, rust
- Domain
- desktop, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100