Strange behavior on zsh via ssh

[wiegell]

Issue Description

When using ghostty to connect to a server via ssh with zsh as a shell i see some strange behavior,
e.g. when pressing backspace the cursor moves forwards. This does not happen if i change the remote shell to bash.
It sound alot like #7208
However i can also trigger the reversed cursor on backspace after wiping .zshrc, so there should be absolutely no plugins.
Zsh auto-suggestions is also jumping around all over the line when enabled.

Expected Behavior

Normal behavior like when not run via ssh

Actual Behavior

Here i press space consecutively multiple times followed by multiple backspaces
output.webm

Reproduction Steps

1. connect to an ssh server with zsh
2. see the behavior above

Ghostty Logs

➜  ~ ghostty
info: ghostty version=1.2.3
info: ghostty build optimize=ReleaseFast
info: runtime=apprt.Runtime.gtk
info: font_backend=font.main.Backend.fontconfig_freetype
info: dependency harfbuzz=11.0.0
info: dependency fontconfig=21402
info: renderer=renderer.generic.Renderer(renderer.OpenGL)
info: libxev default backend=io_uring
info(os_locale): setlocale after unset lang result=C
warning(os_locale): setlocale failed with LANG and system default. Falling back to en_US.UTF-8
warning(os_locale): setlocale failed even with the fallback, uncertain results
info(gtk): GTK version build=4.18.6 runtime=4.18.6
info(gtk): libadwaita version build=1.7.6 runtime=1.7.6
info: reading configuration file path=/home/<USER_REDACTED>/.config/ghostty/config
info(config): default shell src=passwd value=/usr/bin/zsh
info(config): default working directory src=passwd value=/home/<USER_REDACTED>
warning(gtk_ghostty_application): setting GDK_DEBUG=
warning(gtk_ghostty_application): setting GDK_DISABLE=gles-api,vulkan

(process:13079): Gtk-WARNING **: 14:08:51.330: Unknown key gtk-modules in /home/<USER_REDACTED>/.config/gtk-4.0/settings.ini

(process:13079): Adwaita-WARNING **: 14:08:51.412: Using GtkSettings:gtk-application-prefer-dark-theme with libadwaita is unsupported. Please use AdwStyleManager:color-scheme instead.
info(gtk_systemd_cgroup): transient scope created cgroup=/user.slice/user-1000.slice/[email protected]/app.slice/app-ghostty-transient-13079.scope
info(gtk_ghostty_application): cgroup isolation enabled base=/user.slice/user-1000.slice/[email protected]/app.slice/app-ghostty-transient-13079.scope
info(opengl): loaded OpenGL 4.6
info(io_exec): found Ghostty resources dir: /usr/share/ghostty
info(io_exec): shell integration automatically injected shell=termio.shell_integration.Shell.zsh
warning(gtk_ghostty_application): unimplemented action=apprt.action.Action.Key.cell_size
info(io_exec): started subcommand path=/bin/sh pid=13108
info(io_exec): subcommand cgroup=/user.slice/user-1000.slice/[email protected]/app.slice/app-ghostty-transient-13079.scope/surfaces/55C0F7FDC3D0.scope
info(stream): OSC 1 (change icon) received and ignored icon=~
warning(stream): unimplemented OSC command: change_window_icon
warning(io_handler): OSC 7 uri must contain a hostname: error.NoHostnameInUri
info(stream): OSC 1 (change icon) received and ignored [email protected]
warning(stream): unimplemented OSC command: change_window_icon

Ghostty Version

➜  ~ ghostty --version
Ghostty 1.2.3

Version
  - version: 1.2.3
  - channel: stable
Build Config
  - Zig version   : 0.14.1
  - build mode    : builtin.OptimizeMode.ReleaseFast
  - app runtime   : apprt.Runtime.gtk
  - font engine   : font.main.Backend.fontconfig_freetype
  - renderer      : renderer.generic.Renderer(renderer.OpenGL)
  - libxev        : io_uring
  - kernel version: 6.12.57+deb13-amd64
  - desktop env   : other
  - GTK version   :
    build         : 4.18.6
    runtime       : 4.18.6
  - libadwaita    : enabled
    build         : 1.7.6
    runtime       : 1.7.6
  - libX11        : enabled
  - libwayland    : enabled

OS Version Information

Linux <HOST_REDACTED> 6.12.57+deb13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.57-1 (2025-11-05) x86_64 GNU/Linux

(Linux only) Display Server

Wayland

(Linux only) Desktop Environment/Window Manager

Plasma 6.3.6

Minimal Ghostty Configuration

➜  ghostty cat config
# This is the configuration file for Ghostty.
#
# This template file has been automatically created at the following
# path since Ghostty couldn't find any existing config files on your system:
#
#   /home/bjoern/.config/ghostty/config
#
# The template does not set any default options, since Ghostty ships
# with sensible defaults for all options. Users should only need to set
# options that they want to change from the default.
#
# Run `ghostty +show-config --default --docs` to view a list of
# all available config options and their default values.
#
# Additionally, each config option is also explained in detail
# on Ghostty's website, at https://ghostty.org/docs/config.
#
# Ghostty can reload the configuration while running by using the menu
# options or the bound key (default: Command + Shift + comma on macOS and
# Control + Shift + comma on other platforms). Not all config options can be
# reloaded while running; some only apply to new windows and others may require
# a full restart to take effect.

# Config syntax crash course
# ==========================
# # The config file consists of simple key-value pairs,
# # separated by equals signs.
# font-family = Iosevka
# window-padding-x = 2
#
# # Spacing around the equals sign does not matter.
# # All of these are identical:
# key=value
# key= value
# key =value
# key = value
#
# # Any line beginning with a # is a comment. It's not possible to put
# # a comment after a config option, since it would be interpreted as a
# # part of the value. For example, this will have a value of "#123abc":
# background = #123abc
#
# # Empty values are used to reset config keys to default.
# key =
#
# # Some config options have unique syntaxes for their value,
# # which is explained in the docs for that config option.
# # Just for example:
# resize-overlay-duration = 4s 200ms
keybind = shift+super+d=new_split:down
keybind = super+t=new_tab
keybind = super+c=copy_to_clipboard
keybind = super+v=paste_from_clipboard%

Additional Relevant Configuration

Should have correct terminfo on this ncurses version, right?

➜  ghostty apt list | grep ncurses

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

fizmo-ncursesw/stable 0.7.14-2+b2 amd64
gambas3-gb-ncurses/stable 3.20.2-1 amd64
lib32ncurses-dev/stable 6.5+20250216-2 amd64
lib32ncurses6/stable 6.5+20250216-2 amd64
lib32ncursesw6/stable 6.5+20250216-2 amd64
libcunit1-ncurses-dev/stable 2.1-3-dfsg-2.7+b1 amd64
libcunit1-ncurses/stable 2.1-3-dfsg-2.7+b1 amd64
libncurses-dev/stable 6.5+20250216-2 amd64
libncurses6/stable,now 6.5+20250216-2 amd64 [installed,automatic]
libncursesada-dev/stable 6.3.20211021-13 amd64
libncursesada6.2.4/stable 6.3.20211021-13 amd64
libncursesw6/stable,now 6.5+20250216-2 amd64 [installed]
ncurses-base/stable,now 6.5+20250216-2 all [installed]
ncurses-bin/stable,now 6.5+20250216-2 amd64 [installed]
ncurses-doc/stable 6.5+20250216-2 all
ncurses-examples/stable 6.5+20250216-2 amd64
ncurses-hexedit/stable 0.9.7+orig-7.3 amd64
ncurses-term/stable 6.5+20250216-2 all
ruby-ncurses/stable 1.4.11-1+b2 amd64
vfu-ncurses/stable 5.09-3 amd64
wordgrinder-ncurses/stable 0.8-1+b1 amd64

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.

[danielwe]

Almost certainly a terminfo issue, see https://ghostty.org/docs/help/terminfo#ssh.

TL;DR: Try adding shell-integration-features = ssh-terminfo,ssh-env to your Ghostty config and see if anything changes.

I'm guessing your remote .bashrc includes a hardcoded export TERM=xterm-256color or similar, which would explain why the problem does not appear with bash as the remote shell.

[danielwe]

Should have correct terminfo on this ncurses version, right?

Re this part: The updated ncurses only supports TERM=ghostty, not TERM=xterm-ghostty, so sadly it doesn't fix the problem unless you set term = ghostty in your Ghostty config.

The ncurses maintainer (who is also the xterm maintainer) wouldn't accept the xterm prefix in ncurses. But many programs and distro-provided shell configurations require TERM=xterm-* to enable basic functionality. So, here we are...