Codex v0.131.0 terminal corruption after codex_apps MCP startup on Windows
Resolved 💬 7 comments Opened May 19, 2026 by Pedro-Fernandes Closed May 25, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of Codex CLI is running?
v0.131.0
What subscription do you have?
Plus
Which model were you using?
gpt-5.5
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What terminal emulator and version are you using (if applicable)?
PowerShell
Codex doctor report
What issue are you seeing?
After upgrading to 0.131.0, Codex starts normally but the terminal UI becomes corrupted immediately after:
Booting MCP server: codex_apps
The terminal then fills with ANSI/control escape sequences like:
←[49m←[K←[52;27H...
The issue appears project-specific:
some repositories work normally
some repositories consistently trigger the corruption
Downgrading back to 0.130.0 fully resolves the issue.
<img width="2530" height="660" alt="Image" src="https://github.com/user-attachments/assets/3f8102c3-59c4-4cd5-8976-776c8a842d85" />
What steps can reproduce the bug?
npm install -g @openai/codex@0.131.0
cd <affected repo>
codex
What is the expected behavior?
no ANSI characters, normal text startup
Additional information
- AGENTS.md content does not appear to be the cause
- deleting .codex did not resolve it
- corruption starts specifically during MCP server startup
- issue reproduced in Windows Terminal using PowerShell
- renaming some large folders slightly delayed the corruption but did not prevent it
7 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Would you do me a favor: can you run codex on a directory that isn't a git repository, like C:\Users\Pedro in your case and see if the issue still happens?
sure! here is the output:
<img width="2535" height="596" alt="Image" src="https://github.com/user-attachments/assets/63c82ed4-5d24-4a46-a0c7-3a94ecb10384" />
PS: It is still present in v0.132.0
Thanks for the outside-Git screenshot. That narrows the shape of this: on the affected machine the raw-control-byte rendering issue does not manifest outside a Git repo, so we are treating repo-conditioned startup work as a trigger rather than claiming Git status rendering itself is the proven root cause.
I opened draft PR #23723 to harden Windows TUI output when stdout VT processing cannot be trusted and to expose Windows stdout VT visibility in
codex doctor.If you are willing, a fresh
codex doctor --jsoncaptured from a broken in-repo run on the affected machine would still help us compare the terminal details. Once a release contains the hardening change, we will ask you to retry that version as well.Sure! Here is the output:
+1, just upgraded to v0.133.0 and have the same issue. v0.130.0 was fine and didn't have UI issues
Upgrade your git version and this should be fixed. Otherwise you can wait for the next release.