Kiro 2.0.1 breaks completely after update

[obijan42]

Checks

• I have searched github.com/aws/amazon-q-developer-cli/issues and there are no duplicates of my issue
• I have run q doctor in the affected terminal session
• I have run q restart and replicated the issue again

Operating system

Linux 6.8.0-110-generic - Ubuntu 24.04.4 LTS

Expected behaviour

Sidebar: Did you know that "q" is now called "Kiro"? Maybe update the docs?

After running kiro-cli update, I expect Kiro to still work.

Actual behaviour

When launching with "q" or "kiro-cli" NOTHING happens.
Tried a reinstall. Nothing worked.

Deleted all configurations. Reinstalled.
Had to log in again.
Nothing worked.

Did the sshd changes. ( WHY DO I NEED TO MESS WITH SSHD CONFIG ON STANDALONE MACHINE????)
Nothing.

A log file would be great...

Steps to reproduce

$q doctor
Warning! Q CLI is now Kiro CLI and should be invoked as kiro-cli rather than q

✘ Kiro CLI terminal integrations: kiro-cli-term is not running in this terminal, please try restarting your terminal

✘ Doctor found errors. Please fix them and try again.

If you are not sure how to fix it, please open an issue with kiro-cli issue to let us know!

$ kiro-cli-term
$ kiro-cli
$ kiro-cli doctor

✔ Everything looks good!

Kiro CLI still not working? Run kiro-cli issue to let us know!

$ kiro-cli chat
$

Environment

<This will be visible to anyone. Do not include personal or sensitive information>

[q-details]
version = "2.0.1"
hash = "4a41569da83e25b6ab94898d7c4c83fa18cb5216"
date = "2026-04-17T14:49:43.303879Z (10h ago)"
variant = "minimal"

[system-info]
chip = "Intel(R) Xeon(R) CPU E5-1620 0 @ 3.60GHz"
total-cores = 4
memory = "25.37 GB"

[system-info.os.linux]
kernel_version = "6.8.0-110-generic"
id = "ubuntu"
name = "Ubuntu"
pretty_name = "Ubuntu 24.04.4 LTS"
version_id = "24.04"
version = "24.04.4 LTS (Noble Numbat)"

[environment]
cwd = "/home/USER"
cli-path = "/home/USER"
os = "Linux"
shell-path = "/usr/bin/bash"
shell-version = "5.2.21"
install-method = "unknown"
in-ssh = true

[env-vars]
PATH = "~/scripts/:~/scripts/:/home/USER/.local/bin:~/scripts/:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/home/USER/.local/bin"
QTERM_SESSION_ID = "f6cdd8269943488c89ac913e1a1ceb27"
Q_SET_PARENT_CHECK = "1"
Q_TERM = "2.0.1"
SHELL = "/bin/bash"
TERM = "xterm-256color"
XDG_SESSION_TYPE = "tty"

[obijan42]

Claude figured it out! The new TUI broke accessibility via SSH!

Is this on purpose?