Mouse tracking mode not reset after SSH session dies with broken pipe

[Gandalf-Le-Dev]

Issue Description

When an SSH session terminates abruptly (broken pipe / remote host closes connection), Ghostty leaves mouse tracking mode enabled. Subsequent cursor movement emits raw coordinate escape sequences to the shell instead of being suppressed.

Expected Behavior

Mouse tracking mode is reset to disabled after the SSH session ends. No escape sequences emitted on cursor move.

Actual Behavior

Raw mouse tracking sequences appear in the terminal:

35;153;73M35;154;72M35;155;71M35;158;69M35;159;68M...

These are \e[?1003h (any-event mouse tracking) coordinates leaking because the remote process never sent the disable sequence (\e[?1003l) before disconnect.

Reproduction Steps

1. Open Ghostty terminal
2. SSH into a remote host running an interactive TUI or any process that enables mouse reporting (\e[?1003h or similar)
3. Let the SSH connection drop abruptly (broken pipe, network drop, remote host closes)
4. Move the cursor in the now-local terminal

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 Version 26.2 (25C56)

(Linux only) Display Server

None

(Linux only) Desktop Environment/Window Manager

No response

Minimal Ghostty Configuration

theme = Catppuccin Frappe
font-family = Maple Mono NF
font-size = 14
font-feature = +cv02
command = /bin/zsh --login --interactive

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.

[00-kat]

The program is responsible for turning off mouse tracking mode, Ghostty has no way of knowing when to do it. Since the ssh connection was abruptly dropped, the program never got a chance to turn it off, so it wasn't turned off; the only real solution here would be for ssh to reset a bunch of terminal state on exit¹. Run reset (or press Reset in the context menu).

Footnotes

1. Or your shell, when it reaches a prompt; a few like fish do indeed do this. ↩