Bug: Codex Desktop inherits Chrome `DynamicCodeSettings` (ACG) policy

Open 💬 1 comment Opened Jun 5, 2026 by gembleman

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

26.602.30954

What subscription do you have?

Business

What platform is your computer?

Microsoft Windows NT 10.0.19045.0 x64

What issue are you seeing?

Summary

On Windows, setting Chrome policy DynamicCodeSettings=1 enables Arbitrary Code
Guard (ACG) for Chrome's browser process. Codex Desktop appears to read or
inherit this Chrome policy from SOFTWARE\Policies\Google\Chrome, then fails to
start.

This looks like a Codex-side bug. Codex should not inherit policies configured for the user's installed Chrome browser.
If Codex intentionally uses a Chrome-agent/browser integration, that
integration should be disabled or isolated from Chrome policy state.

Environment

  • Chrome policy: DynamicCodeSettings=1
  • Source config: enable-dynamic-code-restriction

Notes

  • Bisection showed DynamicCodeSettings=1 is the sole culprit.
  • HKCU vs HKLM does not change the result.
  • Obsidian, also Electron, still launches. This does not appear to be a generic

Electron issue.

What steps can reproduce the bug?

  1. Apply a Chrome policy reg file containing:

"DynamicCodeSettings"=dword:00000001

  1. Fully quit and relaunch Codex Desktop.

What is the expected behavior?

Expected: Codex launches normally.
Actual: Codex fails to start.

Additional information

RKNF404/chromium-hardening-guide#72

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗