Cursor jumps between UI regions in third-party terminals (Tabby, Wave)

What version of Codex CLI are you using?

codex-cli 0.120.0

What subscription do you have?

free

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64 (Windows 11)

What terminal emulator and version are you using?

• Tabby (latest)
• Wave Terminal (latest)
• Windows Terminal (for comparison)
• Warp (for comparison)
• System default cmd.exe and pwsh

What issue are you seeing?

When running Codex CLI in certain third-party terminals (Tabby, Wave), the cursor rapidly jumps between multiple UI regions:

1. The Working (XXs · esc to interrupt) status line
2. The > input command line
3. The model info line (e.g., gpt-5.4 high · ~)

This makes it difficult to see where the actual input cursor is and is visually distracting.

What steps can reproduce the bug?

1. Open Tabby or Wave terminal
2. Run codex
3. Send a prompt and wait for the model to process
4. Observe the cursor jumping between the status line, input line, and bottom info bar

Expected behavior

The cursor should remain at the input field, as it does in stock Windows terminals, Windows Terminal, and Warp.

Additional information

| Terminal | Shell | Behavior |
|----------|-------|----------|
| System default terminal | cmd/pwsh | ✅ Normal |
| Windows Terminal | cmd/pwsh | ✅ Normal |
| Warp | cmd/pwsh | ✅ Normal |
| Tabby | cmd | ❌ Cursor jumps |
| Tabby | pwsh | ❌ Cursor jumps |
| Wave | cmd | ❌ Cursor jumps |
| Wave | pwsh | ❌ Cursor jumps |

The issue occurs in Tabby and Wave regardless of shell (cmd or pwsh). System default terminal, Windows Terminal, and Warp all work correctly. This suggests the problem is related to how Codex's TUI handles ANSI escape sequences for cursor positioning in specific terminal emulators.

This appears related to #16687 but this report adds more terminal coverage, notably that Warp works correctly while Tabby and Wave do not.