Roo loosing consistent connection to terminal (not seeing terminal output)

[cfdude]

Which version of the app are you using?

3.3.17

Which API Provider are you using?

OpenRouter

Which Model are you using?

Claude 3.5 Sonnet

What happened?

https://discord.com/channels/1332146336664915968/1338654181988241518

Can confirm multiple users are reporting an issue where Roo does not see terminal output. I've experienced this myself, Roo runs a test, the test completes fairly fast and Roo reports that it didn't see any output and tries to run the test again. Another instance, Roo was waiting for output in the terminal and just kept waiting. This issue appears to effect users with ZSH, even those with the fix/workaround in place for Oh My ZSH. This is an intermittent bug, not easily repeatable with specific steps at this point.

Steps to reproduce

Relevant API REQUEST output

Additional context

No response

[egyleader]

same issue here , +1

[cfdude]

@egyleader are you using "Oh My ZSH" by chance? I've found that if I modify my .zshrc file and completely comment out lines added by Oh My ZSH it works just fine. There is something about Oh My ZSH that interrupts this. I've switched over to Starship for my customized shell and I haven't had any issues since.

[egyleader]

UPDATE & FIX :

yes I kept getting this message:

and also I had the multiple terminal issue #552

and I've done the following to fix them :

1. removed omz entirely (even the lines in .zshrc) , it makes problems with roo even after re-installing it and tried Starship as recommended by @cfdude and can confirm it works fine with roo-cline

2. I had amazon Q in my system and vscode extention that kept adding this lines in my .zshrc file :

  "terminal.integrated.env.osx": {
    "Q_NEW_SESSION": "1"
  }

so I deleted it , I am not sure it conflicts with roo though.

3. I've used manual terminal integration as described here

• by adding this to my settings.json "terminal.integrated.shellIntegration.enabled": false
• and adding these lines to my .zshrc :

path+=("/Applications/Visual Studio Code.app/Contents/Resources/app/bin")
[[ "$TERM_PROGRAM" == "vscode" ]] && . "$(code --locate-shell-integration-path zsh)"

[cfdude]

I'm not sure if this will work for you, but this currently works for me. Try downloading iTerm2 https://iterm2.com, its free. In VS Code, try setting the Mac terminal to iTerm2.app as seen in this screenshot.

Be sure to restart iTerm2 if you have it open and also restart VS Code. Once you restart iTerm, I'd be curious what the results of these commands are. They should verify you're running ZSH and show the version:

echo $SHELL
zsh --version

[neoliminal]

Didn't work for me. :(

[unkier]

version 3.7.8 - same. model complains, "I see that the command executed, but I don't see the output."

[hannesrudolph]

Changes have been recently made to fix this. I am not sure if they worked as this thread does not have any clear repro steps.

[KJ7LNW]

Try https://www.linuxglobal.com/out/roo/roo-cline-3.11.12-fix-misc-terminal-issues.vsix build of #2456 and enable the ZDOTDIR option or the , that may fix it.

also try these in that build: