[Windows] Chrome/Browser Use disabled with statsig-disabled and workspace_type null on 26.609

Resolved 💬 2 comments Opened Jun 12, 2026 by clifftsou68 Closed Jun 12, 2026
💡 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?

Windows Store package: OpenAI.Codex_26.609.3341.0_x64__2p2nqsd0c76g0

Desktop release shown in logs: 26.609.30741

What subscription do you have?

Personal ChatGPT account. The account has US billing/payment, but the user is currently located in Vietnam.

What platform is your computer?

Microsoft Windows 11 Home x64

OS version: 10.0.26200

Build: 26200

What issue are you seeing?

In Codex Desktop Settings > Computer use, Google Chrome is disabled and shows:

Disabled by your organization or unavailable in your region

Chrome/Browser Use also does not show up as an available usable plugin/tool in the app, even though the installed Windows package and local bundled plugin cache contain the plugin files.

This appears to be the same family of issue as:

Local diagnostics

The installed app bundle contains the bundled plugins:

C:\Program Files\WindowsApps\OpenAI.Codex_26.609.3341.0_x64__2p2nqsd0c76g0\app\resources\plugins\openai-bundled\plugins

browser
chrome
computer-use
latex
sites

The repaired local plugin cache also contains:

C:\Users\cliff\.codex\plugins\cache\openai-bundled\plugins

browser
chrome
computer-use
latex
sites

But after Codex Desktop startup, the active generated bundled marketplace only exposes:

C:\Users\cliff\.codex\.tmp\bundled-marketplaces\openai-bundled\plugins

computer-use
latex

There is no local machine policy file disabling this:

C:\ProgramData\OpenAI\Codex\requirements.toml     missing
C:\ProgramData\OpenAI\Codex\managed_config.toml  missing

The user config enables the relevant features/plugins:

[plugins."computer-use@openai-bundled"]
enabled = true

[plugins."chrome@openai-bundled"]
enabled = true

[plugins."browser@openai-bundled"]
enabled = true

[features]
browser_use = true
in_app_browser = true
computer_use = true
js_repl = true

The Windows Computer Use native pipe starts successfully:

computer-use native pipe startup ready pipePath=\\.\pipe\codex-computer-use-ec2c804e-2d3d-41f6-9ee4-199f6d7ebff8 platform=win32

But feature bootstrap then fails:

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

And Browser/Chrome availability resolves disabled:

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

Troubleshooting already tried

  • Set CODEX_ELECTRON_ENABLE_WINDOWS_COMPUTER_USE=1 in the user environment.
  • Rebuilt/repaired the local openai-bundled plugin cache.
  • Enabled browser@openai-bundled, chrome@openai-bundled, and computer-use@openai-bundled in C:\Users\cliff\.codex\config.toml.
  • Enabled browser_use, in_app_browser, computer_use, and js_repl in config.toml.
  • Confirmed there is no %ProgramData%\OpenAI\Codex\requirements.toml disabling these features.
  • Confirmed the installed package contains the Browser/Chrome/Computer Use plugin files.
  • Confirmed native Windows Computer Use can start, but Chrome/browser control remains blocked because the Browser Use gate resolves statsig-disabled.

Expected behavior

Chrome/Browser Use should either be available for this account/platform, or the app should show a precise reason why it is unavailable.

If Vietnam/current physical location, account workspace data, or a rollout gate makes this account ineligible, the UI should say that explicitly instead of only showing the generic organization/region message.

Actual behavior

The app shows Chrome disabled in Settings > Computer use and does not expose Chrome/Browser Use, despite local plugin files being present and enabled in config. Logs indicate user.custom.workspace_type is null or otherwise invalid for Statsig bootstrap, followed by reason=statsig-disabled.

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.

  • ##26735
  • ##26780
  • ##27635
  • ##26744
  • ##26594

Powered by Codex Action

clifftsou68 · 2 months ago

Duplicate/closed-issue review after the bot suggestions:

  • Closest duplicate: #26735. It has the same core symptoms: Windows, personal account, Vietnam, Browser/Computer Use disabled, Statsig bootstrap failure on user.custom.workspace_type, and browser_use_availability_resolved ... reason=statsig-disabled.
  • Same root-cause family: #26780. It tracks the same workspace_type bootstrap failure and Browser/Chrome availability fallout, with additional i18n symptoms.
  • Related but not exact: #27635, #26744, and #26594.
  • Checked related closed candidates: #25878 and #26437 are closed, but neither contains a confirmed fix for this workspace_type / statsig-disabled Chrome/Browser Use case.

Local checks on this machine also ruled out the known local-only workarounds from related comments:

  • CODEX_ELECTRON_ENABLE_WINDOWS_COMPUTER_USE=1 is already set.
  • [windows] sandbox = "unelevated" is already set.
  • ComSpec is valid: C:\Windows\system32\cmd.exe.
  • The persistent bundled plugin cache contains browser, chrome, computer-use, latex, and sites.
  • The active runtime marketplace is still pruned to computer-use and latex after startup.
  • Current logs still show browser_use_availability_resolved available=false ... reason=statsig-disabled.

Closing this as a duplicate of #26735, while leaving the 26.609 / Windows 11 build 26200 evidence here for maintainers.