Checks
Operating system
Linux 6.1.0-44-amd64 - Debian GNU/Linux 12 (bookworm)
Expected behaviour
I can write on my build server connected to SSH kiro-cli and the new TUI works as the classic version.
Actual behaviour
After upgrading the kiro-cli binary. I am getting an error on initialization. I don't get any logs and --verbose also do not show anything useful.
The doctor commands shows information for a SSHD configuration that do not help at all. After changing it the issue remains.
Steps to reproduce
I think that the new kiro-cli TUI is assuming a SSH connection through kiro-cli when it is not. I am connecting to my build server to a normal SSH connection.
- Download latest version of
kiro-cli
- After logging and everything do
kiro-cli. An return error and nothing else is shown
- Same machine, same SSH connection
kiro-cli --classical, the command works and I can use the models.
Environment
<This will be visible to anyone. Do not include personal or sensitive information>
[q-details]
version = "2.0.0"
hash = "0026b0505ef7bc2b10780c7bdb57813e5d949747"
date = "2026-04-13T09:03:52.798806Z (2d ago)"
variant = "minimal"
[system-info]
chip = "QEMU Virtual CPU version 2.5+"
total-cores = 96
memory = "125.77 GB"
[system-info.os.linux]
kernel_version = "6.1.0-44-amd64"
id = "debian"
name = "Debian GNU/Linux"
pretty_name = "Debian GNU/Linux 12 (bookworm)"
version_id = "12"
version = "12 (bookworm)"
[environment]
cwd = "/home/USER"
cli-path = "/home/USER"
os = "Linux"
shell-path = "/usr/bin/zsh"
shell-version = "5.9"
install-method = "unknown"
in-ssh = true
[env-vars]
DISPLAY = "localhost:14.0"
PATH = "/home/USER/.miniconda/condabin:/home/USER/.cargo/bin:/usr/local/bin:/usr/bin:/bin:/usr/games:/home/USER/.local/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/USER/.local/bin:/opt/nvim/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/USER/.local/bin:/opt/nvim/bin"
QTERM_SESSION_ID = "c15e0a2ad7814c458da408b0388cde4d"
Q_SET_PARENT_CHECK = "1"
Q_TERM = "2.0.0"
SHELL = "/bin/zsh"
TERM = "xterm-256color"
XDG_SESSION_TYPE = "tty"
Checks
q doctorin the affected terminal sessionq restartand replicated the issue againOperating system
Linux 6.1.0-44-amd64 - Debian GNU/Linux 12 (bookworm)
Expected behaviour
I can write on my build server connected to SSH
kiro-cliand the new TUI works as the classic version.Actual behaviour
After upgrading the
kiro-clibinary. I am getting an error on initialization. I don't get any logs and--verbosealso do not show anything useful.The
doctorcommands shows information for a SSHD configuration that do not help at all. After changing it the issue remains.Steps to reproduce
I think that the new
kiro-cliTUI is assuming a SSH connection throughkiro-cliwhen it is not. I am connecting to my build server to a normal SSH connection.kiro-clikiro-cli. An return error and nothing else is shownkiro-cli --classical, the command works and I can use the models.Environment