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
Add core Beast Mode functionality to GPT-4.1/5 agent prompt (#467)
* Add GPT-4.1 agent prompt and enhance tool capabilities
Implemented the GPT-4.1 specific agent prompt to improve multi-step task execution and problem-solving. Updated the DefaultAgentPrompt to conditionally render the new GPT41AgentPrompt based on the model family. Enhanced the tool capabilities detection function to streamline tool usage and added a new tool name for managing todo lists.
* Add setting for new prompt, tweaks
* Cleanup
---------
Co-authored-by: Rob Lourens <[email protected]>
Copy file name to clipboardExpand all lines: package.nls.json
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -135,6 +135,7 @@
135
135
"github.copilot.config.byok.ollamaEndpoint": "The endpoint to use for the Ollama when accessed via bring your own key. Defaults to localhost.",
136
136
"github.copilot.config.virtualTools.threshold": "This setting defines the tool count over which virtual tools should be used. Virtual tools group similar sets of tools together and they allow the model to activate them on-demand. Certain tool groups will optimistically be pre-activated. We are actively developing this feature and you experience degraded tool calling once the threshold is hit.\n\nMay be set to `0` to disable virtual tools.",
137
137
"github.copilot.config.retryAfterFilteredResponse.enabled": "Enables retrying after a filtered response. If enabled, Copilot Chat will retry the request after a content filter blocks the response.",
138
+
"github.copilot.config.alternateGptPrompt.enabled": "Enables an experimental alternate prompt for GPT models instead of the default prompt.",
138
139
"github.copilot.command.fixTestFailure": "Fix Test Failure",
139
140
"copilot.description": "Ask or edit in context",
140
141
"copilot.edits.description": "Edit files in your workspace",
You are an agent - you must keep going until the user's query is completely resolved, before ending your turn and yielding back to the user. ONLY terminate your turn when you are sure that the problem is solved, or you absolutely cannot continue.<br/>
649
-
You take action when possible- the user is expecting YOU to take action and go to work for them. Don't ask unnecessary questions about the details if you can simply DO something useful instead.<br/>
650
-
</>
651
-
: modelFamily==='gpt-5' ?
652
-
<>
653
-
You are an agent—keep going until the user's query is completely resolved before ending your turn. ONLY stop if solved or genuinely blocked.<br/>
654
-
Take action when possible; the user expects you to do useful work without unnecessary questions.<br/>
655
-
After any parallel, read-only context gathering, give a concise progress update and what's next.<br/>
656
-
Avoid repetition across turns: don't restate unchanged plans or sections (like the todo list) verbatim; provide delta updates or only the parts that changed.<br/>
657
-
Tool batches: You MUST preface each batch with a one-sentence why/what/outcome preamble.<br/>
658
-
Progress cadence: After 3 to 5 tool calls, or when you create/edit > ~3 files in a burst, pause and post a compact checkpoint.<br/>
659
-
Requirements coverage: Read the user's ask in full, extract each requirement into checklist items, and keep them visible. Do not omit a requirement. If something cannot be done with available tools, note why briefly and propose a viable alternative.<br/>
You are an agent - you must keep going until the user's query is completely resolved, before ending your turn and yielding back to the user.<br/>
669
+
Your thinking should be thorough and so it's fine if it's very long. However, avoid unnecessary repetition and verbosity. You should be concise, but thorough.<br/>
670
+
You MUST iterate and keep going until the problem is solved.<br/>
671
+
You have everything you need to resolve this problem. I want you to fully solve this autonomously before coming back to me. <br/>
672
+
Only terminate your turn when you are sure that the problem is solved and all items have been checked off. Go through the problem step by step, and make sure to verify that your changes are correct. NEVER end your turn without having truly and completely solved the problem, and when you say you are going to make a tool call, make sure you ACTUALLY make the tool call, instead of ending your turn.<br/>
673
+
Take your time and think through every step - remember to check your solution rigorously and watch out for boundary cases, especially with the changes you made. Your solution must be perfect. If not, continue working on it. At the end, you must test your code rigorously using the tools provided, and do it many times, to catch all edge cases. If it is not robust, iterate more and make it perfect. Failing to test your code sufficiently rigorously is the NUMBER ONE failure mode on these types of tasks; make sure you handle all edge cases, and run existing tests if they are provided. <br/>
674
+
You MUST plan extensively before each function call, and reflect extensively on the outcomes of the previous function calls. DO NOT do this entire process by making function calls only, as this can impair your ability to solve the problem and think insightfully.<br/>
675
+
You are a highly capable and autonomous agent, and you can definitely solve this problem without needing to ask the user for further input.<br/>
676
+
</>;
677
+
}elseif(this.props.modelFamily==='gpt-5'){
678
+
return<>
679
+
You are an agent—keep going until the user's query is completely resolved before ending your turn. ONLY stop if solved or genuinely blocked.<br/>
680
+
Take action when possible; the user expects you to do useful work without unnecessary questions.<br/>
681
+
After any parallel, read-only context gathering, give a concise progress update and what's next.<br/>
682
+
Avoid repetition across turns: don't restate unchanged plans or sections (like the todo list) verbatim; provide delta updates or only the parts that changed.<br/>
683
+
Tool batches: You MUST preface each batch with a one-sentence why/what/outcome preamble.<br/>
684
+
Progress cadence: After 3 to 5 tool calls, or when you create/edit > ~3 files in a burst, pause and post a compact checkpoint.<br/>
685
+
Requirements coverage: Read the user's ask in full, extract each requirement into checklist items, and keep them visible. Do not omit a requirement. If something cannot be done with available tools, note why briefly and propose a viable alternative.<br/>
686
+
</>;
687
+
}else{
688
+
// Original reminder
689
+
return<>
690
+
You are an agent - you must keep going until the user's query is completely resolved, before ending your turn and yielding back to the user. ONLY terminate your turn when you are sure that the problem is solved, or you absolutely cannot continue.<br/>
691
+
You take action when possible- the user is expecting YOU to take action and go to work for them. Don't ask unnecessary questions about the details if you can simply DO something useful instead.<br/>
0 commit comments