[Windows] New Codex chats cannot send messages — workspace settings fail with cloudflare_challenge #53384

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

26.1007.2314.0

What subscription do you have?

ChatGPT Pro

What platform is your computer?

Windows 11 (build 22631)*64

What issue are you seeing?

Problem Description

For several days, I have been experiencing a persistent issue with the Codex Windows desktop application.

The main issue is that newly created Codex conversations cannot send messages, while existing conversations continue to work normally.

Specifically:

1. I can create a new Codex conversation and enter text.
2. The Send button remains greyed out and cannot be clicked.
3. The application repeatedly displays "Couldn't load workspace settings."
4. Switching models briefly enables the Send button, but it becomes disabled again before a message can be sent.
5. Existing Codex conversations can still send messages and execute tasks normally.
6. ChatGPT works normally in Chrome.

Technical Evidence

The Windows Codex desktop application logs contain the following error:

2026-10-12T04:45:51.704Z
sa_server_request_failed
errorCode=cloudflare_challenge
errorMessage=cloudflare_challenge
attachAuth=true
attachIntegrityState=true
method=get

This confirms that at least one desktop application request encountered a Cloudflare security challenge.

Troubleshooting Already Performed

I have attempted all of the following without success:

• Changed proxy applications.
• Tested different proxy nodes and routes.
• Tested both system proxy mode and TUN virtual network adapter mode in Clash Verge.
• Signed out of my ChatGPT account and signed back in.
• Restarted the Codex application.
• Used Windows application Repair.
• Verified the application version: 26.1007.2314.0.
• Inspected the local config.toml file without finding a confirmed root cause.
• Switched models, which only briefly enabled the Send button.

I also attempted to submit feedback using /feedback from an existing working conversation. The command was recognized, but feedback submission failed, so no feedback session ID could be obtained.

After reproducing the issue in a new conversation, I checked the local transcript directory:

%USERPROFILE%\.codex\sessions

No new JSONL transcript was observed for that failed attempt.

Expected Behavior

A new Codex conversation should initialize successfully, load workspace settings, and allow messages to be sent.

Actual Behavior

The new conversation opens, but the Send button remains disabled and no message can be submitted.

Request for Investigation

Could the Codex desktop engineering team investigate:

1. Why workspace settings or authentication-related requests encounter cloudflare_challenge.
2. Whether this is related to a known Windows Codex desktop issue.
3. Why existing conversations work while new conversations cannot initialize correctly.
4. Whether there is a supported fix that preserves existing conversations, projects, and configuration.

I can provide additional redacted desktop logs through a secure support channel if required.

Thank you.

What steps can reproduce the bug?

Steps to Reproduce

1. Launch Codex Desktop on Windows 11 (version 26.1007.2314.0).
2. Sign in with a ChatGPT Pro account.
3. Open an existing Codex conversation and verify that messages can be sent normally.
4. Create a new Codex conversation in the same application.
5. Type a simple message such as test into the composer.
6. Observe that the Send button remains greyed out and cannot be clicked.
7. Change the selected model. The Send button may become enabled briefly, but it becomes disabled again before the message can be submitted.
8. The application also repeatedly reports "Couldn't load workspace settings."

Additional Diagnostic Information

The desktop logs contain:

2026-10-12T04:45:51.704Z

sa_server_request_failed

errorCode=cloudflare_challenge

The issue persists after switching proxy applications and routes, testing both system proxy and TUN modes, signing out and back in, and using Windows application Repair.

The /feedback command is recognized but fails to submit, so no feedback session ID is available.

No new session transcript was observed after the latest failed new-conversation test.

This issue has persisted for several days and is reproducible in new conversations. Existing conversations continue to function normally.

What is the expected behavior?

When a new Codex conversation is created, the application should successfully initialize the conversation and load the required workspace settings.

After entering a message, the Send button should become enabled, allowing the user to submit the message and receive a response.

New conversations should work as reliably as existing conversations, without requiring model switching, application restarts, or repeated authentication.

Additional information

No response