What version of the Codex App are you using?
Current Windows app version: 26.1007.2314.0.
The issue first occurred on 26.1002.7124.0 and recurred after upgrading.
What platform is your computer?
Windows 11.
What issue are you seeing?
The ChatGPT/Codex Windows desktop application intermittently fails to load workspace settings. It first occurred on October 10, 2026, and recurred after restarting Windows on October 11.
During the failure, the normal ChatGPT interface with the Chat and Work sections is unavailable. The application switcher shows “ChatGPT Work” and “Codex,” and the main view displays a workspace settings error.
ChatGPT Work remains functional in a web browser using the same account while the desktop application is affected.
The following errors were observed at different stages, not necessarily simultaneously:
Local Work executor registration failed (HTTP 403)无法检查锁定模式 — approximately “Unable to check Lockdown Mode”无法加载工作空间设置 — approximately “Unable to load workspace settings”请重试以继续聊天 — approximately “Please retry to continue chatting”
The HTTP 403 banner was observed during the initial occurrence. It was not independently confirmed during the recurrence after reboot.
Clicking Retry, switching proxy modes, and signing out and back in do not consistently restore functionality immediately. The application eventually recovered without further configuration changes, but the recovery delay was not measured.
What steps can reproduce the bug?
The issue is intermittent; a reliable reproducer has not yet been established. The observed sequence was:
- Use the Windows desktop application normally.
- Restart Windows.
- Launch Clash Verge Rev and the desktop application.
- Attempt to access ChatGPT Work.
- Observe that the normal ChatGPT interface is unavailable and workspace settings fail to load. The Lockdown Mode check may also fail.
- Compare with ChatGPT Work in a browser using the same account, which continues to work.
- Try Retry, switching proxy modes, or signing out and back in. These may not restore access immediately.
- After an unmeasured delay, the desktop application may recover.
Rebooting preceded the recurrence, but the exact trigger and the role of startup order have not been established.
What is the expected behavior?
The desktop application should reliably load workspace settings and make ChatGPT Chat and Work available after Windows startup.
If initialization fails temporarily, Retry should provide a supported recovery path, or the application should display an actionable error explaining why initialization cannot complete.
Additional information
Environment
- UI language: Chinese
- Proxy software: Clash Verge Rev
- Proxy modes tested: Rule and Global
- TUN mode: not tested
Troubleshooting timeline
- October 10 — version
26.1002.7124.0: Switching Clash from Rule to Global mode restored functionality. After adding high-priority proxy rules for chatgpt.com, openai.com, oaistatic.com, oaiusercontent.com, and oaistatsig.com, Rule mode also worked.
- October 10 — update: Upgraded to
26.1007.2314.0; the application worked afterward.
- October 11 — after Windows reboot: Workspace initialization and Lockdown Mode errors returned. Global mode and signing out/back in did not immediately resolve the issue.
- Later on October 11: The application recovered without further configuration changes. Both Global and Rule modes then worked.
No application reset, cache deletion, or reinstallation was performed.
Initial connectivity checks
PowerShell Test-NetConnection checks on TCP port 443 returned:
| Domain |
TCP 443 result |
chatgpt.com |
False |
auth.openai.com |
True |
desktop.chat.openai.com |
False |
challenges.cloudflare.com |
True |
These direct TCP checks do not establish whether requests through the configured HTTP proxy succeeded.
Related reports
- #52539 — Windows workspace settings failures involving HTTP 403.
- #51661 — Desktop Work Lockdown Mode check failure.
- #52790 — Recurring Windows desktop workspace settings failure.
These reports have overlapping symptoms. I have not established that my installation has the same underlying cause, or that my HTTP 403 was a Cloudflare challenge.
Current status: Temporarily recovered as of October 11, 2026. The issue has recurred across two app versions, and a lasting resolution has not been established.
Please investigate the intermittent workspace initialization failure and delayed recovery on Windows.
What version of the Codex App are you using?
Current Windows app version:
26.1007.2314.0.The issue first occurred on
26.1002.7124.0and recurred after upgrading.What platform is your computer?
Windows 11.
What issue are you seeing?
The ChatGPT/Codex Windows desktop application intermittently fails to load workspace settings. It first occurred on October 10, 2026, and recurred after restarting Windows on October 11.
During the failure, the normal ChatGPT interface with the Chat and Work sections is unavailable. The application switcher shows “ChatGPT Work” and “Codex,” and the main view displays a workspace settings error.
ChatGPT Work remains functional in a web browser using the same account while the desktop application is affected.
The following errors were observed at different stages, not necessarily simultaneously:
Local Work executor registration failed (HTTP 403)无法检查锁定模式— approximately “Unable to check Lockdown Mode”无法加载工作空间设置— approximately “Unable to load workspace settings”请重试以继续聊天— approximately “Please retry to continue chatting”The HTTP 403 banner was observed during the initial occurrence. It was not independently confirmed during the recurrence after reboot.
Clicking Retry, switching proxy modes, and signing out and back in do not consistently restore functionality immediately. The application eventually recovered without further configuration changes, but the recovery delay was not measured.
What steps can reproduce the bug?
The issue is intermittent; a reliable reproducer has not yet been established. The observed sequence was:
Rebooting preceded the recurrence, but the exact trigger and the role of startup order have not been established.
What is the expected behavior?
The desktop application should reliably load workspace settings and make ChatGPT Chat and Work available after Windows startup.
If initialization fails temporarily, Retry should provide a supported recovery path, or the application should display an actionable error explaining why initialization cannot complete.
Additional information
Environment
Troubleshooting timeline
26.1002.7124.0: Switching Clash from Rule to Global mode restored functionality. After adding high-priority proxy rules forchatgpt.com,openai.com,oaistatic.com,oaiusercontent.com, andoaistatsig.com, Rule mode also worked.26.1007.2314.0; the application worked afterward.No application reset, cache deletion, or reinstallation was performed.
Initial connectivity checks
PowerShell
Test-NetConnectionchecks on TCP port 443 returned:chatgpt.comauth.openai.comdesktop.chat.openai.comchallenges.cloudflare.comThese direct TCP checks do not establish whether requests through the configured HTTP proxy succeeded.
Related reports
These reports have overlapping symptoms. I have not established that my installation has the same underlying cause, or that my HTTP 403 was a Cloudflare challenge.
Current status: Temporarily recovered as of October 11, 2026. The issue has recurred across two app versions, and a lasting resolution has not been established.
Please investigate the intermittent workspace initialization failure and delayed recovery on Windows.