codex - 💡(How to fix) Fix Windows Codex Desktop 26.506.31421: config saves fail and Chrome plugin state/capability is broken [1 participants]

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

26.506.31421

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Microsoft Windows NT 10.0.26200.8457 x64

What issue are you seeing?

Windows 11, Codex Desktop 26.506.31421.

Problems:

1. Settings -> Configuration cannot save changes: Unable to save.
2. config.toml is writable manually from PowerShell. ACLs are fine.
3. Workspace Dependencies diagnose as healthy.
4. Chrome plugin cannot be uninstalled from Codex app: Failed to uninstall plugin.
5. Chrome/plugin capability is not exposed in new Codex sessions.
6. JS REPL works.
7. In-app browser/browser use works.
8. Shell can launch chrome.exe and read the window title, but this is not the Chrome plugin.

Likely broken layer: Desktop app config/plugin state management, not filesystem permissions or workspace dependencies.

What steps can reproduce the bug?

Observed on Windows 11 with Codex Desktop 26.506.31421.

1. Open Codex Desktop Settings -> Configuration.
2. Try to save a settings/configuration change.
3. Observe the UI error: Unable to save.
4. From PowerShell, manually edit or write $CODEX_HOME/config.toml.
5. Observe that the file is writable manually, so this does not appear to be a basic filesystem permission or ACL problem.
6. Run Workspace Dependencies diagnostics.
7. Observe that Workspace Dependencies diagnose as healthy.
8. Open the Codex app plugin UI and try to uninstall the bundled Chrome plugin.
9. Observe the UI error: Failed to uninstall plugin.
10. Start a new Codex session and request @chrome / Chrome plugin capability.
11. Observe that the Chrome/plugin capability is not exposed in the new session.
12. In the same environment, verify that JS REPL works.
13. Verify that the in-app browser / browser-use capability works.
14. As a control, use shell/PowerShell to launch chrome.exe and read the Chrome window title. This succeeds, but it is OS shell automation, not the Codex Chrome plugin.

What is the expected behavior?

• Settings -> Configuration should save changes successfully when config.toml is writable.
• If a config write fails, the UI should surface the concrete app-server/config error instead of only Unable to save.
• The Chrome plugin uninstall action should either uninstall successfully or clearly explain why it cannot.
• If the Chrome plugin is installed/enabled, new Codex sessions should expose the Chrome plugin capability.
• Workspace Dependencies health should not be implicated when diagnostics report healthy and JS REPL/browser-use are working.

Additional information

This looks related to existing Windows Desktop config/plugin state issues, but this report combines both failure modes on the same current Desktop build:

• Settings/config saves fail even though config.toml is manually writable.
• Plugin state management also fails: Chrome plugin uninstall fails and Chrome capability is not exposed in new sessions.
• Other runtime layers appear healthy: Workspace Dependencies, JS REPL, in-app browser/browser-use, and shell process launch all work.

Possibly related open issues:

• #20538
• #20856
• #21670
• #22114
• #22462