Cannot use "Enter" in Ghostty [Fedora Linux]

[kevinnkansah]

Describe the bug

I cannot use enter key when trying to trust a folder, in Ghostty. Is find for other terminals

Affected version

0.0.354 Commit: 076bd172b

Steps to reproduce the behavior

Pressing Enter Key

Expected behavior

Should work

Additional context

• SYSTEM INFORMATION
HOST - Aspire A315-58 (Acer)
COMPUTER TYPE - Notebook (V1.31)
CPU - 11th Gen Intel(R) Core(TM) i5-1135G7 (8) @ 4.20 GHz
GPU - Intel Iris Xe Graphics @ 1.30 GHz [Integrated]
MEMORY USED - 6.23 GiB / 11.45 GiB (54%)
SWAP USED - 2.33 GiB / 8.00 GiB (29%)
DISK - 214.39 GiB / 475.35 GiB (45%) - btrfs
• SOFTWARE INFORMATION
DISTRO - Fedora Linux 43 (Workstation Edition) x86_64
INSTALLED DATE - 2025-07-19 05:37:24
KERNEL - Linux 6.17.7-300.fc43.x86_64
PACKAGES - 2484 (rpm), 38 (flatpak), 32 (brew)
UPTIME - 2 hours, 2 mins
• DISPLAY INFORMATION
LOGIN MANAGER - Wayland
WM - niri (Wayland)
MONITOR (BOE07CB) - 1920x1080 @ 60 Hz - 340x190 mm (15 inches, 144 ppi)
• DESIGN INFORMATION
KDE THEME -
ICON THEME -
FONT - Unknown
TERMINAL FONT - JetBrainsMono NFM Bold (16pt)
CURSOR - default (24px)
• VARIOUS INFORMATION
WEATHER - +16°C - Clear (Cape Town, South Africa)
INFO - fastfetch 2.48.1 (x86_64)

[alexaandru]

FWIW, it works fine on EndeavourOS: Ghostty 1.2.3-arch2

[kevinnkansah]

@alexaandru with all due respect , how does you tell me that resolve my issue. I tested on 5 TERMINALS. It works for all but not Ghostty (niri). i dont care about the distro you use.

[alexaandru]

My intent was to provide additional information to developers to aid them with fixing this. The point was never to prove you wrong or anything like that.

[peterbartels]

I'm experiencing the same issue. I'm using arch liux & Ghostty

[maorv]

I experience same issue
$ghostty --version

Ghostty 1.2.3-arch2

Version

• version: 1.2.3-arch2
• channel: tip
  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.17.5-arch1-1
• desktop env : other
• GTK version :
  build : 4.20.2
  runtime : 4.20.2
• libadwaita : enabled
  build : 1.8.1
  runtime : 1.8.1
• libX11 : enabled
• libwayland : enabled

$ copilot --version
0.0.354
Commit: 076bd172b

[maorv]

A workaround to make it work is to set

keybind = enter=text:\r
in $HOME/.config/ghosttty/config 

[RyanHecht]

I started using niri with ghostty over the weekend and can reproduce this if the team needs an internal repro :)

[patniko]

FYI @RyanHecht I was able to repro on MacOS 26.1. Issue appears larger than linux distros.

[00-kat]

I don't use Copilot CLI (and don't have time to mess with it either), but someone opened a post¹ in Ghostty's Discord's #help channel about this, and it was discovered that Copilot uses the Kitty keyboard protocol; the issue might be there (they confirmed it doesn't reproduce on GNOME Terminal (VTE), which doesn't support KKP).

The workaround above,

keybind = enter=text:\r

Is also quite suspect, as that essentially forces Ghostty to encode enter with the legacy encoding.

tested on 5 TERMINALS

Checking if it works fine on another terminal emulator supporting KKP (e.g.: Kitty, Foot, WezTerm, Alacritty) would help disprove this theory of course (though it could be some combination of KKP and Ghostty, such as with special-casing terminal emulators).

FWIW, it works fine on EndeavourOS: Ghostty 1.2.3-arch2

And KKP support was only introduced in v0.0.337, so it would presumably work on older versions if this is the issue (though to be fair that version is a month and a half old).

Footnotes

1. You need to be in the Ghostty Discord for this link to work; you can join with https://discord.gg/ghostty. ↩

[sergiou87]

FYI I checked with @patniko and he cannot reproduce it on Ghostty for macOS anymore. Right now it seems the issue has been reproduced only on:

• Fedora (+ niri) + Ghostty
• Arch Linux + Ghostty