Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Codex Desktop on Windows 10 cannot send the first message in a newly created project (workspace_dependencies unsupported) [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#20163•Fetched 2026-04-30 06:32:57
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
likang1008-ctrllikang1008-ctrl
Participants
github-actions[bot]github-actions[bot]likang1008-ctrllikang1008-ctrl
Timeline (top)
labeled ×3commented ×1cross-referenced ×1

Error Message

Key error observed:

Code Example

[features]
workspace_dependencies = false
RAW_BUFFERClick to expand / collapse

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

Codex Desktop 26.422.62136

Windows Store package observed locally: OpenAI.Codex_26.422.8496.0_x64__2p2nqsd0c76g0

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Windows 10 Pro OS version observed locally: 10.0.19042

What issue are you seeing?

In the Codex Desktop app on Windows 10, I can create a new project and enter the project normally, but the first message in that new project cannot be sent successfully.

The composer accepts input, but after I try to send the first message, the project thread becomes stuck and does not proceed normally.

This appears to happen specifically in newly created projects / project-mode threads.

What steps can reproduce the bug?

  1. Open Codex Desktop on Windows 10.
  2. Create a new project.
  3. Enter the project.
  4. Type a message in the composer.
  5. Send the first message.

What is the expected behavior?

The first message in the new project should send normally and the conversation should begin.

Additional information

Actual behavior

The project thread gets stuck on the first send and does not proceed normally.

Relevant local log path:

C:\Users\Administrator\AppData\Local\Codex\Logs\2026\04\29\codex-desktop-5d9f196d-ec1b-4846-88ed-16d6e088090d-19680-t0-i1-074609-0.log

Key error observed:

Primary runtime install failed before first turn Codex Workspace dependencies are not supported on Windows 10.

Also observed in the same log session:

  • Received turn/started for unknown conversation
  • worker errors with ERR_INVALID_URL

Additional notes:

  • This does not look like a project path problem.
  • I also tried adding the following to C:\Users\Administrator\.codex\config.toml:
[features]
workspace_dependencies = false

but the issue still reproduced after restarting the app.

  • Based on local investigation, this looks like a Windows 10 compatibility issue in project-mode first-turn initialization, likely related to workspace_dependencies.

Potentially related issues:

  • #19437
  • #19811

extent analysis

TL;DR

Disabling workspace dependencies in the Codex configuration may not be sufficient to resolve the issue, and further investigation into Windows 10 compatibility is needed.

Guidance

  • Verify that the config.toml changes are being applied correctly by checking the Codex app's configuration loading logic.
  • Investigate the ERR_INVALID_URL worker errors to determine if they are related to the project-mode first-turn initialization issue.
  • Review the potentially related issues (#19437 and #19811) to see if they provide any insight into the Windows 10 compatibility problem.
  • Check the local log file for any other error messages that may indicate the root cause of the issue.

Example

No code snippet is provided as the issue is more related to configuration and compatibility.

Notes

The issue seems to be specific to Windows 10 and project-mode first-turn initialization, and the provided config.toml change does not resolve the issue. Further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Disable workspace dependencies and investigate Windows 10 compatibility issues, as the problem seems to be related to the interaction between Codex and the Windows 10 environment.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#integration issue#index setup#retrieval issue#search optimization#API routing

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Codex Desktop on Windows 10 cannot send the first message in a newly created project (workspace_dependencies unsupported) [1 comments, 2 participants]