Skip to content

Commit bbd5f8f

Browse files
committed
give gpt-5 editor a hint on the tool call format
1 parent e9a2b7a commit bbd5f8f

File tree

1 file changed

+27
-1
lines changed

1 file changed

+27
-1
lines changed

.agents/editor/best-of-n/editor-best-of-n.ts

Lines changed: 27 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,33 @@ Write out what changes you would make using str_replace and/or write_file tool c
5555
5656
${
5757
isGpt5
58-
? ``
58+
? `<example>
59+
<codebuff_tool_call>
60+
{
61+
"cb_tool_name": "str_replace",
62+
"path": "path/to/file",
63+
"replacements": [
64+
{
65+
"old": "exact old code",
66+
"new": "exact new code"
67+
},
68+
{
69+
"old": "exact old code 2",
70+
"new": "exact new code 2"
71+
},
72+
]
73+
}
74+
</codebuff_tool_call>
75+
76+
<codebuff_tool_call>
77+
{
78+
"cb_tool_name": "write_file",
79+
"path": "path/to/file",
80+
"instructions": "What the change does",
81+
"content": "Complete file content or edit snippet"
82+
}
83+
</codebuff_tool_call>
84+
</example>`
5985
: `
6086
You can also use <think> tags interspersed between tool calls to think about the best way to implement the changes. Keep these thoughts very brief. You may not need to use think tags at all.
6187

0 commit comments

Comments
 (0)