Appearance
Kitty click events
Kitty's click_events extension enhances the keyboard protocol to report mouse click events through the same CSI u encoding used for keyboard events. When enabled (via the kitty keyboard protocol flags), the terminal sends mouse click coordinates and button state as enhanced key events rather than traditional X10/SGR mouse escape sequences.
This unifies keyboard and mouse input into a single protocol, simplifying input parsing for applications that already use the kitty keyboard protocol. Adopted by Ghostty in version 1.3.0 (the first terminal besides Kitty to support it).
How this is testedpartial
Enable kitty keyboard protocol with click_events flag, perform a click, verify the response uses CSI u encoding with mouse event data.
Enable kitty keyboard protocol with click_events flag, perform a click, verify the response uses CSI u encoding with mouse event data.
The same probe runs against headless backends (via Termless) and real terminal apps (via a daemon launched in each terminal). This lets us distinguish parser correctness from rendering correctness.
Supported by 0 of 14 backends (0%)
Terminal Applications
| Terminal | Version | Support | Notes |
|---|---|---|---|
| iTerm2 | 3.6.9 | ? unknown | |
| Ghostty | 1.3.1 | ? unknown | |
| VS Code | ? unknown | ||
| Kitty | 0.46.2 | ? unknown | |
| Warp | ? unknown | ||
| Cursor | ? unknown | ||
| Terminal.app | ? unknown |