Conversation
A weak model hit shell.run, reached for 'cat file | sort' and 'sort ... > out', got both rejected, and concluded it could not sort or save anything -- it never tried the plain 'sort -r file' form. Two fixes. The shell.run description and the rejection message now spell out that commands take a file path as a direct argument and that no pipe is needed. And shell.run gains a save_to argument: the supported stand-in for '>', it writes the command's stdout through the same confined writer files.write uses, so it cannot escape the workspace.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
A weak model hit shell.run, reached for 'cat file | sort' and 'sort ... > out', got both rejected, and concluded it could not sort or save anything -- it never tried the plain 'sort -r file' form.
Two fixes. The shell.run description and the rejection message now spell out that commands take a file path as a direct argument and that no pipe is needed. And shell.run gains a save_to argument: the supported stand-in for '>', it writes the command's stdout through the same confined writer files.write uses, so it cannot escape the workspace.