Windows: New chats blocked by workspace settings verification; built-in feedback also unavailable #52874

Activity

1. TreaFantasy

   added

   appIssues related to the Codex desktop appIssues related to the Codex desktop app

   on Oct 10, 2026
2. github-actions

   added

   bugSomething isn't workingSomething isn't working

   windows-osIssues related to Codex on Windows systemsIssues related to Codex on Windows systems

   connectivityIssues involving networking or endpoint connectivity problems (disconnections)Issues involving networking or endpoint connectivity problems (disconnections)

   authIssues related to authentication and accountsIssues related to authentication and accounts

   on Oct 10, 2026
3. github-actions commented on Oct 10, 2026

   

   github-actionsBot

   on Oct 10, 2026 – with GitHub Actions

   Contributor

   More actions

   Potential duplicates detected. Please review them and close your issue if it is a duplicate.

   • Windows desktop: new chats blocked by workspace settings Cloudflare challenge; sign-out/in restores access temporarily #52790
   • Unable to load workspace settings #52437
   • Windows: persistent workspace settings Cloudflare 403; sending during Retry can start a chat #52539
   • [Windows][26.1007.21434] Couldn't load workspace settings still blocks new chats after update #51917

   Powered by Codex Action
4. TreaFantasy commented on Oct 10, 2026

   

   TreaFantasy

   on Oct 10, 2026

   Author

   More actions

   Update: The issue persists after updating to Windows package 26.1007.2314.0. I verified that the running desktop process uses the updated package.

   Post-update logs still show HTTP 403 with errorCode=cloudflare_challenge for /settings/user and /accounts/check/{version}. New chats remain blocked by the workspace settings error.

   The update did not resolve the issue on this installation.
5. leishanshan8257-hash commented on Oct 11, 2026

   

   leishanshan8257-hash

   on Oct 11, 2026 – with ChatGPT Codex Connector

   More actions

   Repeated workspace-settings failures — additional affected-user report (2026-10-11)

   The affected Windows user explicitly requested escalation because this error has occurred many times:

   无法加载工作空间设置
   请重试以继续聊天
   Couldn't load workspace settings / Retry to continue chatting

   This is a recurring disruption to starting work, not just a single failed load. The user reports that restarting the desktop app did not resolve it. ChatGPT web login was successful during the earlier network comparison.

   Verified local evidence, separate from the user report

   • Windows package version checked on 2026-10-11: 26.1007.2314.0. This is the package version, not the About-dialog app version.
   • Previously inspected desktop logs from 2026-10-09 contain repeated failures across account, settings, and conversation-list requests. Selected fields from that historical log, in UTC:

   2026-10-09T11:43:38.544Z routePattern=/accounts/check/{version} status=403 errorCode=cloudflare_challenge
   2026-10-09T11:43:38.544Z routePattern=/settings/user status=403 errorCode=cloudflare_challenge
   

   Evidence limits: These log entries are historical, not a fresh October 11 capture. The repeated UI symptom is reported by the affected user and documented in a supplied screenshot; this follow-up does not claim a new automated UI reproduction or prove that the Cloudflare responses cause the composer failure. A lasting fix has not been verified. A sign-out/sign-in outcome is not independently established by this follow-up.

   Please investigate the recurring settings-initialization failure and desktop handling of security challenges. Please provide an actionable, supported recovery path that preserves local chats/projects and required authentication/policy checks rather than relying on repeated Retry or restart.

   Submitted with AI assistance at the affected user's explicit request. No raw logs, screenshots, project contents/names, local paths, account/session identifiers, cookies, or credentials are attached.

   👍React with 👍1Reacted by jenglong1899
6. jenglong1899 commented on Oct 12, 2026

   

   jenglong1899

   on Oct 12, 2026

   More actions

   same
7. aakonovalov commented on Oct 14, 2026

   

   aakonovalov

   on Oct 14, 2026 – with ChatGPT Codex Connector

   More actions

   I am also affected on Windows. Additional recurrence evidence: on Oct 8, after fully isolating old .codex state and restoring a clean configuration, desktop Codex successfully passed new chats, send/response, archiving, fresh chat after archive, restart, local projects, and GitHub integration. On the next use on Oct 14, the app prompted for reauthentication; ChatGPT web sign-in succeeded, but desktop immediately returned "Couldn't load workspace settings" with disabled composer in both existing projects and projectless chats. The latest offered app update did not help.

   The Oct 14 desktop log shows 41 matches for status=403, including /settings/user and /accounts/check/{version}, but no literal cloudflare_challenge in that log. This may be a related failure with a different error classification, so I am not assuming the root cause is identical.

   Full sanitized technical report and reproducible timeline: #51917 (comment) . Please investigate why the clean recovery was temporary and what changes during desktop reauthentication after idle time.
8. 0xdevalias commented on Oct 17, 2026

   

   0xdevalias

   on Oct 17, 2026

   Last edited by 0xdevalias

   More actions

   Related settings-failure evidence and navigation diagnostics: our October 16 macOS sample shows the same workspace-settings warning with HTTP 503 “Unable to fetch authentication verification keys” on /settings/user and /accounts/check/{version}. The app also repeatedly left existing chats for Home; the navigation timeline is in #53901. We have not tested or reproduced the feedback-permission failure described here.

   Further read-only inspection on October 17 verified a more specific branch in our installed 26.1007.71326/build 20398 bundle: the Pages/Spaces availability calculation (t3r in app-shared-8340f229c2b3.js) explicitly returns disabled when the chatgpt capability result has isError. This branch runs before the later feature-gate checks, so a capability error can disable availability without a feature flag itself defaulting off. The inspected ZPs route guard redirects disabled availability to /; the Page navigation interceptor can forward that destination to navigateInOwnerWindow.

   That strengthens the proposed error → disabled availability → Home redirect path. It remains static code evidence: we have not captured the capability state and navigation caller together for our October 16 occurrence, or proven which guard initiated each jump. Regardless of why availability is disabled, an unclaimed hidden prewarm's automatic redirect should not navigate/focus the user's active chat.

   Main investigation and detailed diagnostics

   • macOS: hidden Page prewarm redirects the active chat to New chat (captured cross-window navigation) #53901
     • Main place to compare the hidden-window navigation mechanism; our selected timeline and code findings.
   • [Windows][26.1007.21434] Couldn't load workspace settings still blocks new chats after update #51917
     • Main place to compare settings/account failures and composer recovery; our selected 503 evidence.
   • macOS desktop unexpectedly switches an existing chat to New Chat; hidden Pages prewarm navigation suspected #53570
     • Relevant #53570 follow-up — account-check HTTP 500, subsequent navigation, and capability-error handling.

   See also: related reports

   These links group matching symptoms, error responses, and suspected mechanisms for comparison. They do not label every report as a confirmed duplicate or establish a single backend cause.

   • macOS: hidden Page prewarm redirects the active chat to New chat (captured cross-window navigation) #53901
     • Navigation mechanism: captured hidden Page prewarm → owner-window navigation path; our follow-up adds the October 16 timeline and current-build capability-error handling.
   • [Windows][26.1007.21434] Couldn't load workspace settings still blocks new chats after update #51917
     • Settings/composer symptom: unavailable account/settings checks block sending; our follow-up records verification-key HTTP 503s on the same endpoints that other reports show failing with 403s.
   • Codex App on Windows intermittently redirects active threads to the "New Thread" page #14411
     • Navigation symptom: Windows intermittently leaves active threads for New Chat, including recent hidden-window timing reports. Older WSL/terminal-related occurrences may have different causes.
   • [macOS][26.1002.52244] Active chat unexpectedly navigates to new-chat page during scrolling or foreground activation #52491
     • Navigation symptom and suspected mechanism: macOS route resets, bootstrap/availability observations, and analysis of hidden-window fallback routing.
   • macOS desktop unexpectedly switches an existing chat to New Chat; hidden Pages prewarm navigation suspected #53570
     • Suspected mechanism: Pages prewarm/availability analysis; a follow-up reports an account-check HTTP 500 followed 76 ms later by Home navigation, and identifies the explicit capability-error → disabled mapping.
   • Bug: app switches to New chat on its own while idle #17494
     • Navigation symptom: unsolicited New Chat while idle, with existing threads still in the sidebar. This report does not establish the hidden-window mechanism.
   • Windows desktop workspace settings blocked by Cloudflare challenge across restart/update; recovery after normal browser access, token refresh and Retry #51691
     • Settings symptom and recovery: Cloudflare 403s on settings/account endpoints and an observed browser/account-refresh/Retry recovery sequence. That sequence is not a verified remedy for our 503 occurrence.
   • Windows desktop: intermittent workspace-settings failures plus missing rollout files after reinstall #53964
     • Settings symptom: intermittent settings/model failures during active use and after a fresh install. Its missing-rollout and persistence findings remain separate; we have not reproduced them.
   • ChatGPT desktop Chat/Work loses installed skills during authentication verification 503s #39555
     • Matching error response: the exact verification-key HTTP 503 reported across Desktop endpoints, with skill-availability symptoms. We have not reproduced the skill-specific impact.

   Only selected technical observations are included. No raw logs, credentials, account/conversation identifiers, private paths, or screenshots are attached. No new live reproduction or verified fix is claimed.