✅ - terminal shell integration doesn't always work

[last gale]

command would run in the shell, but inside the kiro task window it just has the loading wheel and "working..." underneath

[earnest bough]

Hello @last gale, what command is running? If it is an ongoing command like npm run dev, it would wait until that command is finished (which only finishes with manual intervention)

[last gale]

Hello, this was happening for a variety of commands including jest , git, etc.

[last gale]

I've noticed it happens if I have an existing terminal window open already and it runs the command in an existing window instead of a new one

[lucid bone]

I have this problem as well, sometimes even when. the terminal completes it just sits there

[lucid bone]

@last gale I got it to be a lot more consistent by removing my zsh theme

[last gale]

Tried turning off instant prompt in my powerlevel10k and it didn't help. Might need to disable completely or use a different shell

Works great with bash 😃

Only thing I wish for is the backend to scale up 🚀 and I'm good to go

[lucid bone]

@earnest bough probably a good note that it has trouble with powerlevel10k theme (I use the same one)

[gloomy nova]

at least for me a workaround is after a successful command was executed is to close the terminal session, seems to have no problem making a new one, but with a one pre-existing it bugs out after some time (also using zsh and p10k)

[sullen coral]

I've had it sit there on commands that finish almost instantly, but I'm also using fish

[sullen coral]

I was able to fix it by changing the default shell to bash in my settings ("terminal.integrated.defaultProfile.linux": "bash",) so now I'm only getting a bunch of "the model you are using is experiencing high volume ... " errors. progress! 👍🏽

[glossy needle]

i think windsurf had the same issue? anyway to set a user default terminal set to fish while kiro gets standard bash without having to use the dropdown on every user session?

[remote epoch]

I have had no issues with zsh. To stop it from stalling because the terminal is waiting for input I usually give it these instructions in a file in .kiro/steering/

You will use `pnpm test:run` instead of `npm test`

You will NOT use `npm run dev` or `npm test` or any commands that run forever without user intervention

[lucid bone]

its not zsh itself, its the theme we were using. It was not commands the never complete, even commands that completed were not triggering the AI to continue

[pseudo elk]

Thank you for reporting these terminal shell integration issues. We recommend updating Kiro to the latest version 0.2.38 (https://kiro.dev/changelog/editor-performance-improvements-and-bug-fixes/) which includes several improvements and bug fixes.

Based on the discussion thread, we've observed that this issue particularly affects users with custom shell configurations (like powerlevel10k theme in zsh, fish shell, etc.). While some users have found temporary workarounds by:

• Switching to bash as the default shell
• Removing zsh themes
• Closing terminal sessions after command execution

If you continue to experience these issues after updating to version 0.2.38, please add your experience to our GitHub issue where we're actively tracking this: https://github.com/kirodotdev/Kiro/issues/53

I'll mark this thread as "answered" for now. Feel free to open a new thread in Discord for further discussions after updating Kiro.

Thank you for your patience and helping us improve Kiro!

[solemn night]

✅ - terminal shell integration doesn't always work