Ghostty captures Hyper key (Cmd+Shift+Ctrl+Option) and triggers crosshair cursor, interfering with tmux keybindings

[kushvinth]

Issue Description

I’m using a Hyper key setup where Caps Lock is mapped to Cmd + Shift + Ctrl + Option. This is primarily used inside tmux for custom keybindings.

Since upgrading to Ghostty 1.3.0, pressing the Hyper key inside Ghostty triggers a crosshair cursor mode. This interferes with normal terminal input and prevents tmux from reliably receiving the intended key combinations.

Additionally, if a Hyper-based keybinding causes a focus change (e.g., launching another app), Ghostty does not receive the key release event. When returning focus, the cursor remains stuck in crosshair mode until manually reset (e.g., pressing Caps Lock again or Esc).

This behavior breaks workflows where Hyper is used as a modifier layer for tmux.

Expected Behavior

• Ghostty should pass Hyper key combinations through to the terminal (tmux) without triggering internal UI behavior
• Modifier key state should not get stuck when focus changes
• No cursor mode changes should occur from modifier-only input

Actual Behavior

• Pressing Hyper key activates crosshair cursor mode
• tmux does not reliably receive Hyper-based keybindings
• Losing focus before key release causes Ghostty to miss the release event
• Cursor remains stuck in crosshair mode after refocusing
• Requires manual reset via Caps Lock or Esc

Reproduction Steps

1. Map Caps Lock → Cmd + Shift + Ctrl + Option (Hyper key)
2. Configure tmux keybindings using Hyper combinations
3. Open Ghostty and start tmux
4. Press Hyper or Hyper-based keybindings

Optional:

5. Trigger an action that changes focus while holding Hyper
6. Return to Ghostty

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

MacOS Tahoe 26.3

(Linux only) Display Server

None

(Linux only) Desktop Environment/Window Manager

No response

Minimal Ghostty Configuration

#
#       ██████╗ ██╗  ██╗ ██████╗ ███████╗████████╗████████╗██╗   ██╗
#      ██╔════╝ ██║  ██║██╔═══██╗██╔════╝╚══██╔══╝╚══██╔══╝╚██╗ ██╔╝
#      ██║  ███╗███████║██║   ██║███████╗   ██║      ██║    ╚████╔╝
#      ██║   ██║██╔══██║██║   ██║╚════██║   ██║      ██║     ╚██╔╝
#      ╚██████╔╝██║  ██║╚██████╔╝███████║   ██║      ██║      ██║
#       ╚═════╝ ╚═╝  ╚═╝ ╚═════╝ ╚══════╝   ╚═╝      ╚═╝      ╚═╝
#
#                      Ghostty Terminal Config 👻
#


## --- Window Behavior ---
background-opacity      = 0.8
theme                   = Catppuccin Mocha
confirm-close-surface   = false
macos-icon              = xray
macos-icon-frame        = chrome
mouse-hide-while-typing = true
font-family             = JetBrains Mono
macos-window-buttons = hidden
macos-option-as-alt = true

## --- Yabai-Rice Behavior ---
window-decoration = none
window-padding-x = 0
window-padding-y = 0


## --- Mouse Feat ---
cursor-style = bar

## --- Shell Integrations ---
shell-integration-features = no-cursor,sudo,no-title

## --- Quick Terminal ---
keybind = global:cmd+shift+grave_accent=toggle_quick_terminal
quick-terminal-position = bottom

## --- Shaders ---
custom-shader-animation = true
custom-shader = ~/dotfiles/.config/ghostty/kitty_cursor_trail.glsl
custom-shader = ~/.config/ghostty/ghostty-shaders/underwater.glsl
custom-shader = ~/.config/ghostty/ghostty-shaders/bloom.glsl
custom-shader = ~/.config/ghostty/ghostty-shaders/glitchy.glsl

## --- Testing ---
#macos-titlebar-style = hidden
keybind = alt+left=unbind
keybind = alt+right=unbind

Additional Relevant Configuration

• tmux used for keybinding layer
• Hyper key: Caps Lock → Cmd + Shift + Ctrl + Option from karabiner

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.