openai / openai/codex

Option–Space window stuck on “Waiting for worktree setup…”

Open
#40,253 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug session
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.818.41705 (6971)

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Darwin 25.6.0 arm64 arm

What issue are you seeing?

On macOS, pressing Option–Space opens the Codex hotkey window. After submitting a prompt, the task is created and completes successfully in the main ChatGPT/Codex window, but the hotkey window never transitions to the task. It remains on “New chat” with a disabled composer showing “Waiting for worktree setup…”.

This is not an actual worktree failure: it also reproduces in a projectless New chat, and the backend response is visible in the main app. Reinstalling the app, resetting the Codex Application Support/cache profile, restarting the app, and restarting macOS did not resolve it.

What steps can reproduce the bug?
  1. Launch ChatGPT/Codex desktop 26.818.41705 (6971) on macOS.
  2. Press Option–Space to open the Codex hotkey window.
  3. Choose New chat and submit a simple prompt such as do you work now.
  4. Observe that the popup stays on “Waiting for worktree setup…” and never displays the response.
  5. Open the main ChatGPT/Codex window and observe that the task and completed response are present.
    Example test thread ID: 01a02f4a-7793-7783-9f6d-197ae14880e9
What is the expected behavior?

The Option–Space window should transition from New chat to the created task, remain usable, and display the assistant response when the task completes.

Additional information

Fresh-run desktop logs at 2026-08-23T15:51:05.717Z contain Conversation state not found for the same conversation ID in both hotkeyWindowThread (visible=true) and hotkeyWindowHome. Immediately afterward, the main renderer reports maybe_resume_success with latestTurnStatus=completed and turnCount=1.

The local state_5.sqlite database passes PRAGMA quick_check and contains the affected thread

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue with the Option–Space hotkey window on macOS, then inspect the fresh-run logs around hotkeyWindowThread and hotkeyWindowHome, especially the “Conversation state not found” entries and the following maybe_resume_success event. Verify the affected thread in state_5.sqlite as needed. Done means the popup transitions to the created task and displays the completed assistant response in both projectless and project-based chats.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, rust
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.