You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: agents/editor/best-of-n/editor-implementor.ts
+9-8Lines changed: 9 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -51,12 +51,12 @@ You can make multiple tool calls across multiple steps to complete the implement
51
51
"path": "path/to/file",
52
52
"replacements": [
53
53
{
54
-
"old": "exact old code",
55
-
"new": "exact new code"
54
+
"oldString": "exact old code",
55
+
"newString": "exact new code"
56
56
},
57
57
{
58
-
"old": "exact old code 2",
59
-
"new": "exact new code 2"
58
+
"oldString": "exact old code 2",
59
+
"newString": "exact new code 2"
60
60
},
61
61
]
62
62
}
@@ -72,9 +72,10 @@ OR for new files or major rewrites:
72
72
"content": "Complete file content"
73
73
}
74
74
</codebuff_tool_call>
75
-
${isGpt5||isGemini
76
-
? ``
77
-
: `
75
+
${
76
+
isGpt5||isGemini
77
+
? ``
78
+
: `
78
79
IMPORTANT: Before you start writing your implementation, you should use <think> tags to think about the best way to implement the changes. You should think really really hard to make sure you implement the changes in the best way possible. Take as much time as you to think through all the cases to produce the best changes.
79
80
80
81
You can also use <think> tags interspersed between tool calls to think about the best way to implement the changes.
@@ -102,7 +103,7 @@ You can also use <think> tags interspersed between tool calls to think about the
102
103
</codebuff_tool_call>
103
104
104
105
</example>`
105
-
}
106
+
}
106
107
107
108
After the edit tool calls, you can optionally mention any follow-up steps to take, like deleting a file, or a specific way to validate the changes. There's no need to use the set_output tool as your entire response will be included in the output.
0 commit comments