›_ Codex Issues
Codex Issues / #32876

Codex extension connected to Chrome, but control fails with Windows Sandbox error

Open 💬 4 comments Opened Jul 13, 2026 by alexandrrecardoso-sys
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

A extensão oficial Codex no Chrome está ativa e mostra “Connected”, mas o Codex não consegue controlar o navegador.

Erro apresentado:
windows sandbox failed: helper_unknown_error: setup refresh had errors

Já foram realizados:

  • Reinicialização do Chrome e do Codex;
  • Reinstalação da extensão;
  • Remoção e nova instalação do plugin Chrome no Codex;
  • Confirmação de que a extensão está ativa e conectada.

O erro ocorre antes de o Codex alcançar o Chrome.

View original on GitHub ↗

4 Comments

github-actions[bot] contributor · 1 month ago

English translation:

The official Codex extension for Chrome is active and shows “Connected,” but Codex is unable to control the browser.

Error displayed:
windows sandbox failed: helper_unknown_error: setup refresh had errors

The following have already been attempted:

  • Restarting Chrome and Codex;
  • Reinstalling the extension;
  • Removing and reinstalling the Chrome plugin in Codex;
  • Confirming that the extension is active and connected.

The error occurs before Codex can reach Chrome.

<!-- codex-issue-translator -->

github-actions[bot] contributor · 1 month ago

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

  • #32487
  • #31848
  • #32855

Powered by Codex Action

Eziotrix · 1 month ago

Additional reproduction and diagnostics from another Windows Codex Desktop installation:

  • Codex app build observed: 26.715.72359
  • Chrome is installed and running.
  • The Codex Chrome extension/native bridge is installed and registered.
  • Native host manifest exists at:

C:\Users\Sai Chaitanya\AppData\Local\OpenAI\extension\com.openai.codexextension.json

  • Native host name: com.openai.codexextension
  • Chrome extension ID: hehggadaopoacecdllhhajmbjkdcmajg
  • The registered extension-host.exe exists and was observed running.
  • Codex bridge paths under .codex\plugins\cache\openai-bundled\chrome\latest exist.
  • Codex executables are digitally signed by OpenAI.
  • No Zone.Identifier block was present on the Codex executables.
  • Defender detection history did not show a Codex executable detection.
  • Restarting Codex, reinstalling Codex, restarting Chrome, and running Codex as administrator did not resolve the issue.

Observed failure when initializing Chrome control, before tabs can be listed:

node_repl kernel exited unexpectedly

windows sandbox failed: helper_unknown_error: setup refresh had errors

This appears to fail in the shared Codex Windows sandbox/node_repl startup layer before the Chrome native messaging bridge is reached. The Chrome extension itself appears installed and connected.

Eziotrix · 1 month ago

Workaround discovered

Changing the Codex configuration from elevated to unelevated sandbox mode fixed Chrome control on Windows:

[windows]
sandbox = "unelevated"

Before this change, Chrome control failed before connecting with:

windows sandbox failed: helper_unknown_error: setup refresh had errors

After changing the setting, Codex successfully initialized the Chrome extension and listed the open Chrome tabs.

Could the maintainers clarify the consequences of using windows.sandbox = "unelevated"?

Specifically:

  • What security protections or isolation are reduced?
  • Does Codex still restrict file and process access to the configured workspace?
  • Which tasks may stop working because they require elevated permissions?
  • Is unelevated mode the recommended workaround for this Chrome-control failure, or should users wait for a proper fix?