System Prompt prevents Roo from reading terminal output leading to lots of wasted "fixes" and no progress.

[jakenuts]

Which version of the app are you using?

3.3.20

Which API Provider are you using?

Anthropic

Which Model are you using?

claude-3-5-sonnet-20241022

What happened?

This system instruction is being interpretted differently with the latest model, causing Roo (and Cline) to ignore terminal output if it is "unexpected". This impacts nearly every operation that involves reading terminal output and results in endless attempts to fix problems that don't actually exist.

"When executing commands, if you don't see the expected output, assume the terminal executed the command successfully and proceed with the task. The user's terminal may be unable to stream the output back properly."

Here is Roo confirming this instruction is at fault for it's inability to see unexpected output.

Steps to reproduce

1. Write a test of a method with a compilation error. In my case its an Xunit test of a class that is missing a "using" statement
2. Ask Roo to run the test and tell you what the problem might be
3. Roo runs the test, the build fails, but Roo ignores the output and comes up with some other error and potential fix[Roo runs the test, the output includes build errors, Roo says there is no output from the test]

Relevant API REQUEST output

Additional context

I have tried overriding the command with entries in the "Prompts" tab, but it seems like it can't be properly dismissed. Is there a way to update the actual system command in Prompts?

[jakenuts]

After further testing, it may not be the system prompt (Claude says it is) but there is actually truly no output from a command. I looked at the results from calls to "dotnet test" and one had the output, the other didn't. It's also possible that one command had concatenated commands like "cd x:\myapp && dotnet test --verbose"

[hannesrudolph]

@jakenuts are you still having issues with this? We recently made some changes that might have fixed this.

[jakenuts]

I'll check it out, thanks!

For reference back on the cline repo there are similar terminal output issues being reported on Linux and the "assume success" system prompt is likely masking the problem.