Problem with calling terminal commands

[maryasov]

Which version of the app are you using?

3.8.1 and few previous versions

Which API Provider are you using?

DeepSeek

Which Model are you using?

DeepSeek-V3

What happened?

Every time Cline tries to run a second command in the terminal, it attempt to terminate the previous command by calling ^C before the command, but the terminal was not locked. Then model retries last command because it get non-zero status from terminal

Steps to reproduce

Relevant API REQUEST output

Additional context

No response

[hannesrudolph]

@KJ7LNW do you have any insight here?

[KJ7LNW]

then model retries last command because it get non-zero status from terminal

This is upstream VSCE behavior (not Roo) when it thinks a command is still running. I think that it is not getting the command termination escape sequence \x1b]633;D.

Are you running any special PS1 or PROMPT_COMMAND settings in your .bashrc or .bash_profile?

After the command fails the first time, try this:

PROMPT_COMMAND='sleep 0.050'
PS1='[\u@\h \W]\$ '
source "$(code --locate-shell-integration-path bash)"

and then see if additional commands work better.

[KJ7LNW]

There was a major overhaul of shell integration in last night's code-insiders build. Please test and see if it behaves.
(upstream vscode, not Roo)

[maryasov]

There was a major overhaul of shell integration in last night's code-insiders build. Please test and see if it behaves.
(upstream vscode, not Roo)

I installed the latest version of VSCode Insiders (1.99.0) selected the “bash” terminal profile
Now Roo-Cline doesn't realize that the command “rm info/doc-7.md” has finished at all and stands waiting with a spinner. and offers only “Proceed while running”.

[KJ7LNW]

sounds like an upstream regression. I'll look into it and see.

[KJ7LNW]

also please try this from a Roo-launched prompt:

PROMPT_COMMAND='sleep 0.050'
PS1='[\u@\h \W]\$ '
source "$(code --locate-shell-integration-path bash)"

[KJ7LNW]

also, what OS are you running?