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).

▲

frereubu 6 hours ago | parent | next [-]

https://ghostty.org/docs/help/terminfo#ssh

▲

ubercow13 7 hours ago | parent | prev | next [-]

Or the manual, which describes the features for automatically handling it.

▲

7 hours ago | parent | next [-]

[deleted]

▲

dwedge 7 hours ago | parent | prev [-]

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

▲

Daviey 7 hours ago | parent [-]

It is a bug.. But not with Ghostty...

▲

dwedge 5 hours ago | parent [-]

What do you think the bug is, exactly?

	▲	nout an hour ago \| parent \| next [-]
		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".
	▲	5 hours ago \| parent \| prev [-]
		[deleted]

▲

hijinks 7 hours ago | parent | prev | next [-]

i had to do this for ssh

host * SetEnv TERM=xterm-256color

▲

FireBeyond 4 hours ago | parent | prev [-]

I definitely have had to poke at things a bit, even where they "should" work. I use salt in my homelab and eventually got the xterm-ghostty.terminfo file and I put it in my baseline salt config, then you run 'tic -x xterm-ghostty.terminfo'.