News for hackers. Stuff that matters.
Re:Kitty 0.50 by Systemerror7A69 on Wednesday November 04, 2026 @04:27AM (#50363156)
Oh wow, I did not expect not only that many interesting changes, but also that many which seem actually specifically useful to me - very cool to read!

I love kitty, have used it for a long while now and pretty happy, except for that one thing about ssh xterm - but even that is mostly minor.

Really cool to see such active development of an already perfectly capable and working software.

Re:Kitty 0.50 by birdsongs on Wednesday November 04, 2026 @04:43AM (#50363233)
I have the same SSH qualms. I still use it because there's not much better for what I need.
Re:Kitty 0.50 by Systemerror7A69 on Wednesday November 04, 2026 @05:22AM (#50363540)
I believe I got rid of most of the issues with some .ssh setting which simply uses the normal xterm I believe. I can't check right at this moment, but apparently, simply using xterm and not the xterm-xkitty or what it's called does not actually make much problems when ssh-ing into a machine - not in my case at least.

It was a setting in some ~/.ssh config file though I believe, not a kitty setting.

Re:Kitty 0.50 by cybrox on Wednesday November 04, 2026 @07:12AM (#50364506)
I currently just use this in my .zshrc:

alias ssh="kitty +kitten ssh"

sshpass() { TERM=xterm-256color command sshpass "$@"; }

Could also alias sshpass differently but I mostly use that for embedded devices where I just want a simple shell anyways.

The alternative you mean is in ~/.ssh/config:

Host *

    SetEnv TERM="xterm-256color"
Re:Kitty 0.50 by xnickb on Wednesday November 04, 2026 @04:57AM (#50363355)
I've had so many issues with SSH that I ended up ghosttying kitty.
Re:Kitty 0.50 by cybrox on Wednesday November 04, 2026 @07:10AM (#50364498)
Fixed with a single alias or a single ssh config entry.
Re:Kitty 0.50 by Geezus_42 on Wednesday November 04, 2026 @07:26AM (#50364634)
Ghostty made that obvious in the documentation for me. I haven't looked at the kitty docs, so Idk if they do as well.
Re:Kitty 0.50 by xnickb on Wednesday November 04, 2026 @08:05AM (#50365005)
If you mean the `alias ssh="kitty +kitten ssh"` then no, it's not fixed at all.

For example pikvm exists with read-only mounted filesystem. Having to dive into the details to figure out that the issue is kitty trying to write a file to make some obscure terminal features work doesn't strike me as good design.

`alias ssh="TERM=xterm-256color ssh"` fixes it but isn't mentioned in the docs.

Re:Kitty 0.50 by KetoManx64 on Friday November 06, 2026 @11:43AM (#50394751)
> TERM=xterm-256color ssh

Yep, i switched to kitty a few months ago and Claude dug around and found the solution external to the docs. The developer is very opinionated about how he thinks you should use Kitty.

Re:Kitty 0.50 by wzdd on Wednesday November 04, 2026 @08:26AM (#50365239)
It’s actually fixed, for everything, with a single kitty config line which tells it to use xterm-256color as the terminal type.

I respect the man’s ideological correctness, but it’s not 1982 anymore and nobody is going to add more terminal types.

Re:Kitty 0.50 by remedan on Wednesday November 04, 2026 @06:37AM (#50364223)
Putting the following in my ~/.ssh/config fixed all ssh-related issues I had with kitty.

  Host *
    SetEnv TERM="xterm-256color"
Re:Kitty 0.50 by Systemerror7A69 on Wednesday November 04, 2026 @12:05PM (#50368487)
Yes! That was it, exactly. Thank you, I wasn't able to check my home computer at the time of writing my last comment.
Re:Kitty 0.50 by JaszHere on Wednesday November 04, 2026 @06:56AM (#50364363)
Doesn't `kitten ssh` solve the problem?

https://sw.kovidgoyal.net/kitty/kittens/ssh/

Re:Kitty 0.50 by Geezus_42 on Wednesday November 04, 2026 @07:30AM (#50364684)
Doesn't sound like it would work if connecting to a locked down server. However, the problem OP described is easily solved, for ghostty and kitty, by a single line in your local ssh config.