You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
macOS desktop new-chat composer blocked by workspace-settings load error; DeviceCheck registration returns 403 after sign-in and reinstall #53333
User-visible failure
Opening a new local chat shows “无法加载工作空间设置 / 请重试以继续聊天” (“Couldn't load workspace settings / Retry to continue chatting”). The first prompt cannot be sent. It happens with different folder projects and without selecting a project. Existing desktop conversations continue to accept messages.
Already attempted
Retry in the new-chat page.
Signing out and signing in again.
Uninstalling and reinstalling the desktop application.
The failure persists. The user confirms the same account can create new chats and send messages on chatgpt.com in a browser.
Read-only diagnostic observations
The local stdio app-server initializes successfully. Existing-conversation turn/start responses have errorCode=null.
Account/workspace initialization requests, including /accounts/check/{version}, surface status=500 because of that registration failure.
Some other requests show errorCode=cloudflare_challenge and status=403, including /sentinel/heartbeat.
In the latest post-reinstallation session, the same failures recur around 2026-10-12 09:19–09:27 UTC.
Account usage limit is not reached. Disk free space is ample. System time is consistent with UTC.
Scope and uncertainty
The failure appears specific to desktop initialization / device registration / service verification. Successful native attestation generation is distinct from successful server registration. These observations do not prove a particular network problem, account restriction, operating-system defect, or application regression.
Expected behavior and request
New-chat workspace settings should load and allow the first prompt to be sent. Please investigate the device-registration 403 and workspace-settings initialization failure, and provide a supported recovery procedure that preserves local chat history and project registrations. Please expose the underlying failure clearly instead of indefinitely blocking the composer behind a generic workspace-settings warning.
Privacy
This draft contains software versions, reproduction steps and selected error metadata. It does not attach raw logs, account identifiers, local file paths, project content, chat content, cookies or credentials.
Running app: ChatGPT desktop app with the integrated Codex interface, bundle ID com.openai.codex, version 26.1007.30912 (checked on the machine).
Observed: When opening a new Codex conversation, the composer shows “无法加载工作空间设置 / 请重试以继续聊天” (“Couldn't load workspace settings / Retry to continue chatting”), blocking the first message.
Scope: Reproduces across multiple different project folders and without selecting a project. It is not isolated to one workspace.
Retry: Clicking “Retry” produces the same error.
Diagnostics: Read-only checks confirmed the running app version and OS. Available macOS logs did not establish the underlying cause, and access to a local diagnostic database was blocked. No DeviceCheck HTTP status, account verification failure, or network root cause has been verified for this machine; the DeviceCheck 403 described in the original issue should not be assumed here.
Not attempted: Sign-out/sign-in, reinstall, cache deletion, or configuration edits.
Expected: A new conversation should initialize and accept its first message with any folder selection or no folder selection.
Please investigate the shared new-chat workspace initialization failure and document a recovery procedure that preserves existing conversations and project settings. No raw logs, private filesystem paths, account identifiers, or project content are included in this report.
Failure: New GPT tasks/conversations show “无法加载工作空间设置 / 请重试以继续聊天” (“Couldn’t load workspace settings / Retry to continue chatting”), preventing the first message from being submitted.
Verified on this machine:
Desktop sign-out/sign-in was completed. The log records account_login_completed, success=true, at 2026-10-12T13:52:36.469Z. The failure persists afterward.
DeviceCheck registration subsequently fails with devicecheck_registration_http_failed and DeviceCheck registration failed (403). Dependent requests such as /settings/user and /tbo surface status 500 from that failure.
Other requests separately return HTTP 403 / cloudflare_challenge, including /sentinel/heartbeat.
Local config.toml parses successfully; the local app-server config/read succeeds.
The installed application passes full code-signature verification and is signed by OpenAI OpCo, LLC.
After web sign-in, projects, chat history and the composer render normally in the browser, while the desktop failure continues.
A system HTTP/HTTPS/SOCKS proxy is configured at the loopback address 127.0.0.1:7897. This is environment context only; we have not established that the proxy, the account, the OS, or an application regression is the cause.
Request: Please investigate the native desktop DeviceCheck registration 403 and resulting new-chat workspace initialization failure, and provide a supported recovery path that preserves existing chat history and project settings. Please surface the underlying failure rather than only a generic workspace-settings warning.
No application security checks were disabled, and no application files, authentication storage, chat history or project configuration were modified. No raw logs, credentials, cookies, account identifiers, private filesystem paths, conversation content or project code are attached.
Activity
github-actions commentedon Oct 12, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
personalxz000001-debug commentedon Oct 12, 2026
Additional independent reproduction (2026-10-12):
com.openai.codex, version26.1007.30912(checked on the machine).Expected: A new conversation should initialize and accept its first message with any folder selection or no folder selection.
Please investigate the shared new-chat workspace initialization failure and document a recovery procedure that preserves existing conversations and project settings. No raw logs, private filesystem paths, account identifiers, or project content are included in this report.
alison-xx commentedon Oct 12, 2026
Additional affected machine — sanitized diagnostic report, 2026-10-12.
Environment: ChatGPT/Codex macOS desktop app
26.1007.30912; macOS26.6.2; Apple Silicon (arm64).Failure: New GPT tasks/conversations show “无法加载工作空间设置 / 请重试以继续聊天” (“Couldn’t load workspace settings / Retry to continue chatting”), preventing the first message from being submitted.
Verified on this machine:
account_login_completed,success=true, at2026-10-12T13:52:36.469Z. The failure persists afterward.devicecheck_registration_http_failedandDeviceCheck registration failed (403). Dependent requests such as/settings/userand/tbosurface status 500 from that failure.cloudflare_challenge, including/sentinel/heartbeat.config.tomlparses successfully; the local app-serverconfig/readsucceeds.127.0.0.1:7897. This is environment context only; we have not established that the proxy, the account, the OS, or an application regression is the cause.Request: Please investigate the native desktop DeviceCheck registration 403 and resulting new-chat workspace initialization failure, and provide a supported recovery path that preserves existing chat history and project settings. Please surface the underlying failure rather than only a generic workspace-settings warning.
No application security checks were disabled, and no application files, authentication storage, chat history or project configuration were modified. No raw logs, credentials, cookies, account identifiers, private filesystem paths, conversation content or project code are attached.
The complete sanitized diagnostic report follows:
ChatGPT/Codex 桌面新任务加载工作空间失败
应用版本:26.1007.30912
系统:macOS
表现:新建 GPT 任务提示“无法加载工作空间设置 / 请重试以继续聊天”。
已核验:
请协助排查原生桌面客户端设备校验注册及 Cloudflare 挑战。未清空聊天、认证存储或项目配置,未关闭设备校验或修改应用文件。
最新脱敏事件:
[
{
"utc": "2026-10-12T13:52:36.469Z",
"success": "true"
},
{
"utc": "2026-10-12T13:54:43.332Z",
"errorCode": "devicecheck_registration_http_failed",
"routePattern": "/settings/user",
"status": "500",
"underlyingError": "DeviceCheck registration failed (403)"
},
{
"utc": "2026-10-12T13:54:47.591Z",
"errorCode": "devicecheck_registration_http_failed",
"routePattern": "/tbo",
"status": "500",
"underlyingError": "DeviceCheck registration failed (403)"
},
{
"utc": "2026-10-12T13:54:47.592Z",
"errorCode": "devicecheck_registration_http_failed",
"routePattern": "/settings/user",
"status": "500",
"underlyingError": "DeviceCheck registration failed (403)"
},
{
"utc": "2026-10-12T13:55:39.640Z",
"errorCode": "cloudflare_challenge",
"routePattern": "/sentinel/heartbeat",
"status": "403"
},
{
"utc": "2026-10-12T13:55:47.871Z",
"errorCode": "devicecheck_registration_http_failed",
"routePattern": "/tbo",
"status": "500",
"underlyingError": "DeviceCheck registration failed (403)"
},
{
"utc": "2026-10-12T13:55:49.119Z",
"errorCode": "devicecheck_registration_http_failed",
"routePattern": "/tbo",
"status": "500",
"underlyingError": "DeviceCheck registration failed (403)"
},
{
"utc": "2026-10-12T13:55:51.397Z",
"errorCode": "devicecheck_registration_http_failed",
"routePattern": "/tbo",
"status": "500",
"underlyingError": "DeviceCheck registration failed (403)"
},
{
"utc": "2026-10-12T13:55:55.667Z",
"errorCode": "devicecheck_registration_http_failed",
"routePattern": "/tbo",
"status": "500",
"underlyingError": "DeviceCheck registration failed (403)"
}
]