scroll-to-bottom=keystroke should not be triggered by key release events

[atuooo]

Issue Description

When an application has enabled the Kitty keyboard protocol with the "report event types" flag (release reporting), quickly pressing and releasing the copy shortcut (Cmd+C) unexpectedly scrolls the viewport to the bottom.

This is caused by the key release ordering: Cmd is usually released before C, so the C release arrives with no modifiers. With Kitty keyboard release reporting enabled, this release is sent to the PTY, where scroll-to-bottom=keystroke treats it as a keystroke and scrolls to the bottom.

Expected Behavior

A key release event should not trigger scroll-to-bottom=keystroke. Only press and repeat events represent new user input and should cause an auto-scroll. Pressing and releasing Cmd+C (or any key) should not move the viewport to the bottom.

Actual Behavior

When the Kitty keyboard protocol's release reporting is active, releasing the C key of a Cmd+C shortcut (with Cmd released first) scrolls the viewport to the bottom, even though no new input was produced.

Reproduction Steps

1. Keep the default scroll-to-bottom = keystroke.
2. Make the terminal report key release events via the Kitty keyboard protocol. Use kimi-code or pi-coding-agent or try printf '\e[>2u'; cat -v.
3. Scroll up into the scrollback so you are not at the bottom.
4. Quickly press and release Cmd+C, releasing Cmd slightly before C.
5. Observe that the viewport jumps to the bottom on the C release.

Ghostty Logs

No response

Ghostty Version

Ghostty 1.3.1

Version
  - version: 1.3.1
  - 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

macOS 26.0.1 (25A362)

(Linux only) Display Server

None

(Linux only) Desktop Environment/Window Manager

No response

Minimal Ghostty Configuration

default configuration

Additional Relevant Configuration

No response

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.

[Ragnoroct]

I am having the same exact problem but on linux/gtk and with my ctrl+shift+c keybind. It is very annoying because when going to copy codex text up in the scroll buffer it brings my back again every time if c is not the first key up.

Adding onto this issue since I spent some time reproducing it with a video and screenshot of my keyboard inputs on main commit 73534c4

disclosure: I used codex to debug, build ghostty on main, and get clean recordings/screenshots. All text above was written and edited by me only.

ghostty-key-release-20260720-140213.webm