←[?2026h (XTWINOPS in-band resize) breaks TUI in Visual Studio Developer PowerShell since 0.131

Open 💬 1 comment Opened May 26, 2026 by mhmdali19

Version: codex-cli 0.131.0+ (confirmed broken on 0.131, 0.132, 0.133)
Working version: 0.130.0
Platform: Windows, Visual Studio Developer PowerShell (VsDevCmd.bat)

Description:
After upgrading from 0.130.0 to 0.131+, the interactive TUI renders raw ANSI
escape sequences instead of formatted output, making Codex completely unusable.

The corruption starts exactly when "Booting MCP server: codex_apps" runs during
startup, triggered by the ←[?2026h escape sequence being sent to a console
that doesn't support XTWINOPS in-band resize notification.

The console receives ←[?2026h but returns no confirmation, causing Codex to
lose terminal sync and spill all subsequent escape codes as raw text.

Steps to reproduce:

  1. Open Visual Studio Developer PowerShell (via VsDevCmd.bat)
  2. Run codex.cmd in any Git repository
  3. Observe raw escape sequences flooding the screen during MCP server boot

What was tried (none worked):

  • TERM=dumb
  • TERM=xterm-256color
  • NO_COLOR=1
  • --no-alt-screen flag
  • HKCU registry VirtualTerminalLevel=1
  • Clearing .codex sessions and history

Expected: Graceful fallback when terminal doesn't respond to ←[?2026h
Actual: TUI completely broken, unusable

Workaround: Downgrade to @openai/codex@0.130.0

View original on GitHub ↗

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