🤖 Disable file_edit_replace_lines tool #219
Merged
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
This tool frequently causes models (particularly GPT-5-Codex) to leave the repository in a broken state. Models struggle with line-based edits when files are modified concurrently or when they miscalculate line numbers. Changes: - Commented out tool creation in getToolsForModel() baseTools - Commented out tool name in getAvailableTools() list - Commented out import (no longer used) Tool definition and implementation remain intact for backwards compatibility with old history messages. Models should use file_edit_replace_string or file_edit_insert instead.
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.
Disables the
file_edit_replace_linestool by removing it from the available tools list.Why
This tool frequently causes models (particularly GPT-5-Codex) to leave the repository in a broken state. Models struggle with line-based edits when:
Changes
getToolsForModel()baseToolsgetAvailableTools()listBackwards Compatibility
Tool definition and implementation remain intact so old history messages continue to render correctly. The tool simply won't be available for new messages.
Alternatives
Models should use:
file_edit_replace_string- More reliable, based on exact text matchingfile_edit_insert- Simpler for adding new contentGenerated with
cmux