Compare commits

...
Author SHA1 Message Date
Araandellipsis-dev[bot] 1a1616f462 Update src/core/prompts/system.ts
Co-authored-by: ellipsis-dev[bot] <65095814+ellipsis-dev[bot]@users.noreply.github.com>
2025-05-28 08:27:59 +05:30
Cline Evaluation ff16c3877f Show gemini 2.5 flash prompt cache 2025-05-28 06:52:44 +04:00
Cline Evaluation 8ba20f2494 Fix Claude 4 diff edits prompt 2025-05-28 06:48:03 +04:00
2 changed files with 7 additions and 0 deletions
+5
View File
@@ -0,0 +1,5 @@
---
"claude-dev": patch
---
fix prompt for claude 4 family diff edits
+2
View File
@@ -605,6 +605,8 @@ ${
3. Once the file has been edited with either write_to_file or replace_in_file, the system will provide you with the final state of the modified file. Use this updated content as the reference point for any subsequent SEARCH/REPLACE operations, since it reflects any auto-formatting or user-applied changes.
4. All edits are applied in sequence, in the order they are provided
5. All edits must be valid for the operation to succeed - if any edit fails, none will be applied
6. Do not make more than 4 replacements in a single replace_in_file call, as this can lead to errors and make it difficult to track changes. If you need to make more than 4 changes, consider breaking them into multiple replace_in_file calls.
7. Make sure a single old_str in a replace_in_file call is no more than 4 lines, as too many lines can lead to errors. If you need to replace a larger section, break it into smaller blocks.
`
: `