openai / openai/codex

[Windows][26.915.31029] Account/profile APIs fail with status 432 "Workspace routing is unavailable"

Open
#46,382 5 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

app auth bug connectivity windows-os
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What version of the Codex App are you using (From “About Codex” dialog)?

26.915.31029

What subscription do you have?

ChatGPT Pro

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

The Codex Windows desktop app is still signed in and recognizes my ChatGPT account, but account/profile-related information fails to load.

The account menu still shows my signed-in email address, but the rest of the account/profile information is missing or unavailable.

The desktop logs repeatedly show:

warning [electron-message-handler] sa_server_request_failed
attachAuth=true
attachIntegrityState=true
errorMessage="Workspace routing is unavailable"
method=get
routePattern=/settings/user
status=432
url=/settings/user

The same error occurs for multiple endpoints, including:

/wham/tasks/list
/wham/usage
/accounts/verified_access
/wham/analytics/daily-code-review-metrics
/subscriptions/credits/discount-offer
/subscriptions/auto_top_up/settings

These requests consistently fail with:

status=432
errorMessage="Workspace routing is unavailable"

However, local AppServer account/auth calls appear to complete successfully:

[AppServerConnection] response_routed
errorCode=null
method=account/read

and:

[AppServerConnection] response_routed
errorCode=null
method=getAuthStatus

<img width="247" height="69" alt="Image" src="https://github.com/user-attachments/assets/c561ef49-af73-41ce-beed-dc37b209cb2f" />

### What steps can reproduce the bug?

1. Launch Codex App on Windows.
2. Sign in with my ChatGPT account.
3. Open the account/profile menu.
4. The signed-in email address is visible, but account/profile information does not load correctly.
5. Check the Codex desktop logs.
6. Requests such as `/settings/user` and `/wham/usage` fail with:
   `status=432` and `Workspace routing is unavailable`.

### What is the expected behavior?

The Codex App should successfully resolve the workspace routing for the signed-in ChatGPT account and load the account/profile information normally.

Requests such as `/settings/user`, `/wham/usage`, and other account/workspace-dependent APIs should succeed instead of returning:

`432 Workspace routing is unavailable`

### Additional information

The ChatGPT web app works normally with the same account.

This does not appear to be a simple logged-out or expired-session state. The desktop app still recognizes the signed-in account, and `account/read` and `getAuthStatus` complete without an AppServer error.

The failing `/settings/user` request has authentication/account-related headers attached, including:

```text
ChatGPT-Account-ID
X-OpenAI-Expected-Account-Id
X-OpenAI-Attach-Auth
X-OpenAI-Attach-Integrity-State

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Windows desktop flow and inspect the electron-message-handler logs for /settings/user and /wham/usage, comparing them with the successful account/read and getAuthStatus calls. Trace the workspace-routing failure across the listed account endpoints; done means account/profile data loads and those requests no longer return status 432.

Written by the indexing model from the issue text.

Assessment

Tech stack
electron, rust
Domain
api, authentication, desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.