›_ Codex Issues
Codex Issues / #26735

[Windows] Browser and Computer Use disabled for personal Plus trial account; availability resolves statsig-disabled

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

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

26.602.4764.0

What subscription do you have?

ChatGPT Plus trial, personal Gmail account, not an organization/workspace account

What platform is your computer?

Microsoft Windows NT 10.0.19045.0 x64

What issue are you seeing?

Browser and Computer Use are disabled in Codex App settings.

In Settings > Browser, the Browser toggle is disabled and shows:
"Disabled by your organization or unavailable in your region"

In Settings > Computer use, Google Chrome is disabled and shows the same message:
"Disabled by your organization or unavailable in your region"

This is a personal Gmail account with a ChatGPT Plus trial, signed into the Codex App with my ChatGPT account. I am located in Vietnam. This is not a company, school, Team, Enterprise, or managed workspace account.

Local diagnostics suggest this is not a local config issue. The Codex desktop logs repeatedly show:

browser_use_availability_resolved available=false browserPane=true platform=Windows reason=statsig-disabled release=26.602.40724

The logs also show a Statsig bootstrap error:

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

The local feature bootstrap cache is empty:

{"enabledOwlFeatureNames":[]}

The generated bundled marketplace appears to expose only latex, not Browser/Chrome/Computer Use.

There is also this Windows 10 runtime error, which may or may not be related:

Primary runtime install failed before first turn
errorMessage="Codex Workspace dependencies are not supported on Windows 10."

What steps can reproduce the bug?

Feedback ID: 019e9b04-919d-7e33-b906-42bed4475e12

  1. Install/open Codex App on Windows.
  2. Sign in with a personal ChatGPT Plus trial account.
  3. Open Settings > Browser.
  4. Observe that Browser is disabled with:

"Disabled by your organization or unavailable in your region"

  1. Open Settings > Computer use.
  2. Observe that Google Chrome / Computer Use is disabled with the same message.
  3. Check local Codex desktop logs.
  4. The logs show:

browser_use_availability_resolved available=false browserPane=true platform=Windows reason=statsig-disabled release=26.602.40724

  1. The logs also show a Statsig bootstrap error for user.custom.workspace_type.

I am in Vietnam and this is a personal Gmail account, not an organization account.

What is the expected behavior?

Browser Use and Computer Use should either be available for this personal Plus trial account, or the app should show a specific reason why they are unavailable.

If Vietnam, Plus trial accounts, or Windows 10 are unsupported for Browser/Computer Use, the UI should say that explicitly instead of showing the generic "Disabled by your organization or unavailable in your region" message.

If this is a Statsig/bootstrap issue, the app should recover feature flags correctly after sign-in.

Additional information

Related issues that look similar:

  • #21440
  • #25253
  • #24438

This report adds a newer Codex Windows package/version:
OpenAI.Codex_26.602.4764.0_x64__2p2nqsd0c76g0

Desktop log release:
26.602.40724

OS:
Windows 10 Pro build 19045

I have already submitted in-app feedback:
019e9b04-919d-7e33-b906-42bed4475e12

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 2 months ago

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

  • #26594
  • #26536
  • #26730
  • #26692

Powered by Codex Action

erparker · 2 months ago

Same root cause on macOS (this is filed under Windows, but it's cross-platform), and the same Computer Use symptom. Two additions that may help triage:

1. Dated, deterministic regression. Scanning this Mac's Codex Desktop logs back to May 22:

  • May 22 → Jun 1: zero workspace_type bootstrap errors.
  • First occurrence: 2026-06-02 ~06:10 UTC. By Jun 4–5, 37 of 37 launches that ran the post-login Statsig bootstrap hit it — 0 succeeded.

The Codex app version did not change across that boundary (26.601.x spanned it), and workspace_type does not appear anywhere in the client bundle — it comes from the server-generated post-login Statsig bootstrap payload. So this looks like a backend change around Jun 2 that began emitting user.custom.workspace_type as a non-primitive (the invalid_union rejects string/number/boolean/array/undefined → the value is null or an object).

2. On macOS the same crash surfaces as a misleading Computer Use error. Because the thrown error aborts the entire feature bootstrap, every Statsig gate defaults off (owl-feature-bootstrap-cache.json = {"enabledOwlFeatureNames":[]}). So appshotsEnabled/computerUse are off, the managed Computer Use service never starts, and computer_use.list_apps returns:

Computer Use could not start because its runtime app is missing.

That reads like a missing/broken runtime, but it is purely downstream of this bootstrap crash. Reproduced on both a personal and an org/workspace account on the same machine, so it is not specific to workspace-type accounts.

Env: macOS 26.3.1 (25D2128) arm64, Codex App 26.602.40724, ChatGPT login.

Suggested fast mitigation (client-side): make the post-login bootstrap tolerant of a non-primitive custom value instead of throwing — e.g. a .catch(undefined) / drop-invalid on the per-value schema — so one malformed field can't abort the whole feature bootstrap. Confirmed locally that this alone stops the crash and lets the gates load again.