chore(prompts): remove outdated browser session persistence guidance

Author: hannesrudolph

src/core/prompts/sections/rules.ts

@@ -91,14 +91,6 @@ ${getEditingInstructions(diffStrategy)}
 - When presented with images, utilize your vision capabilities to thoroughly examine them and extract meaningful information. Incorporate these insights into your thought process as you accomplish the user's task.
 - At the end of each user message, you will automatically receive environment_details. This information is not written by the user themselves, but is auto-generated to provide potentially relevant context about the project structure and environment. While this information can be valuable for understanding the project context, do not treat it as a direct part of the user's request or response. Use it to inform your actions and decisions, but don't assume the user is explicitly asking about or referring to this information unless they clearly do so in their message. When using environment_details, explain your actions clearly to ensure the user understands, as they may not be aware of these details.
 - Before executing commands, check the "Actively Running Terminals" section in environment_details. If present, consider how these active processes might impact your task. For example, if a local development server is already running, you wouldn't need to start it again. If no active terminals are listed, proceed with command execution as normal.
-- MCP operations should be used one at a time, similar to other tool usage. Wait for confirmation of success before proceeding with additional operations.${
-		supportsComputerUse
-			? "\n- **BROWSER SESSION PERSISTENCE**: When a browser session is active (launched but not closed), you can freely use ask_followup_question, attempt_completion, and ANY other tools WITHOUT closing the browser. The browser remains open in the background and you can return to browser_action at any time. DO NOT close the browser just because you want to ask a question or use another tool - this is explicitly allowed and the browser will persist."
-			: ""
-	}
-- It is critical you wait for the user's response after each tool use, in order to confirm the success of the tool use. For example, if asked to make a todo app, you would create a file, wait for the user's response it was created successfully, then create another file if needed, wait for the user's response it was created successfully, etc.${
-		supportsComputerUse
-			? " Then if you want to test your work, you might use browser_action to launch the site, wait for the user's response confirming the site was launched along with a screenshot, then perhaps e.g., click a button to test functionality if needed, wait for the user's response confirming the button was clicked along with a screenshot of the new state. The browser will remain open throughout testing - you can ask questions, make file edits, or perform additional browser actions as needed. Only close the browser when you're completely finished with all testing."
-			: ""
-	}`
+- MCP operations should be used one at a time, similar to other tool usage. Wait for confirmation of success before proceeding with additional operations.
+- It is critical you wait for the user's response after each tool use, in order to confirm the success of the tool use. For example, if asked to make a todo app, you would create a file, wait for the user's response it was created successfully, then create another file if needed, wait for the user's response it was created successfully, etc.`
 }