Support modern keyboard protocols (Kitty / CSI u) for AI & TUI compatibility

Hello,

1. The AI Era and Terminal Limitations

In recent years, the software development landscape has fundamentally shifted towards Artificial Intelligence. Developers now heavily rely on advanced AI-driven CLI assistants (such as Antigravity CLI, Aider, Fabric, and AI-enabled Neovim setups). These tools are built on modern TUI (Text User Interface) frameworks which require rich keyboard interaction.

To work efficiently with AI, users need complex, multi-modifier keybindings. A critical example is Ctrl+Enter, which has become the universal standard for submitting a multiline prompt to an AI assistant. Other essential combinations include Ctrl+Backspace and Ctrl+Delete for rapid text manipulation, and Shift+Enter for inserting new lines without submitting. However, xfce4-terminal completely fails to distinguish many of these combinations (e.g., treating Enter and Ctrl+Enter identically, or mishandling Ctrl+Backspace). This severely impedes the workflow of developers using AI, turning what should be a seamless interaction into a frustrating experience of broken hotkeys and rogue escape sequences.

2. Real-world Examples and User Complaints

The internet is filled with complaints from developers who are forced to abandon xfce4-terminal specifically due to these limitations:

  • Cannot submit AI prompts: Users of CLI AI chat tools constantly report that Ctrl+Enter does not work in XFCE terminal, forcing them to use awkward workarounds (like pressing Esc then Enter) just to send a message.
  • Broken text editing (Ctrl+Backspace / Ctrl+Delete): When editing long AI prompts, users expect Ctrl+Backspace to delete the previous word and Ctrl+Delete to delete the next word. In xfce4-terminal, these either act as a regular single-character backspace/delete, or send incompatible control characters (like ^H or ^?) that modern TUIs misinterpret.
  • Rogue characters on screen: When modern editors attempt to enable advanced key support (like modifyOtherKeys for AI plugins), xfce4-terminal outputs garbage characters like ^[>4;2m instead of recognizing the keys.
  • Forced migration: Numerous forum threads on Reddit and GitHub issues end with the same conclusion: "If you want to use modern AI TUI tools, drop xfce4-terminal and use Kitty, WezTerm, or Alacritty."

3. The Root Cause: libvte is an Unfortunate Choice

The core of this problem lies in the terminal's reliance on the libvte library. In the context of modern terminal requirements, libvte has proven to be a highly unfortunate choice. It stubbornly lags behind in supporting modern keyboard standards, specifically the Kitty Keyboard Protocol and comprehensive CSI u / modifyOtherKeys support.

Because libvte refuses to disambiguate identical legacy byte sequences (sending \r for both Enter and Ctrl+Enter, and failing to provide unique unambiguous sequences for modified Backspace/Delete), xfce4-terminal mathematically cannot pass the correct inputs to AI applications.

4. Proposed Solution

To ensure xfce4-terminal remains relevant in the era of AI-assisted development, we strongly urge the XFCE team to reconsider its rendering core architecture.

  1. Change the core: Consider migrating away from libvte to a modern, GPU-accelerated backend that natively supports the Kitty Keyboard Protocol and CSI u (similar to the engines powering WezTerm, Alacritty, or Ghostty).
  2. Push upstream: If replacing the core is impossible, the XFCE team must aggressively push upstream patches to libvte to implement modern key disambiguation, or implement an internal translation layer within xfce4-terminal.

Without these changes, xfce4-terminal acts as a bottleneck for professional developers working with Artificial Intelligence.

We, as your big user community, sincerely hope for a prompt resolution to this unfortunate issue. Thank you for your hard work!

Best regards, Tamila