Fixes

src/core/prompts/system.ts

@@ -41,6 +41,7 @@ RULES
 - Do not ask for more information than necessary. Use the tools provided to accomplish the user's request efficiently and effectively. When you've completed your task, you must use the attempt_completion tool to present the result to the user. The user may provide feedback, which you can use to make improvements and try again.
 - You are only allowed to ask the user questions using the ask_followup_question tool. Use this tool only when you need additional details to complete a task, and be sure to use a clear and concise question that will help you move forward with the task. However if you can use the available tools to avoid having to ask the user questions, you should do so. For example, if the user mentions a file that may be in an outside directory like the Desktop, you should use the list_files tool to list the files in the Desktop and check if the file they are talking about is there, rather than asking the user to provide the file path themselves.
 - When executing commands, if you don't see the expected output, assume the terminal executed the command successfully and proceed with the task. The user's terminal may be unable to stream the output back properly. If you absolutely need to see the actual terminal output, use the ask_followup_question tool to request the user to copy and paste it back to you.
+- The user may provide a file's contents directly in their message, in which case you shouldn't use the read_file tool to get the file contents again since you already have it.
 - Your goal is to try to accomplish the user's task, NOT engage in a back and forth conversation.
 - NEVER end completion_attempt with a question or request to engage in further conversation! Formulate the end of your result in a way that is final and does not require further input from the user. 
 - You are STRICTLY FORBIDDEN from starting your messages with "Great", "Certainly", "Okay", "Sure". You should NOT be conversational in your responses, but rather direct and to the point. For example if you've completed a step and received its results, you should NOT say "Great, I've updated the CSS" but instead something like "I've updated the CSS" or "I've added the component as specified" etc.

webview-ui/src/components/settings/OpenRouterModelPicker.tsx

@@ -207,11 +207,17 @@ const OpenRouterModelPicker: React.FC = () => {
 						marginTop: 0,
 						color: "var(--vscode-descriptionForeground)",
 					}}>
-					You can use{" "}
+					The extension automatically fetches the latest list of models available on{" "}
 					<VSCodeLink style={{ display: "inline", fontSize: "inherit" }} href="https://openrouter.ai/models">
-						any model on OpenRouter
-					</VSCodeLink>{" "}
-					with Cline. (Try searching for "free" to see if there are free models currently available.)
+						OpenRouter.
+					</VSCodeLink>
+					If you're unsure which model to choose, Cline works best with{" "}
+					<VSCodeLink
+						style={{ display: "inline", fontSize: "inherit" }}
+						onClick={() => handleModelChange("anthropic/claude-3.5-sonnet:beta")}>
+						anthropic/claude-3.5-sonnet:beta.
+					</VSCodeLink>
+					You can also try searching for "free" to see if there are any free models currently available.
 				</p>
 			)}
 		</>

webview-ui/src/utils/validate.ts

@@ -61,7 +61,7 @@ export function validateModelId(
 			case "openrouter":
 				const modelId = apiConfiguration.openRouterModelId
 				if (!modelId) {
-					return "You must provide a model ID. If you're not sure which model to choose, Cline works best with Claude 3.5 Sonnet (anthropic/claude-3.5-sonnet)."
+					return "You must provide a model ID."
 				}
 				if (openRouterModels && !Object.keys(openRouterModels).includes(modelId)) {
 					return "The model ID you provided is not available. Please choose a different model."