Codex Desktop logs into Personal account instead of selected ChatGPT workspace

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

26.519.41501

What subscription do you have?

workspace

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Codex Desktop is authenticating into the wrong ChatGPT account context.

I am trying to use Codex Desktop with my ChatGPT workspace account named Upfunding, but after login the app signs me into the account context shown as Personal account instead of the workspace.

In the Codex Desktop account menu, it shows:

• Email: cowebs.lb@gmail.com
• Account type: Personal account

Expected behavior:
Codex Desktop should allow me to select or authenticate into the Upfunding ChatGPT workspace.

Actual behavior:
Codex Desktop logs me into the Personal account context and does not switch to / recognize the Upfunding workspace.

I checked with my workspace admin, and they confirmed this is not caused by workspace permission/device-auth settings on their side.

I also tried clearing local auth and cache, then logging in again, but Codex Desktop still returns to the Personal account context.

Steps tried:

1. Logged out of Codex Desktop.
2. Removed local auth file:

```powershell
Remove-Item "$env:USERPROFILE\.codex\auth.json" -Force -ErrorAction SilentlyContinue

What steps can reproduce the bug?

1. Install/open Codex Desktop on Windows.

1. Log in with a ChatGPT account that has access to both:

• a Personal account context
• a ChatGPT workspace named Upfunding

1. Complete the login flow normally.

1. Open the account menu in Codex Desktop.

1. Observe that Codex Desktop shows:

• Email: cowebs.lb@gmail.com
• Account type: Personal account

1. Try logging out and clearing local auth:

```powershell
Stop-Process -Name Codex -Force -ErrorAction SilentlyContinue
Remove-Item "$env:USERPROFILE\.codex\auth.json" -Force -ErrorAction SilentlyContinue

What is the expected behavior?

Codex Desktop should authenticate into the ChatGPT workspace I have access to, named Upfunding, instead of defaulting to the Personal account context.

Expected behavior:

• During login, Codex Desktop should allow me to select the intended ChatGPT workspace, or automatically use the correct workspace context.
• After login, the account menu should show the Upfunding workspace rather than Personal account.
• Workspace-based subscription/features should be available in Codex Desktop.
• If Codex cannot access the workspace, it should show a clear error explaining why instead of silently logging into the wrong account context.

I do not have a screenshot for this section, but the expected account context is the Upfunding ChatGPT workspace.

Additional information

Additional context:

This appears to be a workspace/account-selection issue in the Codex Desktop ChatGPT login flow.

My ChatGPT account email is:

cowebs.lb@gmail.com

That email has access to a ChatGPT workspace named Upfunding, which is the workspace I need to use with Codex Desktop.

However, Codex Desktop always ends up signed into the Personal account context instead of the Upfunding workspace.

I attached screenshots showing the flow:

1. Codex Desktop account menu shows:

• cowebs.lb@gmail.com
• Personal account
• usage remaining under the Personal account

1. The browser login/consent page says:

• “Sign in to Codex with ChatGPT”
• account shown: cowebs.lb@gmail.com
• text says Codex will use my ChatGPT account’s plan/rate limits/preferences

1. The OpenAI account chooser only shows my account/email, but does not provide a workspace selector or a way to choose the Upfunding workspace before returning to Codex.

After completing login, Codex Desktop still shows Personal account, not the Upfunding workspace.

I checked with my workspace admin and they confirmed this should not be caused by workspace permission/device-auth settings.

I also tried clearing local Codex auth/cache state and logging in again, but the app still binds to the Personal account.

This seems to happen before any coding session starts, so there is no session ID, token limit usage, or context window usage to provide.

The main issue is that the login flow appears to authenticate the user identity, but not the intended ChatGPT workspace context.