Codex Desktop white screen after login - Statsig workspace_type Invalid input

Open 💬 3 comments Opened Jun 6, 2026 by Brococoli
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

Codex Desktop white screen after login

Summary

Codex Desktop opens to a blank white window after login. Login, network, app-server startup, and thread listing appear healthy, but the renderer logs a Statsig bootstrap error during post-login initialization.

Key Error

Statsig: error while bootstrapping post-login client
path: ["user","custom","workspace_type"]
message: "Invalid input"

Full repeated log excerpt:

2026-06-06T04:38:40.893Z error [electron-message-handler] Statsig: error while bootstrapping post-login client errorMessage="[
  {
    \"code\": \"invalid_union\",
    \"errors\": [
      [{ \"expected\": \"string\", \"code\": \"invalid_type\", \"path\": [], \"message\": \"Invalid input\" }],
      [{ \"expected\": \"number\", \"code\": \"invalid_type\", \"path\": [], \"message\": \"Invalid input\" }],
      [{ \"expected\": \"boolean\", \"code\": \"invalid_type\", \"path\": [], \"message\": \"Invalid input\" }],
      [{ \"expected\": \"array\", \"code\": \"invalid_type\", \"path\": [], \"message\": \"Invalid input\" }],
      [{ \"expected\": \"undefined\", \"code\": \"invalid_type\", \"path\": [], \"message\": \"Invalid input\" }]
    ],
    \"path\": [\"user\", \"custom\", \"workspace_type\"],
    \"message\": \"Invalid input\"
  }
]"

Environment

macOS: 26.3.0 arm64
Codex App: 26.602.40724
Bundle version: 3593
Bundled CLI: codex-cli 0.137.0-alpha.4
Homebrew CLI: codex-cli 0.137.0
Auth: Logged in using ChatGPT

Diagnostics Already Tried

  • Restarted Codex Desktop.
  • Verified CLI auth: codex login status returns Logged in using ChatGPT.
  • Ran codex doctor --summary; auth, websocket, reachability, config, and install are healthy.
  • Cleared Chromium/GPU/code caches.
  • Moved Local Storage and Session Storage.
  • Moved full Electron profile:
  • ~/Library/Application Support/Codex
  • ~/Library/Application Support/com.openai.codex
  • ~/Library/Caches/Codex
  • ~/Library/Caches/com.openai.codex
  • Reinstalled Codex Desktop via codex app /Users/bytedance.

The white screen still reproduces after full profile reset and app reinstall.

Relevant Healthy Startup Signals

window ready-to-show
window main frame finished load
account/read ... errorCode=null
thread/list ... errorCode=null
[startup][renderer] app routes mounted

Current Hypothesis

The issue appears to be a Codex Desktop renderer initialization failure caused by an account-side Statsig/custom user field value, specifically user.custom.workspace_type, not by local auth, local network, app installation, or stale profile cache.

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 2 months ago

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

  • #26735

Powered by Codex Action

yuhang1130 · 2 months ago

Additional reproduction from another macOS user/account.

I can reproduce the same post-login Statsig failure on Codex Desktop, but the visible symptom is a black/unresponsive window with a renderer pegged at ~97-99% CPU.

Environment:

macOS: 26.5.1 (25F80), arm64, Apple M1 Pro
Codex Desktop: 26.602.40724
Bundle version: 3593
Chromium base: 149.0.7827.54
Bundled CLI: codex-cli 0.137.0-alpha.4
Standalone CLI: codex-cli 0.137.0
Auth method: ChatGPT

Network and startup signals look healthy:

ab.chatgpt.com/v1/initialize -> 204
chatgpt.com/backend-api/wham/statsig/bootstrap -> 200
chatgpt.com/backend-api/wham/accounts/check -> 200
[startup][renderer] app routes mounted

The failing fingerprint is the same:

[electron-message-handler] Statsig: error while bootstrapping post-login client
code: invalid_union
path: ["user", "custom", "workspace_type"]
message: Invalid input

WARN [Statsig] SDK initialization has not completed. Reason: Loading:Unrecognized

Isolation results:

Real ~/.codex with signed-in auth.json:
  Reproduces black/unresponsive Desktop window and renderer ~97-99% CPU.

Clean Chromium profile:
  Still reproduces.

Empty workspace:
  Still reproduces.

Temporary empty CODEX_HOME with no auth:
  Does not reproduce; renderer CPU stays low.

Copied real CODEX_HOME with only auth.json removed:
  Does not reproduce; app initializes normally and routes mount.

After re-login:
  ~/.codex/auth.json is regenerated, then the same Statsig workspace_type invalid_union error returns and the renderer pegs CPU again.

Renderer sample confirms the hot process is the Electron renderer main thread in V8/JS microtasks, not GPU/network/system proxy blocking.

This strongly suggests the trigger is an account-side post-login Statsig/custom user field value for user.custom.workspace_type that Codex Desktop 26.602.40724 fails to parse, causing a renderer-side loop/hang. CLI/TUI remains usable as a workaround.

KimGSeok · 2 months ago

I split my newer-build, pre-window-creation hang into a separate issue because it looks related but has a distinct failure mode: #27497.

Short summary: Codex Desktop 26.608.12217 on macOS 26.1 hangs at ~100% CPU before [IpcRouter] / [window-manager] when ~/.codex/auth.json is present. Moving auth.json aside lets the app start normally in a signed-out state.