@tencent-ai/codebuddy-code 1.1.5-next.e822df1.20250922 → 1.1.6-next.6d1298b.20250923

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tencent-ai/codebuddy-code",
-  "version": "1.1.5-next.e822df1.20250922",
+  "version": "1.1.6-next.6d1298b.20250923",
   "description": "Use CodeBuddy, Tencent's AI assistant, right from your terminal. CodeBuddy can understand your codebase, edit files, run terminal commands, and handle entire workflows for you.",
   "main": "lib/node/index.js",
   "typings": "lib/node/index.d.ts",

package/product.internal.json

@@ -15,6 +15,7 @@
         "compact"
       ],
       "tools": [
+        "Task",
         "Read",
         "LS",
         "Write",
@@ -29,8 +30,7 @@
         "WebSearch",
         "NotebookRead",
         "NotebookEdit",
-        "NotebookWrite",
-        "Task"
+        "NotebookWrite"
       ],
       "tags": [
         "cli",
@@ -203,6 +203,6 @@
   "productFeatures": {
     "BillingNotice": false
   },
-  "commit": "e822df1b2cdf8b6bc48bc3a7d820da8621e73476",
-  "date": "2025-09-21T16:02:49.571Z"
+  "commit": "6d1298bc949d22709d058156cda4d5161022802d",
+  "date": "2025-09-22T16:03:01.455Z"
 }

package/product.ioa.json

@@ -20,6 +20,7 @@
         "compact"
       ],
       "tools": [
+        "Task",
         "Read",
         "LS",
         "Write",
@@ -34,8 +35,7 @@
         "WebSearch",
         "NotebookRead",
         "NotebookEdit",
-        "NotebookWrite",
-        "Task"
+        "NotebookWrite"
       ],
       "tags": [
         "cli",
@@ -294,6 +294,6 @@
   "productFeatures": {
     "BillingNotice": false
   },
-  "commit": "e822df1b2cdf8b6bc48bc3a7d820da8621e73476",
-  "date": "2025-09-21T16:02:51.898Z"
+  "commit": "6d1298bc949d22709d058156cda4d5161022802d",
+  "date": "2025-09-22T16:03:02.785Z"
 }

package/product.json

@@ -191,7 +191,7 @@
     },
     {
       "name": "init-prompt",
-      "template": "Please analyze this codebase and create a CODEBUDDY.md file, which will be given to future instances of CodeBuddy Code to operate in this repository.\n            \nWhat to add:\n1. Commands that will be commonly used, such as how to build, lint, and run tests. Include the necessary commands to develop in this codebase, such as how to run a single test.\n2. High-level code architecture and structure so that future instances can be productive more quickly. Focus on the \"big picture\" architecture that requires reading multiple files to understand\n\nUsage notes:\n- If there's already a CODEBUDDY.md, suggest improvements to it.\n- When you make the initial CODEBUDDY.md, do not repeat yourself and do not include obvious instructions like \"Provide helpful error messages to users\", \"Write unit tests for all new utilities\", \"Never include sensitive information (API keys, tokens) in code or commits\" \n- Avoid listing every component or file structure that can be easily discovered\n- Don't include generic development practices\n- If there are Claude Code rules (in ./CLAUDE.md) or Cursor rules (in .cursor/rules/ or .cursorrules) or Copilot rules (in .github/copilot-instructions.md), make sure to include the important parts.\n- If there is a README.md, make sure to include the important parts. \n- Do not make up information such as \"Common Development Tasks\", \"Tips for Development\", \"Support and Documentation\" unless this is expressly included in other files that you read.\n- Be sure to prefix the file with the following text:\n"
+      "template": "Please analyze this codebase and create a CODEBUDDY.md file, which will be given to future instances of CodeBuddy Code to operate in this repository.\n            \nWhat to add:\n1. Commands that will be commonly used, such as how to build, lint, and run tests. Include the necessary commands to develop in this codebase, such as how to run a single test.\n2. High-level code architecture and structure so that future instances can be productive more quickly. Focus on the \"big picture\" architecture that requires reading multiple files to understand\n\nUsage notes:\n- If there's already a CODEBUDDY.md, suggest improvements to it.\n- When you make the initial CODEBUDDY.md, do not repeat yourself and do not include obvious instructions like \"Provide helpful error messages to users\", \"Write unit tests for all new utilities\", \"Never include sensitive information (API keys, tokens) in code or commits\" \n- Avoid listing every component or file structure that can be easily discovered\n- Don't include generic development practices\n- If there are Claude Code rules (in ./CLAUDE.md) or Cursor rules (in .cursor/rules/ or .cursorrules) or Copilot rules (in .github/copilot-instructions.md) or ./AGENTS.md, make sure to include the important parts.\n- If there is a README.md, make sure to include the important parts. \n- Do not make up information such as \"Common Development Tasks\", \"Tips for Development\", \"Support and Documentation\" unless this is expressly included in other files that you read.\n- Be sure to prefix the file with the following text:\n"
     },
     {
       "name": "compact-agent-prompt",
@@ -247,11 +247,11 @@
     },
     {
       "name": "tool-edit-description",
-      "template": "Performs exact string replacements in files.\n\nUsage:\n- You must use your `Read` tool at least once in the conversation before editing. This tool will error if you attempt an edit without reading the file.\n- When editing text from Read tool output, ensure you preserve the exact indentation (tabs/spaces) as it appears AFTER the line number prefix. The line number prefix format is: spaces + line number + tab. Everything after that tab is the actual file content to match. Never include any part of the line number prefix in the old_string or new_string.\n- ALWAYS prefer editing existing files in the codebase. NEVER write new files unless explicitly required.\n- Only use emojis if the user explicitly requests it. Avoid adding emojis to files unless asked.\n- The edit will FAIL if `old_string` is not unique in the file. Either provide a larger string with more surrounding context to make it unique or use `replace_all` to change every instance of `old_string`.\n- Use `replace_all` for replacing and renaming strings across the file. This parameter is useful if you want to rename a variable for instance.\n\nCRITICAL REQUIREMENTS:\n- The tool will fail if `old_string` and `new_string` are the same\n- The tool will fail if `old_string` doesn't match the file contents exactly (including whitespace)\n- This tool is for MODIFYING content only - if `old_string` equals `new_string`, you are not making any changes\n\nWARNING:\n- NEVER use this tool to \"verify\" content or as a no-op operation\n- NEVER pass identical values for `old_string` and `new_string`\n- If you don't need to change anything, don't use this tool\n"
+      "template": "Performs exact string replacements in files.\n\nUsage:\n- You must use your `Read` tool at least once in the conversation before editing. This tool will error if you attempt an edit without reading the file.\n- When editing text from Read tool output, ensure you preserve the exact indentation (tabs/spaces) as it appears AFTER the line number prefix. The line number prefix format is: spaces + line number + tab. Everything after that tab is the actual file content to match. Never include any part of the line number prefix in the old_string or new_string.\n- ALWAYS prefer editing existing files in the codebase. NEVER write new files unless explicitly required.\n- Only use emojis if the user explicitly requests it. Avoid adding emojis to files unless asked.\n- The edit will FAIL if `old_string` is not unique in the file. Either provide a larger string with more surrounding context to make it unique or use `replace_all` to change every instance of `old_string`.\n- Use `replace_all` for replacing and renaming strings across the file. This parameter is useful if you want to rename a variable for instance.\n\nCRITICAL REQUIREMENTS:\n- The tool will fail if `old_string` and `new_string` are the same\n- The tool will fail if `old_string` doesn't match the file contents exactly (including whitespace)\n- This tool is for MODIFYING content only - if `old_string` equals `new_string`, you are not making any changes\n\nWARNING:\n- NEVER use this tool to \"verify\" content or as a no-op operation\n- NEVER pass identical values for `old_string` and `new_string`\n- If you don't need to change anything, don't use this tool\n- Make sure the text matches exactly, including whitespace\n"
     },
     {
       "name": "tool-multiedit-description",
-      "template": "This is a tool for making multiple edits to a single file in one operation. It is built on top of the Edit tool and allows you to perform multiple find-and-replace operations efficiently. Prefer this tool over the Edit tool when you need to make multiple edits to the same file.\n\nBefore using this tool:\n\n1. Use the Read tool to understand the file's contents and context\n2. Verify the directory path is correct\n\nTo make multiple file edits, provide the following:\n1. file_path: The absolute path to the file to modify (must be absolute, not relative)\n2. edits: An array of edit operations to perform, where each edit contains:\n   - old_string: The text to replace (must match the file contents exactly, including all whitespace and indentation)\n   - new_string: The edited text to replace the old_string\n   - replace_all: Replace all occurences of old_string. This parameter is optional and defaults to false.\n\nIMPORTANT:\n- All edits are applied in sequence, in the order they are provided\n- Each edit operates on the result of the previous edit\n- All edits must be valid for the operation to succeed - if any edit fails, none will be applied\n- This tool is ideal when you need to make several changes to different parts of the same file\n- For Jupyter notebooks (.ipynb files), use the NotebookEdit instead\n\nCRITICAL REQUIREMENTS:\n1. All edits follow the same requirements as the single Edit tool\n2. The edits are atomic - either all succeed or none are applied\n3. Plan your edits carefully to avoid conflicts between sequential operations\n\nWARNING:\n- The tool will fail if edits.old_string doesn't match the file contents exactly (including whitespace)\n- The tool will fail if edits.old_string and edits.new_string are the same\n- Since edits are applied in sequence, ensure that earlier edits don't affect the text that later edits are trying to find\n\nWhen making edits:\n- Ensure all edits result in idiomatic, correct code\n- Do not leave the code in a broken state\n- Always use absolute file paths (starting with /)\n- Only use emojis if the user explicitly requests it. Avoid adding emojis to files unless asked.\n- Use replace_all for replacing and renaming strings across the file. This parameter is useful if you want to rename a variable for instance.\n\nIf you want to create a new file, use:\n- A new file path, including dir name if needed\n- First edit: empty old_string and the new file's contents as new_string\n- Subsequent edits: normal edit operations on the created content\n"
+      "template": "This is a tool for making multiple edits to a single file in one operation. It is built on top of the Edit tool and allows you to perform multiple find-and-replace operations efficiently. Prefer this tool over the Edit tool when you need to make multiple edits to the same file.\n\nBefore using this tool:\n\n1. Use the Read tool to understand the file's contents and context\n2. Verify the directory path is correct\n\nTo make multiple file edits, provide the following:\n1. file_path: The absolute path to the file to modify (must be absolute, not relative)\n2. edits: An array of edit operations to perform, where each edit contains:\n   - old_string: The text to replace (must match the file contents exactly, including all whitespace and indentation)\n   - new_string: The edited text to replace the old_string\n   - replace_all: Replace all occurences of old_string. This parameter is optional and defaults to false.\n\nIMPORTANT:\n- All edits are applied in sequence, in the order they are provided\n- Each edit operates on the result of the previous edit\n- All edits must be valid for the operation to succeed - if any edit fails, none will be applied\n- This tool is ideal when you need to make several changes to different parts of the same file\n- For Jupyter notebooks (.ipynb files), use the NotebookEdit instead\n\nCRITICAL REQUIREMENTS:\n1. All edits follow the same requirements as the single Edit tool\n2. The edits are atomic - either all succeed or none are applied\n3. Plan your edits carefully to avoid conflicts between sequential operations\n\nWARNING:\n- The tool will fail if edits.old_string doesn't match the file contents exactly (including whitespace)\n- The tool will fail if edits.old_string and edits.new_string are the same\n- Since edits are applied in sequence, ensure that earlier edits don't affect the text that later edits are trying to find\n- Make sure the text matches exactly, including whitespace\n\nWhen making edits:\n- Ensure all edits result in idiomatic, correct code\n- Do not leave the code in a broken state\n- Always use absolute file paths (starting with /)\n- Only use emojis if the user explicitly requests it. Avoid adding emojis to files unless asked.\n- Use replace_all for replacing and renaming strings across the file. This parameter is useful if you want to rename a variable for instance.\n\nIf you want to create a new file, use:\n- A new file path, including dir name if needed\n- First edit: empty old_string and the new file's contents as new_string\n- Subsequent edits: normal edit operations on the created content\n"
     },
     {
       "name": "tool-write-description",
@@ -336,6 +336,7 @@
         "compact"
       ],
       "tools": [
+        "Task",
         "Read",
         "LS",
         "Write",
@@ -350,8 +351,7 @@
         "WebSearch",
         "NotebookRead",
         "NotebookEdit",
-        "NotebookWrite",
-        "Task"
+        "NotebookWrite"
       ],
       "tags": [
         "cli",
@@ -469,6 +469,7 @@
     "CodeAction": true,
     "Mcp": true,
     "McpMarket": true,
+    "MemoryManagement": true,
     "McpInstallationGuide": true,
     "SelectImage": false,
     "Aegis": true,
@@ -569,6 +570,6 @@
       "description": "tool-task-description"
     }
   ],
-  "commit": "e822df1b2cdf8b6bc48bc3a7d820da8621e73476",
-  "date": "2025-09-21T16:02:48.161Z"
+  "commit": "6d1298bc949d22709d058156cda4d5161022802d",
+  "date": "2025-09-22T16:03:00.137Z"
 }