Sweep 22 Sep 2026 · 15:52Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Writing the changelog v2.1.280 merge candidates · 1/5 waiting for the next tick
Tool description

Edit, as sent

CLI Claude Code, interactive mode, v2.1.270. 17 model strings share this prompt, byte for byte.

Lines91,094 characters
Moved+0−0 against v2.1.269
Reach17model strings receive this description
Copies2distinct descriptions under this name
Parameters43 of them required Tools in captureall of themevery description on this arm
2 genuinely different descriptions of this tool Plain text · sha256 f907faa95966

The description, rendered

This renders the markdown inside the description, so it isn’t quite the description itself.

The raw view and the plain text are the bytes as they were sent.

Performs exact string replacements in files.

Usage:

  • You must use your Read tool at least once in the conversation before editing. This tool will error if you attempt an edit without reading the file.
  • When editing text from Read tool output, ensure you preserve the exact indentation (tabs/spaces) as it appears AFTER the line number prefix. The line number prefix format is: line number + tab. Everything after that is the actual file content to match. Never include any part of the line number prefix in the old_string or new_string.
  • ALWAYS prefer editing existing files in the codebase. NEVER write new files unless explicitly required.
  • Only use emojis if the user explicitly requests it. Avoid adding emojis to files unless asked.
  • The edit will FAIL if old_string is not unique in the file. Either provide a larger string with more surrounding context to make it unique or use replace_all to change every instance of old_string.
  • Use replace_all for replacing and renaming strings across the file. This parameter is useful if you want to rename a variable for instance.

What it accepts

4 parameters The JSON parameter schema sent beside this description, 654 characters of it. Name, type, then whether the client marked it required.
file_path string required The absolute path to the file to modify
new_string string required The text to replace it with (must be different from old_string)
old_string string required The text to replace
replace_all boolean optional Replace all occurrences of old_string (default false)

sha256 9748c75edc64 · the schema as the client sent it:

{ "$schema": "https://json-schema.org/draft/2020-12/schema", "additionalProperties": false, "properties": { "file_path": { "description": "The absolute path to the file to modify", "type": "string" }, "new_string": { "description": "The text to replace it with (must be different from old_string)", "type": "string" }, "old_string": { "description": "The text to replace", "type": "string" }, "replace_all": { "default": false, "description": "Replace all occurrences of old_string (default false)", "type": "boolean" } }, "required": [ "file_path", "old_string", "new_string" ], "type": "object" }