[Windows] Personal Plus account has Work/Codex access on web/CLI but desktop app incorrectly says “Contact your admin”
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
Environment
- ChatGPT plan: Personal Plus (not Business/Enterprise)
- OS: Windows
- ChatGPT Windows desktop app version: 26.901.6511.0
- Codex CLI version: 0.153.4
Issue
The ChatGPT Windows desktop app incorrectly denies access to both ChatGPT Work and Codex and displays messages equivalent to:
- “You don't have access to Work yet. Contact your admin to request access.”
- “You don't have access to Codex yet. Contact your admin to request access.”
This is a personal Plus account, so there is no workspace administrator to contact.
Cross-client verification
I have isolated the problem to the Windows desktop experience:
- ChatGPT Work on web: WORKING. The same Plus account can select Work and open the Work task interface normally.
- Codex CLI: WORKING. The same ChatGPT account authenticates successfully and Codex responds normally.
- ChatGPT Work in Windows desktop app: ACCESS DENIED.
- Codex in Windows desktop app: ACCESS DENIED.
Authentication verification
I completed a fresh OpenAI OAuth authentication for the Windows app. During OAuth:
- The correct account was verified by email.
- The workspace selection screen explicitly identified the workspace as Personal account.
- OAuth completed successfully and returned to the Windows application.
- Work and Codex still showed the same access-denied / “Contact your admin” messages.
Troubleshooting already performed
- Signed out and signed back in.
- Completed fresh OAuth authentication.
- Windows Repair/Reset attempted.
- Confirmed the app is up to date.
- Verified that Codex backend entitlement is functional through Codex CLI.
- Verified that Work entitlement is functional through ChatGPT web.
Expected behavior
Because Work is already enabled for this account on the web and Codex CLI works with the same ChatGPT account, the Windows desktop app should recognize the account's available Work/Codex access instead of showing an administrator-access error.
Additional context
This appears related to Windows desktop entitlement/account-state synchronization or client-side access gating rather than a general rollout or subscription eligibility problem.
A similar Windows/Plus symptom has also been reported in #35113.
I can provide screenshots showing:
- Work functioning on the web
- Work access denied on Windows
- Codex access denied on Windows
- OAuth workspace selection showing Personal account
No authentication tokens or other sensitive account data will be posted publicly.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files or tests are identified in the report. Start by locating the Windows desktop entitlement and account-state handling, then compare its Work/Codex access checks with the successful web and Codex CLI behavior; done means a Personal Plus account with those entitlements is recognized without an administrator error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- authorization, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100