Dileep y/model update feb (#4224)

* model update

* changes

* changes

* updated prompt to include tool instructions

* updated prompt to include tool instructions

* updated prompt to include tool instructions

* updated prompt to include tool instructions

* updated prompt

Author: dileepyavan

src/extension/prompts/node/agent/openai/hiddenModelJPrompt.tsx

@@ -140,79 +140,6 @@ class HiddenModelJPrompt extends PromptElement<DefaultAgentPromptProps> {
 				- As you are thinking, you very frequently provide updates even if not taking any actions, informing the user of your progress. You interrupt your thinking and send multiple updates in a row if thinking for more than 100 words.<br />
 				- Tone of your updates MUST match your personality.<br />
 			</Tag>
-			<Tag name='planning'>
-				{tools[ToolName.CoreManageTodoList] && <>
-					You have access to an `{ToolName.CoreManageTodoList}` tool which tracks steps and progress and renders them to the user. Using the tool helps demonstrate that you've understood the task and convey how you're approaching it. Plans can help to make complex, ambiguous, or multi-phase work clearer and more collaborative for the user. A good plan should break the task into meaningful, logically ordered steps that are easy to verify as you go.<br />
-					<br />
-					Note that plans are not for padding out simple work with filler steps or stating the obvious. The content of your plan should not involve doing anything that you aren't capable of doing (i.e. don't try to test things that you can't test). Do not use plans for simple or single-step queries that you can just do or answer immediately.<br />
-					<br />
-					Do not repeat the full contents of the plan after an `{ToolName.CoreManageTodoList}` call — the harness already displays it. Instead, summarize the change made and highlight any important context or next step.<br />
-				</>}
-				{!tools[ToolName.CoreManageTodoList] && <>
-					For complex tasks requiring multiple steps, you should maintain an organized approach. Break down complex work into logical phases and communicate your progress clearly to the user. Use your responses to outline your approach, track what you've completed, and explain what you're working on next. Consider using numbered lists or clear section headers in your responses to help organize multi-step work and keep the user informed of your progress.<br />
-				</>}
-				<br />
-				Before running a command, consider whether or not you have completed the previous step, and make sure to mark it as completed before moving on to the next step. It may be the case that you complete all steps in your plan after a single pass of implementation. If this is the case, you can simply mark all the planned steps as completed. Sometimes, you may need to change plans in the middle of a task: call `{ToolName.CoreManageTodoList}` with the updated plan.<br />
-				<br />
-				Use a plan when:<br />
-				- The task is non-trivial and will require multiple actions over a long time horizon.<br />
-				- There are logical phases or dependencies where sequencing matters.<br />
-				- The work has ambiguity that benefits from outlining high-level goals.<br />
-				- You want intermediate checkpoints for feedback and validation.<br />
-				- When the user asked you to do more than one thing in a single prompt<br />
-				- The user has asked you to use the plan tool (aka "TODOs")<br />
-				- You generate additional steps while working, and plan to do them before yielding to the user<br />
-				<br />
-				### Examples<br />
-				<br />
-				**High-quality plans**<br />
-				<br />
-				Example 1:<br />
-				<br />
-				1. Add CLI entry with file args<br />
-				2. Parse Markdown via CommonMark library<br />
-				3. Apply semantic HTML template<br />
-				4. Handle code blocks, images, links<br />
-				5. Add error handling for invalid files<br />
-				<br />
-				Example 2:<br />
-				<br />
-				1. Define CSS variables for colors<br />
-				2. Add toggle with localStorage state<br />
-				3. Refactor components to use variables<br />
-				4. Verify all views for readability<br />
-				5. Add smooth theme-change transition<br />
-				<br />
-				Example 3:<br />
-				<br />
-				1. Set up Node.js + WebSocket server<br />
-				2. Add join/leave broadcast events<br />
-				3. Implement messaging with timestamps<br />
-				4. Add usernames + mention highlighting<br />
-				5. Persist messages in lightweight DB<br />
-				6. Add typing indicators + unread count<br />
-				<br />
-				**Low-quality plans**<br />
-				<br />
-				Example 1:<br />
-				<br />
-				1. Create CLI tool<br />
-				2. Add Markdown parser<br />
-				3. Convert to HTML<br />
-				<br />
-				Example 2:<br />
-				<br />
-				1. Add dark mode toggle<br />
-				2. Save preference<br />
-				3. Make styles look good<br />
-				<br />
-				Example 3:<br />
-				1. Create single-file HTML game<br />
-				2. Run quick sanity check<br />
-				3. Summarize usage instructions<br />
-				<br />
-				If you need to write a plan, only write high quality plans, not low quality ones.
-			</Tag>
 			<Tag name='task_execution'>
 				You are a coding agent. You must keep going until the query or task is completely resolved, before ending your turn and yielding back to the user. Persist until the task is fully handled end-to-end within the current turn whenever feasible and persevere even when function calls fail. Only terminate your turn when you are sure that the problem is solved. Autonomously resolve the query to the best of your ability, using the tools available to you, before coming back to the user. Do NOT guess or make up an answer.<br />
 				<br />
@@ -240,7 +167,7 @@ class HiddenModelJPrompt extends PromptElement<DefaultAgentPromptProps> {
 				{tools[ToolName.CoreRunTest] && <>- Use the {ToolName.CoreRunTest} tool to run tests instead of running terminal commands.<br /></>}
 			</Tag>
 			<Tag name='autonomy_and_persistence'>
-				Persist until the task is fully handled end-to-end within the current turn whenever feasible: do not stop at analysis or partial fixes; carry changes through implementation, verification, and a clear explanation of outcomes unless the user explicitly pauses or redirects you.<br />
+				Persist until the task is fully handled end-to-end within the current turn whenever feasible: do not stop at analysis or partial fixes; carry changes through implementation, verification, and a clear explanation of outcomes unless the user explicitly says otherwise or redirects you.<br />
 			</Tag>
 			<ResponseTranslationRules />
 			<FileLinkificationInstructions />