What version of the Codex App are you using (From “About Codex” dialog)?
26.924.20706
What subscription do you have?
Pro
What platform is your computer?
Linux 6.6.141-09476-g954adab60416 x86_64 unknown
What issue are you seeing?
After updating ChatGPT Desktop on Linux to 26.924.20706, all local Codex tasks remain indefinitely on “Starting your task”.
The standalone Codex CLI works correctly with the same account and repository.
Relevant desktop backend logs include:
thread_hydration outcome=failure reason=timeout ... wallDurationMs=120005
and repeated:
Worktree archive will be retried errorMessage="Git is unavailable"
However, Git is available and works normally in the same Linux environment:
which git
/usr/bin/git
git --version
git version 2.47.3
git status also works normally in the affected repository.
The desktop app-server itself starts successfully, authenticates successfully, and reports version 0.158.0-alpha.2.
The problem appears specific to the Linux ChatGPT Desktop / Codex integration rather than Git, the repository, account authentication, or standalone Codex CLI.
What steps can reproduce the bug?
-
Run ChatGPT Desktop 26.924.20706 on Debian 13 (trixie), x86_64, under ChromeOS Crostini.
-
Open Codex.
-
Start a brand-new Local task.
-
Submit a trivial read-only prompt, for example:
Read-only check. Report the current working directory. Make no changes.
-
The task remains indefinitely on “Starting your task”.
Troubleshooting already completed:
- Fully restarted ChatGPT Desktop.
- Tried multiple brand-new Codex threads.
- Reset ~/.config/Codex.
- Tested with a clean CODEX_HOME.
- Reauthenticated with ChatGPT.
- Tested on a completely different network using a phone hotspot.
- Confirmed standalone Codex CLI works correctly.
- Confirmed Git works correctly in the same Linux environment.
- Confirmed the affected repository is accessible and git status works normally.
The issue still reproduces after all of the above.
The regression appeared after updating from a previously working 26.908.x ChatGPT Desktop build to 26.924.20706.
What is the expected behavior?
A new Local Codex task should start within a few seconds, create or open the thread successfully, and begin processing the prompt.
The desktop app should detect the installed Git binary at /usr/bin/git and should not report “Git is unavailable” when Git works normally from the same Linux environment.
Additional information
Environment:
- ChatGPT Desktop: 26.924.20706
- Platform: Linux x86_64
- OS: Debian GNU/Linux 13 (trixie) under ChromeOS Crostini
- Standalone Codex CLI: 0.157.0
- Desktop bundled Codex app-server: 0.158.0-alpha.2
- Git: /usr/bin/git
- Git version: 2.47.3
- Userspace: Debian GNU/Linux 13 (trixie) under ChromeOS Crostini
Standalone Codex CLI continues to work correctly with the same account and repository.
The desktop backend successfully completes the Codex app-server initialization handshake and reports authenticatedAccountPresent=true.
A separate frontend/network symptom has also appeared in logs: some embedded ChatGPT requests receive a Cloudflare managed-challenge HTML response. However, reproducing the Codex task-start hang on both the normal network and a phone hotspot suggests the primary task-start issue is not specific to the local network.
I can provide the full sanitized backend log if useful.
What version of the Codex App are you using (From “About Codex” dialog)?
26.924.20706
What subscription do you have?
Pro
What platform is your computer?
Linux 6.6.141-09476-g954adab60416 x86_64 unknown
What issue are you seeing?
After updating ChatGPT Desktop on Linux to 26.924.20706, all local Codex tasks remain indefinitely on “Starting your task”.
The standalone Codex CLI works correctly with the same account and repository.
Relevant desktop backend logs include:
thread_hydration outcome=failure reason=timeout ... wallDurationMs=120005
and repeated:
Worktree archive will be retried errorMessage="Git is unavailable"
However, Git is available and works normally in the same Linux environment:
which git
/usr/bin/git
git --version
git version 2.47.3
git status also works normally in the affected repository.
The desktop app-server itself starts successfully, authenticates successfully, and reports version 0.158.0-alpha.2.
The problem appears specific to the Linux ChatGPT Desktop / Codex integration rather than Git, the repository, account authentication, or standalone Codex CLI.
What steps can reproduce the bug?
Run ChatGPT Desktop 26.924.20706 on Debian 13 (trixie), x86_64, under ChromeOS Crostini.
Open Codex.
Start a brand-new Local task.
Submit a trivial read-only prompt, for example:
Read-only check. Report the current working directory. Make no changes.
The task remains indefinitely on “Starting your task”.
Troubleshooting already completed:
The issue still reproduces after all of the above.
The regression appeared after updating from a previously working 26.908.x ChatGPT Desktop build to 26.924.20706.
What is the expected behavior?
A new Local Codex task should start within a few seconds, create or open the thread successfully, and begin processing the prompt.
The desktop app should detect the installed Git binary at /usr/bin/git and should not report “Git is unavailable” when Git works normally from the same Linux environment.
Additional information
Environment:
Standalone Codex CLI continues to work correctly with the same account and repository.
The desktop backend successfully completes the Codex app-server initialization handshake and reports authenticatedAccountPresent=true.
A separate frontend/network symptom has also appeared in logs: some embedded ChatGPT requests receive a Cloudflare managed-challenge HTML response. However, reproducing the Codex task-start hang on both the normal network and a phone hotspot suggests the primary task-start issue is not specific to the local network.
I can provide the full sanitized backend log if useful.