Roo code does not respond on long-time terminal commands

[donhiddenname]

Which version of the app are you using?

v3.7.9

Which API Provider are you using?

OpenRouter

Which Model are you using?

claude 3.7

What happened?

Description:
When executing long-running commands in the terminal, such as a Docker build, if an error occurs, the Roo Code extension fails to detect the terminal's completion and becomes completely unresponsive. I am unable to interact with the extension in any way, and the only solution is to fully restart VS Code. This issue has occurred multiple times (at least 10 times), severely disrupting my workflow.

Actual Behavior:
The extension becomes unresponsive, requiring a full restart of VS Code to continue working.

Environment:

OS: MacOS 15.2
Terminal Type: Bash
Additional Notes:
This issue has been happening frequently, significantly affecting usability.

Steps to reproduce

Open VS Code with the Roo Code extension enabled.
Run a long-running command in the terminal (e.g., docker build ...).
Encounter an error in the terminal during execution.
Observe that the Roo Code extension does not detect the terminal's termination and freezes completely.
Try to interact with the extension – it remains unresponsive.
The only workaround is to restart VS Code entirely.
Expected Behavior:
The extension should properly detect terminal completion and remain responsive, even when an error occurs.

Relevant API REQUEST output

Additional context

No response

[Rain-Of-Stars]

matlab win11 as well

[hannesrudolph]

@Rain-Of-Stars @donhiddenname are you able to provide me some steps to repro this? My attempts are reproing it have not yielded any of the issues you mentioned above though I know this is a behaviour that occurs sometimes. Thanks.

[donhiddenname]

Yes please:

1. Try to build docker project by asking the Roo Code to run the command.
2. Let it run ~2-3min
3. When it finishes - Roo code does not catch a signal that terminal is finished processing the command

[ossconsulting]

I have the feeling that it is not only doing this on long commands. I have it hanging on simple and fast stuff like:
bin/rails generate migration CreateRoles

Executes it and just sits there... Only way to resume is teminate the task and start a new one.

BTW: I can terminate the task and then select it again and click resume task and it will resume where it stalled so there is a workaround.