Kitty keyboard protocol enabled even if not requested by the application

[jjjordan]

Issue Description

When using Ghostty locally on my Mac and starting the JOE text editor, pressing some sequences such as Ctrl-M and Ctrl-I generate Kitty Keyboard Protocol sequences despite the application not subscribing to such events. I have tried to eliminate other things that may be setting this flag in the terminal session (ohmyzsh) but even with an absolute bare-bones setup, these sequences are still generated.

This interferes with common command sequences (^K ^I, ^K ^M etc). Other control keys, as far as I can tell, are unaffected.

Expected Behavior

Pressing ^I is a synonym for tab, ^M is a synonym for enter. ^K ^I should do some window manipulation and ^K ^M is the move block command. This works on the same set up with iTerm and iTerm2.

Actual Behavior

Typing these keys inserts partial kitty keyboard protocol sequences into the document instead, e.g. 9;5u (the prefix of this may be recognized as something else). When using quote mode (invoked by ^Q) and then pressing ^I or ^M, you will see the whole sequence inserted e.g. [[105;5u.

Reproduction Steps

Open Ghostty with default config on a Mac.
Run JOE and press Control-I

Ghostty Logs

No response

Ghostty Version

Ghostty 1.3.0

Version
  - version: 1.3.0
  - channel: stable
Build Config
  - Zig version   : 0.15.2
  - build mode    : .ReleaseFast
  - app runtime   : .none
  - font engine   : .coretext
  - renderer      : renderer.generic.Renderer(renderer.Metal)
  - libxev        : kqueue

OS Version Information

Sequoia 15.7.4 (24G517)

(Linux only) Display Server

None

(Linux only) Desktop Environment/Window Manager

No response

Minimal Ghostty Configuration

(Any config seems to do)

Additional Relevant Configuration

This happens on all versions from at least 3.8 through current main. You can install this from brew.

I acknowledge that:

• I have reviewed the FAQ and confirm that my issue is NOT among them.
• I have searched the Ghostty repository (both open and closed Discussions and Issues) and confirm this is not a duplicate of an existing issue or discussion.
• I have checked the "Preview" tab on all text fields to ensure that everything looks right, and have wrapped all configuration and code in code blocks with a group of three backticks (```) on separate lines.

[mitchellh]

I think that's just CSIu, which is our default legacy encoding mechanism: https://www.leonerd.org.uk/hacks/fixterms/

[jjjordan]

My mistake - this is indeed the encoding.

I can add them, but I'd ask what other input sequences will be encoded in such a way that differ from xterm (or konsole/the usual suspects) so I'm not surprised later? I will note to my knowledge we've never had a report about these sequences missing from the keymap from other terminals.

[mitchellh]

It's only CSIu.