@tencent-ai/codebuddy-code 2.127.3-dev.0a05362.202607281440 → 2.127.3-next.5a079f0.202607281443

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tencent-ai/codebuddy-code",
-  "version": "2.127.3-dev.0a05362.202607281440",
+  "version": "2.127.3-next.5a079f0.202607281443",
   "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",
@@ -44,7 +44,7 @@
   },
   "publishConfig": {
     "access": "public",
-    "tag": "dev"
+    "tag": "next"
   },
   "scripts": {},
   "devDependencies": {}

package/product.cloudhosted.json

@@ -60,6 +60,8 @@
         "DelegateTool",
         "WeChatReply",
         "WeComReply",
+        "PushNotification",
+        "ReportFindings",
         "ComputerUse",
         "ListMcpResources",
         "ReadMcpResource",
@@ -830,6 +832,6 @@
     "SelectImage": true,
     "SkipToolCallSupportCheck": true
   },
-  "commit": "0a053626e1f0ddb87f4122c7b3b715a12b0ffb4b",
-  "date": "2026-07-28T06:39:34.856Z"
+  "commit": "5a079f00d748c1ecd2a52c42e27591b79e2487ae",
+  "date": "2026-07-28T06:43:00.979Z"
 }

package/product.internal.json

@@ -74,6 +74,8 @@
         "DelegateTool",
         "WeChatReply",
         "WeComReply",
+        "PushNotification",
+        "ReportFindings",
         "ComputerUse",
         "ListMcpResources",
         "ReadMcpResource",
@@ -813,6 +815,6 @@
       }
     }
   },
-  "commit": "0a053626e1f0ddb87f4122c7b3b715a12b0ffb4b",
-  "date": "2026-07-28T06:39:34.891Z"
+  "commit": "5a079f00d748c1ecd2a52c42e27591b79e2487ae",
+  "date": "2026-07-28T06:43:00.995Z"
 }

package/product.ioa.json

@@ -96,6 +96,8 @@
         "DelegateTool",
         "WeChatReply",
         "WeComReply",
+        "PushNotification",
+        "ReportFindings",
         "ComputerUse",
         "ListMcpResources",
         "ReadMcpResource",
@@ -1309,6 +1311,6 @@
       }
     }
   },
-  "commit": "0a053626e1f0ddb87f4122c7b3b715a12b0ffb4b",
-  "date": "2026-07-28T06:39:34.911Z"
+  "commit": "5a079f00d748c1ecd2a52c42e27591b79e2487ae",
+  "date": "2026-07-28T06:43:00.976Z"
 }

package/product.json

@@ -951,7 +951,7 @@
     },
     {
       "name": "code-review-trigger-reminder",
-      "template": "<system-reminder data-role=\"code-review-trigger\">\nThe user invoked `/code-review`{{target}} to review code for bugs and quality issues.\n{%- if fix %}\nThe user requested --fix: after the review, apply the findings to the working tree.\n{%- endif %}\n{%- if comment %}\nThe user requested --comment: after the review, post findings as inline PR comments.\n{%- endif %}\n\nReview the current diff for correctness bugs and reuse/simplification/efficiency cleanups.\n\n## Steps\n\n1. Run `git diff` (or `git diff HEAD` if there are staged changes) to see what changed. If a specific PR number or target is provided, run `gh pr diff <number>` instead.\n\n2. Analyze the changes thoroughly, looking for:\n   - **Correctness bugs**: logic errors, off-by-one, null/undefined handling, race conditions, missing error handling\n   - **Security issues**: injection vulnerabilities, improper input validation, exposed secrets\n   - **Performance problems**: unnecessary work, N+1 patterns, missing concurrency, hot-path bloat\n   - **Code quality**: duplicated code, leaky abstractions, parameter sprawl, stringly-typed code\n   - **Test coverage gaps**: untested edge cases, missing error path tests\n\n3. For each finding, provide:\n   - File and line number\n   - Severity (critical / warning / suggestion)\n   - One-line summary of the issue\n   - Suggested fix\n\n4. Present findings ranked most-severe first. Group by file when multiple findings are in the same file.\n{%- if fix %}\n\nAfter the review, apply all fixable findings to the working tree directly.\n{%- endif %}\n{%- if comment %}\n\nAfter the review, post each finding as an inline PR comment using `gh api` or `gh pr review`.\n{%- endif %}\n</system-reminder>\n"
+      "template": "<system-reminder data-role=\"code-review-trigger\">\nThe user invoked `/code-review`{{target}} to review code for bugs and quality issues.\n{%- if fix %}\nThe user requested --fix: after the review, apply the findings to the working tree.\n{%- endif %}\n{%- if comment %}\nThe user requested --comment: after the review, post findings as inline PR comments.\n{%- endif %}\n\nReview the current diff for correctness bugs and reuse/simplification/efficiency cleanups.\n\n## Steps\n\n1. Run `git diff` (or `git diff HEAD` if there are staged changes) to see what changed. If a specific PR number or target is provided, run `gh pr diff <number>` instead.\n\n2. Analyze the changes thoroughly, looking for:\n   - **Correctness bugs**: logic errors, off-by-one, null/undefined handling, race conditions, missing error handling\n   - **Security issues**: injection vulnerabilities, improper input validation, exposed secrets\n   - **Performance problems**: unnecessary work, N+1 patterns, missing concurrency, hot-path bloat\n   - **Code quality**: duplicated code, leaky abstractions, parameter sprawl, stringly-typed code\n   - **Test coverage gaps**: untested edge cases, missing error path tests\n\n3. For each finding, determine:\n   - File and line number\n   - Severity (critical / warning / suggestion)\n   - One-line summary of the issue\n   - A concrete failure scenario (how/when this would actually break or cause harm)\n   - Suggested fix\n\n4. Call the `ReportFindings` tool once with all findings (most-severe first), mapping each to\n   `file` (path + line), `summary` (one-line issue + suggested fix), and `failureScenario`\n   (the concrete scenario from step 3). If `ReportFindings` is not available, present findings\n   ranked most-severe first in prose instead, grouped by file when multiple findings share a file.\n{%- if fix %}\n\nAfter the review, apply all fixable findings to the working tree directly.\n{%- endif %}\n{%- if comment %}\n\nAfter the review, post each finding as an inline PR comment using `gh api` or `gh pr review`.\n{%- endif %}\n</system-reminder>\n"
     },
     {
       "name": "verify-trigger-reminder",
@@ -1069,6 +1069,8 @@
         "DelegateTool",
         "WeChatReply",
         "WeComReply",
+        "PushNotification",
+        "ReportFindings",
         "ComputerUse",
         "ListMcpResources",
         "ReadMcpResource",
@@ -1772,12 +1774,22 @@
       "name": "WeComReply",
       "description": "Send a reply to a WeCom (企业微信) user. For text: pass text (markdown supported)."
     },
+    {
+      "name": "PushNotification",
+      "description": "tool-pushnotification-description",
+      "deferLoading": true
+    },
+    {
+      "name": "ReportFindings",
+      "description": "tool-reportfindings-description",
+      "deferLoading": true
+    },
     {
       "name": "Workflow",
       "description": "workflow-tool-description",
       "deferLoading": true
     }
   ],
-  "commit": "0a053626e1f0ddb87f4122c7b3b715a12b0ffb4b",
-  "date": "2026-07-28T06:39:34.955Z"
+  "commit": "5a079f00d748c1ecd2a52c42e27591b79e2487ae",
+  "date": "2026-07-28T06:43:00.979Z"
 }

package/product.selfhosted.json

@@ -53,6 +53,8 @@
         "DelegateTool",
         "WeChatReply",
         "WeComReply",
+        "PushNotification",
+        "ReportFindings",
         "ComputerUse",
         "ListMcpResources",
         "ReadMcpResource",
@@ -344,6 +346,6 @@
     "ScheduledTasks": true,
     "SkipToolCallSupportCheck": true
   },
-  "commit": "0a053626e1f0ddb87f4122c7b3b715a12b0ffb4b",
-  "date": "2026-07-28T06:39:34.917Z"
+  "commit": "5a079f00d748c1ecd2a52c42e27591b79e2487ae",
+  "date": "2026-07-28T06:43:01.020Z"
 }