[Bug] Terminal setup fails on VTE-based terminals (Ptyxis/GNOME Terminal)

---

Found 3 possible duplicate issues:

1. https://github.com/anthropics/claude-code/issues/8034
2. https://github.com/anthropics/claude-code/issues/10060
3. https://github.com/anthropics/claude-code/issues/7712

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

I'm also seeing the issue.

Ptyxis is the default for many linux distros so this is a major UX difficulty.

Ptyxis is now the default terminal for:

• Fedora Workstation/Silverblue/Kinoite 41+ source
• Project Bluefin and other Universal Blue immutable distributions source
• Ubuntu 25.10+ source

This makes the lack of Shift+Enter support a significant usability issue for a growing portion of Linux users. Multi-line prompts are essential for providing context to Claude.

The workaround of using "quick escape" workaround (\ + Enter, source) is clunky.

As I understand it, the underlying issue is that VTE sends the same byte sequence for Enter and Shift+Enter. Related: https://gitlab.gnome.org/GNOME/vte/-/merge_requests/14

I searched the Ptyxis issue tracker but found no existing issues for shift+enter or kitty keyboard protocol the work is happening upstream in VTE itself.

I'm on Bluefin DX 43 (based on Fedora Silverblue) running GNOME 49 with Ptyxis as the terminal.

$ gnome-shell --version
GNOME Shell 49.2

$ cat /etc/os-release
NAME="Bluefin"
VERSION="latest-43.20260122.1 (Silverblue)"
RELEASE_TYPE=stable
ID=bluefin
ID_LIKE="fedora"
VERSION_ID=43
VERSION_CODENAME="Deinonychus"
PRETTY_NAME="Bluefin (Version: latest-43.20260122.1)"
...

$ ptyxis --version
Ptyxis 49.2

  GTK: 4.20.3 (Compiled against 4.20.2)
  VTE: 0.82.2 (Compiled against 0.82.1)
...

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

AI is truly revolutionary. Who knew the key to solving a problem was simply to close the issue after 30 days without even having looked at it.

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.