codex - 💡(How to fix) Fix Cursor jumps between UI regions in third-party terminals (Tabby, Wave) [1 comments, 2 participants]

TL;DR

The issue can likely be mitigated by adjusting how Codex CLI handles ANSI escape sequences for cursor positioning in specific terminal emulators like Tabby and Wave.

Guidance

• Investigate the differences in how Tabby and Wave terminals handle ANSI escape sequences compared to Windows Terminal and Warp, which work correctly.
• Review the Codex CLI code for any terminal-specific handling of cursor positioning to identify potential inconsistencies.
• Consider testing with other terminals to further isolate the issue and determine if it's specific to certain terminal emulators or a broader issue with Codex CLI's handling of ANSI escape sequences.
• Look into the possibility of using a library or utility that normalizes ANSI escape sequence handling across different terminals to simplify the Codex CLI codebase.

Example

No specific code example can be provided without access to the Codex CLI source code, but investigating the use of a terminal-agnostic library for handling ANSI escape sequences could be beneficial.

Notes

The issue seems to be related to how specific terminals (Tabby and Wave) handle ANSI escape sequences, which suggests that a solution might involve either adjusting Codex CLI to better handle these sequences in a terminal-agnostic way or working with the terminal emulators to correct their handling of these sequences.

Recommendation

Apply a workaround by potentially using a different terminal emulator that is known to work correctly with Codex CLI, such as Windows Terminal or Warp, until a more permanent fix can be implemented in Codex CLI to handle ANSI escape sequences more robustly across various terminals.