@tencent-ai/codebuddy-code 2.31.1 → 2.31.2-next.7f4c8cc.20260112

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tencent-ai/codebuddy-code",
-  "version": "2.31.1",
+  "version": "2.31.2-next.7f4c8cc.20260112",
   "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",
@@ -29,7 +29,8 @@
     "url": "https://cnb.cool/codebuddy/codebuddy-code/-/issues"
   },
   "publishConfig": {
-    "access": "public"
+    "access": "public",
+    "tag": "next"
   },
   "scripts": {},
   "devDependencies": {},

package/product.cloudhosted.json

@@ -316,6 +316,6 @@
     "BillingNotice": false,
     "CustomModelsJSON": true
   },
-  "commit": "b4b4b78dc12aebc2719b679d536f400278a39828",
-  "date": "2026-01-09T08:00:22.131Z"
+  "commit": "7f4c8cc62814d18709d9c0c445a66064dfe93dff",
+  "date": "2026-01-11T16:08:27.185Z"
 }

package/product.internal.json

@@ -318,6 +318,6 @@
     "BillingNotice": false,
     "CustomModelsJSON": true
   },
-  "commit": "b4b4b78dc12aebc2719b679d536f400278a39828",
-  "date": "2026-01-09T08:00:19.370Z"
+  "commit": "7f4c8cc62814d18709d9c0c445a66064dfe93dff",
+  "date": "2026-01-11T16:08:24.669Z"
 }

package/product.ioa.json

@@ -525,6 +525,6 @@
     "BillingNotice": false,
     "CustomModelsJSON": true
   },
-  "commit": "b4b4b78dc12aebc2719b679d536f400278a39828",
-  "date": "2026-01-09T08:00:20.724Z"
+  "commit": "7f4c8cc62814d18709d9c0c445a66064dfe93dff",
+  "date": "2026-01-11T16:08:25.935Z"
 }

package/product.json

@@ -478,12 +478,16 @@
     },
     {
       "name": "tool-exit-planmode-description",
-      "template": "Use this tool when you are in plan mode and have finished presenting your plan and are ready to code. This will prompt the user to exit plan mode.\nIMPORTANT: Only use this tool when the task requires planning the implementation steps of a task that requires writing code. For research tasks where you're gathering information, searching files, reading files or in general trying to understand the codebase - do NOT use this tool.\n\n## Handling Ambiguity in Plans\nBefore using this tool, ensure your plan is clear and unambiguous. If there are multiple valid approaches or unclear requirements:\n1. Use the AskUserQuestion tool to clarify with the user\n2. Ask about specific implementation choices (e.g., architectural patterns, which library to use)\n3. Clarify any assumptions that could affect the implementation\n4. Only proceed with ExitPlanMode after resolving ambiguities\n\n## Examples\n\n1. Initial task: \\\"Search for and understand the implementation of vim mode in the codebase\\\" - Do not use the exit plan mode tool because you are not planning the implementation steps of a task.\n2. Initial task: \\\"Help me implement yank mode for vim\\\" - Use the exit plan mode tool after you have finished planning the implementation steps of the task.\n3. Initial task: \\\"Add a new feature to handle user authentication\\\" - If unsure about auth method (OAuth, JWT, etc.), use AskUserQuestion first, then use exit plan mode tool after clarifying the approach.\n"
+      "template": "Use this tool when you are in plan mode and have finished writing your plan to the plan file and are ready for user approval.\n\n## How This Tool Works\n- You should have already written your plan to the plan file specified in the plan mode system message\n- This tool does NOT take the plan content as a parameter - it will read the plan from the file you wrote\n- This tool simply signals that you're done planning and ready for the user to review and approve\n- The user will see the contents of your plan file when they review it\n\n## When to Use This Tool\nIMPORTANT: Only use this tool when the task requires planning the implementation steps of a task that requires writing code. For research tasks where you're gathering information, searching files, reading files or in general trying to understand the codebase - do NOT use this tool.\n\n## Handling Ambiguity in Plans\nBefore using this tool, ensure your plan is clear and unambiguous. If there are multiple valid approaches or unclear requirements:\n1. Use the AskUserQuestion tool to clarify with the user\n2. Ask about specific implementation choices (e.g., architectural patterns, which library to use)\n3. Clarify any assumptions that could affect the implementation\n4. Edit your plan file to incorporate user feedback\n5. Only proceed with ExitPlanMode after resolving ambiguities and updating the plan file\n\n## Examples\n\n1. Initial task: \\\"Search for and understand the implementation of vim mode in the codebase\\\" - Do not use the exit plan mode tool because you are not planning the implementation steps of a task.\n2. Initial task: \\\"Help me implement yank mode for vim\\\" - Use the exit plan mode tool after you have finished planning the implementation steps of the task.\n3. Initial task: \\\"Add a new feature to handle user authentication\\\" - If unsure about auth method (OAuth, JWT, etc.), use AskUserQuestion first, then use exit plan mode tool after clarifying the approach.\n"
     },
     {
       "name": "tool-exit-planmode-rejected",
       "template": "The user doesn't want to proceed with this tool use. The tool use was rejected (eg. if it was a file edit, the new_string was NOT written to the file). STOP what you are doing and wait for the user to tell you how to proceed.\n"
     },
+    {
+      "name": "tool-exit-planmode-resolve",
+      "template": "User has approved your plan. You can now start coding. Start with updating your todo list if applicable\n\nYour plan has been saved to: {{ planFilePath }}\nYou can refer back to it if needed during implementation.\n\n## Approved Plan:\n{{ plan }}\n\n<system-reminder>\n## Exited Plan Mode\n\nYou have exited plan mode. You can now make edits, run tools, and take actions. The plan file is located at {{ planFilePath }} if you need to reference it.\n</system-reminder>\n"
+    },
     {
       "name": "tool-bashoutput-description",
       "template": "\n- Retrieves output from a running or completed background bash shell\n- Takes a shell_id parameter identifying the shell\n- Always returns only new output since the last check\n- Returns stdout and stderr output along with shell status\n- Supports optional regex filtering to show only lines matching a pattern\n- Use this tool when you need to monitor or check the output of a long-running shell\n- Shell IDs can be found using the /bashes command\n\n"
@@ -866,7 +870,6 @@
     "SelectComponent": true,
     "UIComponentLibrary": true,
     "CustomModelsJSON": true,
-    "LSP": true,
     "BillingNotice": true
   },
   "featureToggles": {
@@ -1014,6 +1017,6 @@
       "description": "tool-lsp-description"
     }
   ],
-  "commit": "b4b4b78dc12aebc2719b679d536f400278a39828",
-  "date": "2026-01-09T08:00:18.056Z"
+  "commit": "7f4c8cc62814d18709d9c0c445a66064dfe93dff",
+  "date": "2026-01-11T16:08:23.419Z"
 }

package/product.selfhosted.json

@@ -198,6 +198,6 @@
     "BillingNotice": false,
     "CustomModelsJSON": true
   },
-  "commit": "b4b4b78dc12aebc2719b679d536f400278a39828",
-  "date": "2026-01-09T08:00:23.451Z"
+  "commit": "7f4c8cc62814d18709d9c0c445a66064dfe93dff",
+  "date": "2026-01-11T16:08:28.438Z"
 }