Codex App has been stuck on "Starting your service" since September 5
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What issue are you seeing?
Codex has been stuck on the "Starting your service" screen since September 5 and never finishes loading.
Whenever I try to start a new task, Codex remains on this screen indefinitely and the task never starts.
The issue has persisted for more than a day and is still occurring.
Error/diagnostic ID:
no-active-thread-01a076f1-2b40-7143-a2d1-b356dba63d7e
What steps can reproduce the bug?
- Open the Codex App.
- Try to start a new task.
- Codex displays "Starting your service".
- The service never finishes starting, and the task cannot be used.
I have already tried restarting the Codex App and refreshing/reopening ChatGPT, but the issue persists.
What is the expected behavior?
Codex should finish starting the service and allow me to create and run a task normally.
Additional information
- ChatGPT plan: Plus
- Codex App version: 26.831.21537
- Platform: Microsoft Windows NT 10.0.26200.0 x64
- Issue started: September 5, 2026
- Current status: Still occurring
- Symptom: Stuck indefinitely on "Starting your service"
- ChatGPT Classic: Working normally
- Codex Cli: Working normally
- I also have another macbook air m1
The issue appears to be specific to my Codex environment or service startup.
Please let me know if logs, screenshots, or additional diagnostic information would be helpful.
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 by reproducing the Codex App startup flow on Microsoft Windows using the listed steps, and use diagnostic ID no-active-thread-01a076f1-2b40-7143-a2d1-b356dba63d7e when investigating. The issue is done when a new task can pass the “Starting your service” screen and run normally; no source files or tests are named.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100