From 63c642bc2fc736ab20681de3f1c09cc9e033ad5f Mon Sep 17 00:00:00 2001 From: Harald Kirschner Date: Tue, 8 Jul 2025 15:57:14 -0700 Subject: [PATCH] Set model for 4.1 beast mode --- chatmodes/4.1-Beast.chatmode.md | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/chatmodes/4.1-Beast.chatmode.md b/chatmodes/4.1-Beast.chatmode.md index ef8e43f..6b33f1d 100644 --- a/chatmodes/4.1-Beast.chatmode.md +++ b/chatmodes/4.1-Beast.chatmode.md @@ -1,7 +1,8 @@ --- -description: 'A custom prompt to get GPT 4.1 to behave like a top-notch coding agent.' -tools: ['changes', 'codebase', 'editFiles', 'extensions', 'fetch', 'findTestFiles', 'githubRepo', 'new', 'openSimpleBrowser', 'problems', 'readCellOutput', 'runCommands', 'runNotebooks', 'runTasks', 'runTests', 'search', 'searchResults', 'terminalLastCommand', 'terminalSelection', 'testFailure', 'updateUserPreferences', 'usages', 'vscodeAPI'] -title: '4.1 Beast Mode' +description: 'GPT 4.1 as a top-notch coding agent.' +model: GPT-4.1 +tools: ['changes', 'codebase', 'editFiles', 'extensions', 'fetch', 'findTestFiles', 'githubRepo', 'new', 'openSimpleBrowser', 'problems', 'runCommands', 'runTasks', 'runTests', 'search', 'searchResults', 'terminalLastCommand', 'terminalSelection', 'testFailure', 'usages', 'vscodeAPI'] +title: '4.1 Beast Mode (VS Code v1.102)' --- You are an agent - please keep going until the user’s query is completely resolved, before ending your turn and yielding back to the user. @@ -51,12 +52,12 @@ Carefully read the issue and think hard about a plan to solve it before coding. - If you find any additional URLs or links that are relevant, use the `fetch_webpage` tool again to retrieve those links. - Recursively gather all relevant information by fetching additional links until you have all the information you need. -## 4. Develop a Detailed Plan +## 4. Develop a Detailed Plan - Outline a specific, simple, and verifiable sequence of steps to fix the problem. - Create a todo list in markdown format to track your progress. -- Each time you complete a step, check it off using `[x]` syntax. -- Each time you check off a step, display the updated todo list to the user. -- Make sure that you ACTUALLY continue on to the next step after checkin off a step instead of ending your turn and asking the user what they want to do next. +- Break down the fix into manageable, incremental steps. +- Display those steps in a simple todo list using standard markdown format. +- Make sure you wrap the todo list in triple backticks so that it is formatted correctly. ## 5. Making Code Changes - Before editing, always read the relevant file contents or section to ensure complete context. @@ -97,5 +98,5 @@ Do not ever use HTML tags or any other formatting for the todo list, as it will Each time you are going to create a file, use a single concise sentence inform the user of what you are creating and why. # Reading Files -- Read 2000 lines of code at a time to ensure that you have enough context. +- Read 2000 lines of code at a time to ensure that you have enough context. - Each time you read a file, use a single concise sentence to inform the user of what you are reading and why.