Rename 'write_to_file' tool to 'create_file' across codebase and fixed tests

Author: Roo Code

CHANGELOG.md

@@ -479,7 +479,7 @@ Join us at https://www.reddit.com/r/RooCode to share your custom modes and be pa
 ## [2.1.14]
 
 - Fix bug where diffs were not being applied correctly and try Aider's [unified diff prompt](https://github.com/Aider-AI/aider/blob/3995accd0ca71cea90ef76d516837f8c2731b9fe/aider/coders/udiff_prompts.py#L75-L105)
-- If diffs are enabled, automatically reject write_to_file commands that lead to truncated output
+- If diffs are enabled, automatically reject create_file commands that lead to truncated output
 
 ## [2.1.13]
 

src/api/transform/o1-format.ts

@@ -67,13 +67,13 @@ Description: Perform a regex search across files in a specified directory, provi
 </read_file>
 Description: Read the contents of a file at the specified path. Use this when you need to examine the contents of an existing file, for example to analyze code, review text files, or extract information from configuration files. Automatically extracts raw text from PDF and DOCX files. May not be suitable for other types of binary files, as it returns the raw content as a string.
 
-6. write_to_file:
-<write_to_file>
+6. create_file:
+<create_file>
 <path>File path here</path>
 <content>
 Your file content here
 </content>
-</write_to_file>
+</create_file>
 Description: Write content to a file at the specified path. If the file exists, it will be overwritten with the provided content. If the file doesn't exist, it will be created. Always provide the full intended content of the file, without any truncation. This tool will automatically create any directories needed to write the file.
 
 7. ask_followup_question:
@@ -107,7 +107,7 @@ Example 2: Using multiple tools
 
 Let's create two new configuration files for the web application: one for the frontend and one for the backend.
 
-<write_to_file>
+<create_file>
 <path>./frontend-config.json</path>
 <content>
 {
@@ -125,9 +125,9 @@ Let's create two new configuration files for the web application: one for the fr
   "version": "1.0.0"
 }
 </content>
-</write_to_file>
+</create_file>
 
-<write_to_file>
+<create_file>
 <path>./backend-config.yaml</path>
 <content>
 database:
@@ -154,7 +154,7 @@ externalServices:
   emailProvider: sendgrid
   storageProvider: aws-s3
 </content>
-</write_to_file>
+</create_file>
 
 Example 3: Asking a follow-up question
 
@@ -239,7 +239,7 @@ const toolNames = [
 	"list_code_definition_names",
 	"search_files",
 	"read_file",
-	"write_to_file",
+	"create_file",
 	"ask_followup_question",
 	"attempt_completion",
 ]
@@ -331,7 +331,7 @@ function validateToolInput(toolName: string, tool_input: Record<string, string>)
 			return "path" in tool_input
 		case "search_files":
 			return "path" in tool_input && "regex" in tool_input
-		case "write_to_file":
+		case "create_file":
 			return "path" in tool_input && "content" in tool_input
 		case "ask_followup_question":
 			return "question" in tool_input
@@ -349,10 +349,10 @@ function validateToolInput(toolName: string, tool_input: Record<string, string>)
 //   <command>ls -la</command>
 // </execute_command>
 
-// <write_to_file>
+// <create_file>
 //   <path>./example.txt</path>
 //   <content>Hello, World!</content>
-// </write_to_file>`;
+// </create_file>`;
 //
 // const { normalText, toolCalls } = parseAIResponse(aiResponse);
 // console.log(normalText);

src/core/Cline.ts

@@ -698,7 +698,7 @@ export class Cline {
 			text:
 				`[TASK RESUMPTION] This task was interrupted ${agoText}. It may or may not be complete, so please reassess the task context. Be aware that the project state may have changed since then. The current working directory is now '${cwd.toPosix()}'. If the task has not been completed, retry the last step before interruption and proceed with completing the task.\n\nNote: If you previously attempted a tool use that the user did not provide a result for, you should assume the tool use was not successful and assess whether you should retry. If the last tool was a browser_action, the browser has been closed and you must launch a new browser if needed.${
 					wasRecent
-						? "\n\nIMPORTANT: If the last tool use was a write_to_file that was interrupted, the file was reverted back to its original state before the interrupted edit, and you do NOT need to re-read the file as you already have its up-to-date contents."
+						? "\n\nIMPORTANT: If the last tool use was a create_file that was interrupted, the file was reverted back to its original state before the interrupted edit, and you do NOT need to re-read the file as you already have its up-to-date contents."
 						: ""
 				}` +
 				(responseText
@@ -1102,7 +1102,7 @@ export class Cline {
 							return `[${block.name} for '${block.params.command}']`
 						case "read_file":
 							return `[${block.name} for '${block.params.path}']`
-						case "write_to_file":
+						case "create_file":
 							return `[${block.name} for '${block.params.path}']`
 						case "edit_file":
 							return `[${block.name} for '${block.params.path}']`
@@ -1267,7 +1267,7 @@ export class Cline {
 				}
 
 				switch (block.name) {
-					case "write_to_file": {
+					case "create_file": {
 						const relPath: string | undefined = block.params.path
 						let newContent: string | undefined = block.params.content
 						let predictedLineCount: number | undefined = parseInt(block.params.line_count ?? "0")
@@ -1332,20 +1332,20 @@ export class Cline {
 							} else {
 								if (!relPath) {
 									this.consecutiveMistakeCount++
-									pushToolResult(await this.sayAndCreateMissingParamError("write_to_file", "path"))
+									pushToolResult(await this.sayAndCreateMissingParamError("create_file", "path"))
 									await this.diffViewProvider.reset()
 									break
 								}
 								if (!newContent) {
 									this.consecutiveMistakeCount++
-									pushToolResult(await this.sayAndCreateMissingParamError("write_to_file", "content"))
+									pushToolResult(await this.sayAndCreateMissingParamError("create_file", "content"))
 									await this.diffViewProvider.reset()
 									break
 								}
 								if (!predictedLineCount) {
 									this.consecutiveMistakeCount++
 									pushToolResult(
-										await this.sayAndCreateMissingParamError("write_to_file", "line_count"),
+										await this.sayAndCreateMissingParamError("create_file", "line_count"),
 									)
 									await this.diffViewProvider.reset()
 									break
@@ -2194,7 +2194,7 @@ export class Cline {
 											formatResponse.toolResult(
 												`The browser action has been executed. The console logs and screenshot have been captured for your analysis.\n\nConsole logs:\n${
 													browserActionResult.logs || "(No new logs)"
-												}\n\n(REMEMBER: if you need to proceed to using non-\`browser_action\` tools or launch a new browser, you MUST first close this browser. For example, if after analyzing the logs and screenshot you need to edit a file, you must first close the browser before you can use the write_to_file tool.)`,
+												}\n\n(REMEMBER: if you need to proceed to using non-\`browser_action\` tools or launch a new browser, you MUST first close this browser. For example, if after analyzing the logs and screenshot you need to edit a file, you must first close the browser before you can use the create_file tool.)`,
 												browserActionResult.screenshot ? [browserActionResult.screenshot] : [],
 											),
 										)
@@ -2711,7 +2711,7 @@ export class Cline {
 
 		/*
 		Seeing out of bounds is fine, it means that the next too call is being built up and ready to add to assistantMessageContent to present.
-		When you see the UI inactive during this, it means that a tool is breaking without presenting any UI. For example the write_to_file tool was breaking when relpath was undefined, and for invalid relpath it never presented UI.
+		When you see the UI inactive during this, it means that a tool is breaking without presenting any UI. For example the create_file tool was breaking when relpath was undefined, and for invalid relpath it never presented UI.
 		*/
 		this.presentAssistantMessageLocked = false // this needs to be placed here, if not then calling this.presentAssistantMessage below would fail (sometimes) since it's locked
 		// NOTE: when tool is rejected, iterator stream is interrupted and it waits for userMessageContentReady to be true. Future calls to present will skip execution since didRejectTool and iterate until contentIndex is set to message length and it sets userMessageContentReady to true itself (instead of preemptively doing it in iterator)
@@ -3261,7 +3261,7 @@ export class Cline {
 
 		// Add warning if not in code mode
 		if (
-			!isToolAllowedForMode("write_to_file", currentMode, customModes ?? [], {
+			!isToolAllowedForMode("create_file", currentMode, customModes ?? [], {
 				edit_file: this.diffEnabled,
 			}) &&
 			!isToolAllowedForMode("edit_file", currentMode, customModes ?? [], { edit_file: this.diffEnabled })

src/core/__tests__/mode-validator.test.ts

@@ -59,7 +59,7 @@ describe("mode-validator", () => {
 				]
 				// Should allow tools from read and edit groups
 				expect(isToolAllowedForMode("read_file", "custom-mode", customModes)).toBe(true)
-				expect(isToolAllowedForMode("write_to_file", "custom-mode", customModes)).toBe(true)
+				expect(isToolAllowedForMode("create_file", "custom-mode", customModes)).toBe(true)
 				// Should not allow tools from other groups
 				expect(isToolAllowedForMode("execute_command", "custom-mode", customModes)).toBe(false)
 			})
@@ -76,7 +76,7 @@ describe("mode-validator", () => {
 				// Should allow tools from read group
 				expect(isToolAllowedForMode("read_file", codeMode, customModes)).toBe(true)
 				// Should not allow tools from other groups
-				expect(isToolAllowedForMode("write_to_file", codeMode, customModes)).toBe(false)
+				expect(isToolAllowedForMode("create_file", codeMode, customModes)).toBe(false)
 			})
 
 			it("respects tool requirements in custom modes", () => {
@@ -94,7 +94,7 @@ describe("mode-validator", () => {
 				expect(isToolAllowedForMode("edit_file", "custom-mode", customModes, requirements)).toBe(false)
 
 				// Should allow other edit tools
-				expect(isToolAllowedForMode("write_to_file", "custom-mode", customModes, requirements)).toBe(true)
+				expect(isToolAllowedForMode("create_file", "custom-mode", customModes, requirements)).toBe(true)
 			})
 		})
 

src/core/assistant-message/index.ts

@@ -11,7 +11,7 @@ export interface TextContent {
 export const toolUseNames = [
 	"execute_command",
 	"read_file",
-	"write_to_file",
+	"create_file",
 	"edit_file",
 	"insert_content",
 	"search_and_replace",
@@ -80,7 +80,7 @@ export interface ReadFileToolUse extends ToolUse {
 }
 
 export interface WriteToFileToolUse extends ToolUse {
-	name: "write_to_file"
+	name: "create_file"
 	params: Partial<Pick<Record<ToolParamName, string>, "path" | "content" | "line_count">>
 }
 

src/core/assistant-message/parse-assistant-message.ts

@@ -61,9 +61,9 @@ export function parseAssistantMessage(assistantMessage: string) {
 
 				// there's no current param, and not starting a new param
 
-				// special case for write_to_file where file contents could contain the closing tag, in which case the param would have closed and we end up with the rest of the file contents here. To work around this, we get the string between the starting content tag and the LAST content tag.
+				// special case for create_file where file contents could contain the closing tag, in which case the param would have closed and we end up with the rest of the file contents here. To work around this, we get the string between the starting content tag and the LAST content tag.
 				const contentParamName: ToolParamName = "content"
-				if (currentToolUse.name === "write_to_file" && accumulator.endsWith(`</${contentParamName}>`)) {
+				if (currentToolUse.name === "create_file" && accumulator.endsWith(`</${contentParamName}>`)) {
 					const toolContent = accumulator.slice(currentToolUseStartIndex)
 					const contentStartTag = `<${contentParamName}>`
 					const contentEndTag = `</${contentParamName}>`