Blackbird

Blackbird advertises TERM=xterm-kitty locally so kitty-aware tools get the full keyboard protocol, but remote hosts often don't know that terminfo entry — and remote tools that sniff TERM strings for color support don't either. Current versions of Blackbird fix this automatically: shell integration runs every ssh with TERM=xterm-256color, the value every remote stack recognizes (kitty's keyboard protocol still works remotely — apps negotiate it at runtime, independent of TERM). Prefer the kitty TERM on your remotes? Export BB_SSH_REMOTE_TERM=kitty and Blackbird instead installs the terminfo entry on first connect (cached per host), falling back to xterm-256color only if the install can't land. On older Blackbird versions, run infocmp -x xterm-kitty | ssh <host> 'tic -x -' once per host, or install ncurses-term on the remote. Automatic integration covers zsh and fish; bash users can source the bundled ssh.bash from .bashrc. Inside tmux, panes see tmux's own default-terminal instead — if colors look wrong there (in any terminal), add set -g default-terminal "tmux-256color" to your tmux config.