Bug Report: Unable to Create New Conversations in Codex Desktop (thread/start Timeout)

What version of the Codex App are you using (From “About Codex” dialog)?

26.623.42026

What subscription do you have?

pro

What platform is your computer?

MacOS 26.5.1 (25F80)

What issue are you seeing?

Summary

Codex Desktop is unable to create any new conversations.

Existing conversations continue to work normally.

The issue reproduces across all projects, including newly created projects.

The same behavior is also partially reproducible in Codex Web, where newly created tasks remain stuck at “Running setup scripts”.

⸻

Environment

Operating System

• macOS 26.5.1

Codex Desktop

• Version 26.623.31921-26.623.42026
• Released Jun 26, 2026

Account

• Same account works normally in ChatGPT.
• Existing Codex conversations remain usable.

⸻

Reproduction Steps

1. Launch Codex Desktop.
2. Open any existing project or create a completely new project.
3. Click New Conversation.
4. Enter any prompt (for example: “Hello”).
5. Wait approximately 30 seconds.

⸻

Expected Result

A new conversation should be created immediately and become interactive.

⸻

Actual Result

Desktop reports:

• Error creating local task
• Timeout

No new conversation becomes available.

Existing conversations continue to function normally.

⸻

Additional Observation

In Codex Web:

• A new task can sometimes be created.
• However, it remains indefinitely at:

Running setup scripts…

Desktop may later synchronize a Summary generated by that task, but the task never becomes interactive and cannot accept follow-up prompts.

⸻

Relevant Log Entries

The following entries consistently appear during the failure:

mcp_request_timeout
method=thread/start
timeoutMs=30000
Failed to prewarm conversation
Error: Timeout
Error creating local task
Error: Timeout
response_routed
method=thread/start
durationMs=40232
No promise for request ID

Additional connection-related log:

Socket error
write EPIPE
AppServerConnection
disconnected
transport=stdio

⸻

Analysis

From the logs it appears that:

1. thread/start is successfully initiated.
2. The client waits 30 seconds and triggers a timeout.
3. The backend response arrives roughly 40 seconds later (durationMs=40232).
4. Since the frontend has already rejected the request, it logs:

No promise for request ID

This suggests a race condition or timeout handling issue during the thread/start lifecycle rather than a repository, prompt, or project-specific problem.

⸻

Notes

• The problem occurs across all projects.
• It also occurs in newly created projects.
• Restarting Codex Desktop does not resolve the issue.
• Rebooting macOS does not resolve the issue.
• Logging out and logging back in does not resolve the issue.
• ChatGPT continues to function normally.
• Existing Codex conversations remain usable.
• Only creating new conversations consistently fails.

What steps can reproduce the bug?

Feedback ID: 019f0830-18cb-7e93-9416-0982edff4ef1

What is the expected behavior?

_No response_

Additional information

The issue started on June 25, 2026. Before that, creating new Codex conversations worked normally. Existing conversations created before the issue continue to function.