Reworked "When executing commands, if you don't see" rule fixing the "can't see output bug" #1043
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…eaking Roo when using the Anthropic API.
Contributor
|
this maybe an important clarification because unix philosophy has always been to exclude output for successful operations. I think this philosophy is less common these days, but still a consideration:
|
Contributor
|
also in the less common case of a user not supporting shell integration, #1365 will report this message to the model: this.emit(
"completed",
"<shell integration is not available, so terminal output and command execution status is unknown>",
) |
Member
|
Hey @jakenuts, |
github-project-automation
bot
moved this from PR [Draft/WIP]
to Done
in Roo Code Roadmap
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Updated the language of the rule that prevented Roo from seeing the terminal output when using the latest Claude Sonnet 3.5 model.
Instead of:
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. If you absolutely need to see the actual terminal output, use the ask_followup_question tool to request the user to copy and paste it back to you.
It now reads:
Type of change
How Has This Been Tested?
I loaded the history of a task where Roo was ignoring the terminal output (or rather "could not see" the output) and with this change to the associated rule Roo started seeing the errors and correcting them.
Checklist:
Additional context
Related Issues
#1038
Reviewers