update gpt51CodexPrompt as suggested by openAI #2195
Conversation
There was a problem hiding this comment.
Pull request overview
This PR updates the GPT-5.1 Codex prompt template according to new recommendations from OpenAI. The changes restructure the prompt to emphasize parallelism in tool usage, add guidance for frontend design tasks, and provide clearer error handling instructions.
Key Changes:
- Added new sections for file exploration/reading with emphasis on parallel tool execution via
multi_tool_use.parallel - Added frontend design guidance to avoid generic "AI slop" and encourage intentional, bold design choices
- Replaced generic tool usage and special request handling with more specific error handling guidance
You can also share your feedback on Copilot code review for a chance to win a $100 gift card. Take the survey.
| <Tag name='Exploration_and_reading_files'> | ||
| - Think first. Before any tool call, decide ALL files/resources you will need.<br /> | ||
| - Batch everything. If you need multiple files (even from different places), read them together.<br /> | ||
| - multi_tool_use.parallel Use `multi_tool_use.parallel` to parallelize tool calls and only this.<br /> |
There was a problem hiding this comment.
Incomplete sentence on line 38. The line starts with "multi_tool_use.parallel Use multi_tool_use.parallel..." which appears to have text before "Use" that doesn't form a proper sentence. Should likely be either "- Use multi_tool_use.parallel to parallelize tool calls and only this." or restructured for clarity.
| - multi_tool_use.parallel Use `multi_tool_use.parallel` to parallelize tool calls and only this.<br /> | |
| - Use `multi_tool_use.parallel` to parallelize tool calls and only this.<br /> |
| - While you are working, you might notice unexpected changes that you didn't make. If this happens, STOP IMMEDIATELY and ask the user how they would like to proceed.<br /> | ||
| - **NEVER** use destructive commands like `git reset --hard` or `git checkout --` unless specifically requested or approved by the user.<br /> | ||
| </Tag> | ||
| <Tag name='Exploration_and_reading_files'> |
There was a problem hiding this comment.
The tag name 'Exploration_and_reading_files' uses underscores and starts with a capital letter, which is inconsistent with other tag names in this file (e.g., 'editing_constraints', 'tool_use', 'frontend_tasks'). For consistency, consider using 'exploration_and_reading_files' instead.
| <Tag name='Exploration_and_reading_files'> | |
| <Tag name='exploration_and_reading_files'> |
| - Motion: Use a few meaningful animations (page-load, staggered reveals) instead of generic micro-motions.<br /> | ||
| - Background: Don't rely on flat, single-color backgrounds; use gradients, shapes, or subtle patterns to build atmosphere.<br /> | ||
| - Overall: Avoid boilerplate layouts and interchangeable UI patterns. Vary themes, type families, and visual languages across outputs.<br /> | ||
| - Ensure the page loads properly on both desktop and mobile<br /> |
There was a problem hiding this comment.
Missing period at the end of the sentence. The line should end with a period for consistency with other bullet points in the prompt that all end with periods.
| - Ensure the page loads properly on both desktop and mobile<br /> | |
| - Ensure the page loads properly on both desktop and mobile.<br /> |
| - {tools[ToolName.CoreManageTodoList] && <> | ||
| <br /> |
There was a problem hiding this comment.
The conditional rendering logic changed from wrapping the entire tool_use content to only wrapping the CoreManageTodoList section. This means the opening - {tools[ToolName.CoreManageTodoList] && <> on line 48 creates a bullet point that starts with a conditional JSX expression, which will render as "- " when the condition is false, leaving an empty bullet point. Consider restructuring to avoid rendering anything when the tool is not available, or move the - inside the conditional block.
| - {tools[ToolName.CoreManageTodoList] && <> | |
| <br /> | |
| {tools[ToolName.CoreManageTodoList] && <> | |
| - <br /> |
|
@dileepyavan looks like some tests failed |
| </>} | ||
| </Tag> | ||
| <Tag name='special_user_requests'> | ||
| - If the user makes a simple request (such as asking for the time) which you can fulfill by running a terminal command (such as `date`), you should do so.<br /> |
There was a problem hiding this comment.
Did you mean to delete this section?
src/extension/prompt/node/test/__snapshots__/defaultIntentRequestHandler.spec.ts.snap
Show resolved
Hide resolved
dileepyavan
force-pushed
the
DileepY/openAI_modelUpdate
branch
from
b9ff73f to
7156b94
Compare
Updating prompts for new openAI Model