[Windows Desktop 26.915.4065.0] Profile and subscription details blank after update; workspace routing returns 432

What version of the Codex App are you using?

Windows MSIX package version: 26.915.4065.0.

What subscription do you have?

Signed in with ChatGPT. Exact subscription tier was intentionally not collected for this public report.

What platform is your computer?

Microsoft Windows NT 10.0.26200.0, x64.

What issue are you seeing?

After updating the Windows desktop app on September 20, 2026, personal profile and subscription/usage information no longer appears in the desktop UI.

The account itself is still recognized by the application. Sanitized logs show that account reads complete and the failing profile query records both hasAccountId=true and hasUserId=true. There are no matching HTTP 401 or 403 failures.

The profile endpoint is instead rejected with the following recurring sequence:

sa_server_request_failed
errorMessage="Workspace routing is unavailable"
routePattern=/wham/profiles/me
status=432

profile_usage_query_failed
hasAccountId=true
hasUserId=true
status=432

This reproduces across multiple full app launches.

The same launches also repeatedly fail to persist the desktop identity/feature-state file:

Failed to persist global state
errorCode=EXDEV
errorMessage="EXDEV: cross-device link not permitted, rename ...statsig-state.json.tmp-... -> ...statsig-state.json"

Failed to initialize host Statsig identity
errorMessage="EXDEV: cross-device link not permitted, rename ...statsig-state.json.tmp-... -> ...statsig-state.json"

The affected AppData directories have the Windows Encrypted attribute. Application stack/source paths in the logs also reference both C:\Program Files\WindowsApps\OpenAI.Codex_26.915.4065.0_... and D:\WindowsApps\OpenAI.Codex_26.915.4065.0_.... These are observations only; their causal relevance is not confirmed.

Across four sampled launches, the primary desktop-process logs contained:

What steps can reproduce the bug?

1. Update/install Windows desktop build 26.915.4065.0.
2. Sign in using ChatGPT.
3. Open the profile/account area.
4. Observe that personal profile and subscription/usage details are blank or unavailable.
5. Inspect the desktop log for the current launch.
6. Observe repeated /wham/profiles/me failures with status 432 and Workspace routing is unavailable.

Recovery attempts that did not resolve it

• Fully quit the application, including background processes, and relaunch.
• Sign out and sign back in with ChatGPT.
• Confirm/select the intended workspace.
• Windows application Repair.
• Windows application Reset/reinstall.

Expected behavior

The desktop app should resolve the signed-in user's workspace route and display profile, subscription, and usage information. If local identity/state migration fails, the UI should show an actionable error and provide a supported recovery mechanism.

Additional information

• The separately installed npm Codex CLI is not being used as evidence for the desktop authentication state.
• No authentication tokens, account IDs, user IDs, email addresses, usernames, full local paths, or raw log files are included in this report.
• Full logs can be supplied privately if maintainers provide a secure channel.

Start with the desktop profile request at /wham/profiles/me and the workspace-routing failures, then inspect the Statsig identity state persistence logs showing EXDEV during the rename of statsig-state.json. Reproduce on Windows build 26.915.4065.0 and determine how routing and local state migration interact. Done means profile, subscription, and usage details load, or the UI provides an actionable recovery path.