@tencent-ai/codebuddy-code 1.12.0 → 1.14.0-next.bb57cef.20251017

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tencent-ai/codebuddy-code",
-  "version": "1.12.0",
+  "version": "1.14.0-next.bb57cef.20251017",
   "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",
@@ -30,7 +30,8 @@
     "url": "https://cnb.cool/codebuddy/codebuddy-code/-/issues"
   },
   "publishConfig": {
-    "access": "public"
+    "access": "public",
+    "tag": "next"
   },
   "scripts": {},
   "devDependencies": {}

package/product.internal.json

@@ -156,6 +156,6 @@
   "productFeatures": {
     "BillingNotice": false
   },
-  "commit": "89fbe616fdec4c4a834f849dfe92000d11736c5b",
-  "date": "2025-10-14T09:39:28.083Z"
+  "commit": "bb57cef9419ef2c3598789e96e1fd21cc458904b",
+  "date": "2025-10-16T16:05:28.106Z"
 }

package/product.ioa.json

@@ -287,6 +287,6 @@
   "productFeatures": {
     "BillingNotice": false
   },
-  "commit": "89fbe616fdec4c4a834f849dfe92000d11736c5b",
-  "date": "2025-10-14T09:39:29.323Z"
+  "commit": "bb57cef9419ef2c3598789e96e1fd21cc458904b",
+  "date": "2025-10-16T16:05:29.350Z"
 }

package/product.json

@@ -10,6 +10,12 @@
   "platform": "CLI",
   "endpoint": "https://www.codebuddy.ai",
   "stagingEndpoint": "https://staging-codebuddy.tencent.com",
+  "officialEndpoints": [
+    "https://copilot.tencent.com",
+    "https://staging-copilot.tencent.com",
+    "https://www.codebuddy.ai",
+    "https://staging-codebuddy.tencent.com"
+  ],
   "authentication": {
     "id": "Tencent-Cloud.coding-copilot",
     "type": "cli-external-link",
@@ -25,9 +31,17 @@
         "copilot.tencent.com",
         "staging-copilot.tencent.com"
       ],
+      "externalDomain": [
+        "www.codebuddy.ai",
+        "staging-codebuddy.tencent.com"
+      ],
       "iOADomain": [
         "tencent.sso.copilot.tencent.com",
         "tencent.sso.copilot-staging.tencent.com"
+      ],
+      "cloudHostedDomain": [
+        "*.sso.copilot.tencent.com",
+        "*.sso.copilot-staging.tencent.com"
       ]
     }
   },
@@ -208,7 +222,7 @@
     },
     {
       "name": "init-prompt",
-      "template": "Please analyze this codebase and create a CODEBUDDY.md file, which will be given to future instances of Terminal Assistant Agent 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```\n# CODEBUDDY.md This file provides guidance to CodeBuddy Code when working with code in this repository.\n```\n"
+      "template": "Please analyze this codebase and create a CODEBUDDY.md file, which will be given to future instances of Terminal Assistant Agent 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- First check if there's already an AGENTS.md file in the current directory. If it exists, DO NOT create a new CODEBUDDY.md file. Instead, suggest improvements to the existing AGENTS.md file.\n- If there's already a CODEBUDDY.md but no AGENTS.md, suggest improvements to the existing CODEBUDDY.md.\n- If there's already a AGENTS.md but no CODEBUDDY.md, suggest improvements to the existing AGENTS.md.\n- When creating a new file, create CODEBUDDY.md (not AGENTS.md) if neither exists.\n- When you make the initial file, 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```\n# CODEBUDDY.md This file provides guidance to CodeBuddy Code when working with code in this repository.\n```\n"
     },
     {
       "name": "compact-agent-prompt",
@@ -264,7 +278,7 @@
     },
     {
       "name": "tool-read-description",
-      "template": "Reads a file from the local filesystem. You can access any file directly by using this tool.\nAssume this tool is able to read all files on the machine. If the User provides a path to a file assume that path is valid. It is okay to read a file that does not exist; an error will be returned.\n\nUsage:\n- The file_path parameter must be an absolute path, not a relative path\n- By default, it reads up to 2000 lines starting from the beginning of the file\n- You can optionally specify a line offset and limit (especially handy for long files), but it's recommended to read the whole file by not providing these parameters\n- Any lines longer than 2000 characters will be truncated\n- Results are returned using cat -n format, with line numbers starting at 1\n- This tool allows Terminal Assistant Agent to read images (eg PNG, JPG, etc). When reading an image file the contents are presented visually as Terminal Assistant Agent is a multimodal LLM.\n- This tool can read PDF files (.pdf). PDFs are processed page by page, extracting both text and visual content for analysis.\n- For Jupyter notebooks (.ipynb files), use the NotebookRead instead\n- You have the capability to call multiple tools in a single response. It is always better to speculatively read multiple files as a batch that are potentially useful.\n- You will regularly be asked to read screenshots. If the user provides a path to a screenshot ALWAYS use this tool to view the file at the path. This tool will work with all temporary file paths like /var/folders/123/abc/T/TemporaryItems/NSIRD_screencaptureui_ZfB1tD/Screenshot.png\n- If you read a file that exists but has empty contents you will receive a system reminder warning in place of file contents.\n"
+      "template": "Reads a file from the local filesystem. You can access any file directly by using this tool.\nAssume this tool is able to read all files on the machine. If the User provides a path to a file assume that path is valid. It is okay to read a file that does not exist; an error will be returned.\n\nUsage:\n- The file_path parameter must be an absolute path, not a relative path\n- By default, it reads up to 2000 lines starting from the beginning of the file\n- You can optionally specify a line offset and limit (especially handy for long files), but it's recommended to read the whole file by not providing these parameters\n- Any lines longer than 2000 characters will be truncated\n- Results are returned using cat -n format, with line numbers starting at 1\n- This tool allows Terminal Assistant Agent to read images (eg PNG, JPG, etc). When reading an image file the contents are presented visually as Terminal Assistant Agent is a multimodal LLM.\n- This tool can read PDF files (.pdf). PDFs are processed page by page, extracting both text and visual content for analysis.\n- This tool can read Jupyter notebooks (.ipynb files) and returns all cells with their outputs, combining code, text, and visualizations.\n- This tool can only read files, not directories. To read a directory, use an ls command via the Bash tool.\n- You have the capability to call multiple tools in a single response. It is always better to speculatively read multiple files as a batch that are potentially useful.\n- You will regularly be asked to read screenshots. If the user provides a path to a screenshot ALWAYS use this tool to view the file at the path. This tool will work with all temporary file paths like /var/folders/123/abc/T/TemporaryItems/NSIRD_screencaptureui_ZfB1tD/Screenshot.png\n- If you read a file that exists but has empty contents you will receive a system reminder warning in place of file contents.\n"
     },
     {
       "name": "tool-edit-description",
@@ -625,6 +639,6 @@
       "description": "tool-slashcommand-description"
     }
   ],
-  "commit": "89fbe616fdec4c4a834f849dfe92000d11736c5b",
-  "date": "2025-10-14T09:39:26.834Z"
+  "commit": "bb57cef9419ef2c3598789e96e1fd21cc458904b",
+  "date": "2025-10-16T16:05:26.873Z"
 }