Version regression; Codex Desktop bridge failure; Chrome plugin not working; Deleting .codex is not enough;

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

OpenAI.Codex_26.513.4821

What subscription do you have?

Plus

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

<img width="1114" height="448" alt="Image" src="https://github.com/user-attachments/assets/26619beb-5e2a-4e8c-a7fb-91017db846ca" />
Too many bugs!!!!!
no plugins chrome, no computer-use, error launching app when i tap the messages from the codex.

Over the past few days, your Codex issues were not caused by one single bug, but by several problems stacking on top of each other:

Codex Desktop seems unstable on Windows right now, especially the parts related to Chrome control, plugins, MCP/app-server, and “Computer Use”-style desktop automation.

The main bugs/issues you ran into were:

Version regression

The newer Codex versions, especially around 0.135.0, seem less stable than the older ones. You said rolling back helped before, and that makes sense. Some of the recent issues look like version-related regressions.

Codex Desktop bridge failure

Errors like:

MCP client for codex_apps failed to start

suggest that the bridge between Codex Desktop, Windows apps, Chrome, and plugins is broken or failing to start.

Chrome plugin not working

Codex could not properly control Chrome or continue from the expense page. This likely means the Chrome extension / plugin bridge was not correctly detected or started.

Deleting .codex is not enough

You deleted:

C:\Users\34494\.codex

but Codex still showed popups. That means Codex Desktop also stores state in other places, such as:

AppData
WindowsApps / Microsoft Store package data
plugin cache
background extension-host processes
Windows notification registration

So .codex is only part of the local state.

What steps can reproduce the bug?

1, about plugins: when using chrome or computer-use
2, about error launching error: when tapping messages from codex

What is the expected behavior?

_No response_

Additional information

_No response_