Terminal resize crashes kiro-cli

[stuckinsnow]

Before opening, please confirm:

• I have searched for duplicate or closed issues

Operating System

Linux

Kiro Version

Latest

Bug Description

With kitty 0.46.2, if I open kiro-cli in a terminal, then shrink the terminal, kiro-cli crashes.

Steps to Reproduce

With a tiling wm (i3), open kiro-cli in kitty, then open something to the side e.g. file browser, then close the file browser so kitty expands to fill the space and it will crash

Expected Behavior

Terminal should resize and kiro-cli should not crash

Conversation ID

No response

Additional Context

This could be a kitty issue but I haven't seen it with other terminal apps

[github-actions]

Thanks for reporting this issue! We appreciate you providing detailed reproduction steps for the terminal resize crash in kiro-cli with Kitty — that's really helpful for narrowing things down. A maintainer will take a look at this shortly. In the meantime, thanks for checking that it doesn't happen with other terminal apps; that kind of context goes a long way! 🙌

[hmcqueen]

I'm having the same issue when I resize my terminal. kiro-cli became unresponsive and a bun process went out of control, consuming excessive cpu and growing to use 56 GB of memory.

I'm on PopOS 24.04 and using gnome terminal

[ahfx]

+1

[Kitty-gehc]

Title: kiro-cli TUI hangs and leaks memory on terminal resize (SIGWINCH)

Description:

When resizing the terminal window while kiro-cli chat is running, the tui.js process enters a
runaway state — consuming unbounded memory and becoming unresponsive.

Environment:

• kiro-cli (latest as of 2026-05-04)
• Linux (remote server via SSH from VS Code terminal)
• Reproduces in: VS Code integrated terminal, GNU screen, likely any terminal

Steps to reproduce:

1. SSH into a remote Linux server
2. Run kiro-cli chat
3. Resize the terminal window (drag VS Code panel divider, or resize the window)

Expected: TUI re-renders to fit new dimensions

Actual: tui.js process hangs, CPU spikes, memory grows unbounded (observed 53 GB before manual kill)

Relevant process:

/home/user/.local/share/kiro-cli/bun /home/user/.local/share/kiro-cli/tui.js chat

Workaround: Kill the process with pkill -f 'tui.js chat' and restart.

Root cause hypothesis: The SIGWINCH handler in tui.js likely triggers a re-render loop without
debouncing, causing infinite layout recalculations and memory allocation

[stuckinsnow]

This now seems to be fixed! Thank you.

[AnilMaktala]

Thanks for reporting this, and glad to hear it's resolved!

This was a known issue with the TUI's SIGWINCH (terminal resize signal) handling that caused the bun/tui.js process to enter a runaway state. It's been addressed in a recent CLI update.

Closing this issue as resolved. If anyone still experiences this on the latest version, please open a new issue with your CLI version (kiro --version).