Using its own TERM is a deliberate design decision. I don't remember how to fix the terminal database, but it's pretty easy (your favorite search engine or LLM should be able to help you there).
Or the manual, which describes the features for automatically handling it.
{"deleted":true,"id":47207427,"parent":47207327,"time":1772377989,"type":"comment"}
If I install a terminal and SSH doesn't work from it out of the box, I would describe that as a bug and wonder if I need to read the full manual to not fall foul of other gotchas
It is a bug.. But not with Ghostty...
What do you think the bug is, exactly?
Servers throwing "missing or unsuitable terminal" even when the connecting terminal is available and very suitable. And this is just because they hardcode xterm as the "standard".
{"deleted":true,"id":47208979,"parent":47208570,"time":1772387663,"type":"comment"}
i had to do this for ssh
host * SetEnv TERM=xterm-256color
loading story #47209511