SWE-agent takes a GitHub issue and tries to automatically fix it, using your LM of choice. It can also be employed for offensive cybersecurity or competitive coding challenges. [NeurIPS 2024]
Config: Update docstring of str_replace_editor
Kilian Lieret1d16b9d2641d
diff --git a/tools/edit_anthropic/config.yaml b/tools/edit_anthropic/config.yamlindex d68fa98c..5a3dd6cd 100644--- a/tools/edit_anthropic/config.yaml+++ b/tools/edit_anthropic/config.yaml@@ -2,8 +2,20 @@ tools:str_replace_editor:signature: |str_replace_editor <command> <path> [<file_text>] [<view_range>] [<old_str>] [<new_str>] [<insert_line>]+ # This docstrings was taken from openhands:+ # https://github.com/All-Hands-AI/OpenHands/blob/main/openhands/agenthub/codeact_agent/function_calling.pydocstring: >- Create, view, or edit a file.+ Custom editing tool for viewing, creating and editing files+ * State is persistent across command calls and discussions with the user+ * If `path` is a file, `view` displays the result of applying `cat -n`. If `path` is a directory, `view` lists non-hidden files and directories up to 2 levels deep+ * The `create` command cannot be used if the specified `path` already exists as a file+ * If a `command` generates a long output, it will be truncated and marked with `<response clipped>`+ * The `undo_edit` command will revert the last edit made to the file at `path`++ Notes for using the `str_replace` command:+ * The `old_str` parameter should match EXACTLY one or more consecutive lines from the original file. Be mindful of whitespaces!+ * If the `old_str` parameter is not unique in the file, the replacement will not be performed. Make sure to include enough context in `old_str` to make it unique+ * The `new_str` parameter should contain the edited lines that should replace the `old_str`arguments:- name: commandtype: string