@tencent-ai/codebuddy-code 2.94.4 → 2.95.0-next.dddd628.20260502

package/dist/web-ui/index.html

@@ -19,7 +19,7 @@
     <link rel="preconnect" href="https://fonts.googleapis.com">
     <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
     <link href="https://fonts.googleapis.com/css2?family=Poppins:wght@400;500;600;700&display=swap" rel="stylesheet">
-  <script type="module" crossorigin src="/assets/index-BpnOVpEQ.js"></script>
+  <script type="module" crossorigin src="/assets/index-BY1JTnsk.js"></script>
   <link rel="modulepreload" crossorigin href="/assets/markdown-Ce2Umeb2.js">
   <link rel="modulepreload" crossorigin href="/assets/vendor-DpYitQz5.js">
   <link rel="stylesheet" crossorigin href="/assets/index-BjcZsltA.css">

package/dist/web-ui/sw.js

@@ -1 +1 @@
-if(!self.define){let s,e={};const o=(o,n)=>(o=new URL(o+".js",n).href,e[o]||new Promise(e=>{if("document"in self){const s=document.createElement("script");s.src=o,s.onload=e,document.head.appendChild(s)}else s=o,importScripts(o),e()}).then(()=>{let s=e[o];if(!s)throw new Error(`Module ${o} didn’t register its module`);return s}));self.define=(n,i)=>{const l=s||("document"in self?document.currentScript.src:"")||location.href;if(e[l])return;let t={};const r=s=>o(s,l),u={module:{uri:l},exports:t,require:r};e[l]=Promise.all(n.map(s=>u[s]||r(s))).then(s=>(i(...s),t))}}define(["./workbox-e082a648"],function(s){"use strict";self.skipWaiting(),s.clientsClaim(),s.precacheAndRoute([{url:"logo.svg",revision:"6165db837a6039880af9705aa09be574"},{url:"index.html",revision:"5d1869aade91b301753385418b8e707e"},{url:"assets/workbox-window.prod.es5-BIl4cyR9.js",revision:null},{url:"assets/vendor-DpYitQz5.js",revision:null},{url:"assets/octicons-CaZ_fok2.woff2",revision:null},{url:"assets/mfixx-CpAhKOZz.woff2",revision:null},{url:"assets/markdown-Ce2Umeb2.js",revision:null},{url:"assets/logo-iZVLr450.svg",revision:null},{url:"assets/index-DixJ0kqk.js",revision:null},{url:"assets/index-BpnOVpEQ.js",revision:null},{url:"assets/index-BjcZsltA.css",revision:null},{url:"assets/fontawesome-B-jkhYfk.woff2",revision:null},{url:"assets/file-icons-C0jOugUK.woff2",revision:null},{url:"assets/devopicons-QN4QXivI.woff2",revision:null},{url:"logo.svg",revision:"6165db837a6039880af9705aa09be574"},{url:"manifest.webmanifest",revision:"ed76a251c8eb35918791b0d0a060a0c2"}],{}),s.cleanupOutdatedCaches(),s.registerRoute(new s.NavigationRoute(s.createHandlerBoundToURL("/index.html"),{denylist:[/^\/api/,/^\/gateway/,/^\/docs\//]})),s.registerRoute(/^https:\/\/fonts\.googleapis\.com/,new s.StaleWhileRevalidate({cacheName:"google-fonts-stylesheets",plugins:[]}),"GET"),s.registerRoute(/^https:\/\/fonts\.gstatic\.com/,new s.CacheFirst({cacheName:"google-fonts-webfonts",plugins:[new s.ExpirationPlugin({maxEntries:20,maxAgeSeconds:31536e3})]}),"GET")});
+if(!self.define){let s,e={};const o=(o,n)=>(o=new URL(o+".js",n).href,e[o]||new Promise(e=>{if("document"in self){const s=document.createElement("script");s.src=o,s.onload=e,document.head.appendChild(s)}else s=o,importScripts(o),e()}).then(()=>{let s=e[o];if(!s)throw new Error(`Module ${o} didn’t register its module`);return s}));self.define=(n,i)=>{const l=s||("document"in self?document.currentScript.src:"")||location.href;if(e[l])return;let t={};const r=s=>o(s,l),a={module:{uri:l},exports:t,require:r};e[l]=Promise.all(n.map(s=>a[s]||r(s))).then(s=>(i(...s),t))}}define(["./workbox-e082a648"],function(s){"use strict";self.skipWaiting(),s.clientsClaim(),s.precacheAndRoute([{url:"logo.svg",revision:"6165db837a6039880af9705aa09be574"},{url:"index.html",revision:"6970ca00b3afab2b3f48f65a44e44d55"},{url:"assets/workbox-window.prod.es5-BIl4cyR9.js",revision:null},{url:"assets/vendor-DpYitQz5.js",revision:null},{url:"assets/octicons-CaZ_fok2.woff2",revision:null},{url:"assets/mfixx-CpAhKOZz.woff2",revision:null},{url:"assets/markdown-Ce2Umeb2.js",revision:null},{url:"assets/logo-iZVLr450.svg",revision:null},{url:"assets/index-DixJ0kqk.js",revision:null},{url:"assets/index-BjcZsltA.css",revision:null},{url:"assets/index-BY1JTnsk.js",revision:null},{url:"assets/fontawesome-B-jkhYfk.woff2",revision:null},{url:"assets/file-icons-C0jOugUK.woff2",revision:null},{url:"assets/devopicons-QN4QXivI.woff2",revision:null},{url:"logo.svg",revision:"6165db837a6039880af9705aa09be574"},{url:"manifest.webmanifest",revision:"ed76a251c8eb35918791b0d0a060a0c2"}],{}),s.cleanupOutdatedCaches(),s.registerRoute(new s.NavigationRoute(s.createHandlerBoundToURL("/index.html"),{denylist:[/^\/api/,/^\/gateway/,/^\/docs\//]})),s.registerRoute(/^https:\/\/fonts\.googleapis\.com/,new s.StaleWhileRevalidate({cacheName:"google-fonts-stylesheets",plugins:[]}),"GET"),s.registerRoute(/^https:\/\/fonts\.gstatic\.com/,new s.CacheFirst({cacheName:"google-fonts-webfonts",plugins:[new s.ExpirationPlugin({maxEntries:20,maxAgeSeconds:31536e3})]}),"GET")});

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tencent-ai/codebuddy-code",
-  "version": "2.94.4",
+  "version": "2.95.0-next.dddd628.20260502",
   "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

@@ -94,7 +94,9 @@
         "SendMessage",
         "NotebookEdit",
         "LSP",
-        "ComputerUse"
+        "ComputerUse",
+        "ImageGen",
+        "ImageEdit"
       ],
       "tags": [
         "cli",
@@ -407,6 +409,6 @@
     "ScheduledTasks": true,
     "SkillManage": false
   },
-  "commit": "ecb69a546767b4073b1c433aeffbe2918875dd40",
-  "date": "2026-05-01T06:09:39.043Z"
+  "commit": "dddd62842dc01424ffe806de1755b26543900246",
+  "date": "2026-05-02T10:14:27.428Z"
 }

package/product.internal.json

@@ -102,7 +102,9 @@
         "SendMessage",
         "NotebookEdit",
         "LSP",
-        "ComputerUse"
+        "ComputerUse",
+        "ImageGen",
+        "ImageEdit"
       ],
       "tags": [
         "cli",
@@ -592,6 +594,6 @@
       }
     }
   },
-  "commit": "ecb69a546767b4073b1c433aeffbe2918875dd40",
-  "date": "2026-05-01T06:09:39.039Z"
+  "commit": "dddd62842dc01424ffe806de1755b26543900246",
+  "date": "2026-05-02T10:14:27.386Z"
 }

package/product.ioa.json

@@ -125,7 +125,9 @@
         "NotebookEdit",
         "LSP",
         "SkillManage",
-        "ComputerUse"
+        "ComputerUse",
+        "ImageGen",
+        "ImageEdit"
       ],
       "tags": [
         "cli",
@@ -943,6 +945,6 @@
       }
     }
   },
-  "commit": "ecb69a546767b4073b1c433aeffbe2918875dd40",
-  "date": "2026-05-01T06:09:39.121Z"
+  "commit": "dddd62842dc01424ffe806de1755b26543900246",
+  "date": "2026-05-02T10:14:27.507Z"
 }

package/product.json

@@ -541,7 +541,7 @@
     },
     {
       "name": "tool-bash-description",
-      "template": "Executes a given bash command and returns its output.\n\nThe working directory persists between commands, but shell state does not. The shell environment is initialized from the user's profile.\n\nIMPORTANT: The user's default shell is {{defaultShell}}. Generate commands using syntax compatible with this shell.\n\n{% if platform == 'win32' %}\nIMPORTANT: On Windows, this tool uses Git Bash. Windows-specific notes:\n- Use forward slashes `/` in paths (Git Bash handles conversion automatically)\n- Standard Unix commands are available (ls, grep, cat, sed, awk, etc.)\n- For Windows-specific operations (registry, services, COM objects, .NET), consider using the PowerShell tool instead\n- Avoid CMD-style null redirects (`2>nul`) — use POSIX `2>/dev/null` instead\n- Drive paths are accessible as `/c/`, `/d/` etc. (e.g., `/c/Users/name/`)\n{% endif %}\n\nIMPORTANT: Avoid using this tool to run `cat`, `head`, `tail`, `sed`, `awk`, or `echo` commands, unless explicitly instructed or after you have verified that a dedicated tool cannot accomplish your task. Instead, use the appropriate dedicated tool as this will provide a much better experience for the user:\n\n- Read files: Use Read (NOT cat/head/tail)\n- Edit files: Use Edit (NOT sed/awk)\n- Write files: Use Write (NOT echo >/cat <<EOF)\n- Communication: Output text directly (NOT echo/printf)\n\nIMPORTANT: Avoid using this tool to run `find`, `grep`, or `rg` commands, unless explicitly instructed or after you have verified that a dedicated tool cannot accomplish your task. Instead, use the appropriate dedicated tool as this will provide a much better experience for the user:\n\n- File search: Use Glob (NOT find or ls)\n- Content search: Use Grep (NOT grep or rg)\n\nWhile the Bash tool can do similar things, it’s better to use the built-in tools as they provide a better user experience and make it easier to review tool calls and give permission.\n\n# Instructions\n- If your command will create new directories or files, first use this tool to run `ls` to verify the parent directory exists and is the correct location.\n- Always quote file paths that contain spaces with double quotes in your command (e.g., cd \"path with spaces/file.txt\").\n- Try to maintain your current working directory throughout the session by using absolute paths and avoiding usage of `cd`. You may use `cd` if the User explicitly requests it. In particular, never prepend `cd <current-directory>` to a `git` command — `git` already operates on the current working tree, and the compound triggers a permission prompt.\n- You may specify an optional timeout in milliseconds (up to {{bashMaxTimeoutMs}}ms). When the command may run longer than a few seconds (installers, build steps, long-running helper binaries, data processing) prefer to **omit the `timeout` parameter entirely** — the system default ({{bashDefaultTimeoutMs}}ms) is controlled by `BASH_DEFAULT_TIMEOUT_MS` and lets the user tune it without editing prompts. Only specify an explicit `timeout` when the command has a known short upper bound (e.g. a quick probe, a health check).\n- Non-interactive runs (`--print`/`-p`, `--output-format stream-json`) exit the process as soon as the main agent finishes its turn, even if earlier commands spawned background or long-running child processes. When designing multi-step workflows (skills, scripts that kick off build/analysis pipelines), either await the child process in the foreground (do not `nohup ... &` + return immediately) or plan the turns so the final step collects the artifact/exit status before the agent returns.\n- You can use the `run_in_background` parameter to run the command in the background. Only use this if you don't need the result immediately and are OK being notified when the command completes later. You do not need to use '&' at the end of the command when using this parameter.\n- When issuing multiple commands:\n  - If the commands are independent and can run in parallel, make multiple Bash tool calls in a single message. Example: if you need to run \"git status\" and \"git diff\", send a single message with two Bash tool calls in parallel.\n  - If the commands depend on each other and must run sequentially, use a single Bash call with '&&' to chain them together.\n  - Use ';' only when you need to run commands sequentially but don't care if earlier commands fail.\n  - DO NOT use newlines to separate commands (newlines are ok in quoted strings).\n- For git commands:\n  - For creating commits, use the `/commit` command — it handles git safety protocol, HEREDOC formatting, and pre-commit hook recovery.\n  - For committing, pushing, and opening a PR, use the `/commit-push-pr` command.\n  - Prefer creating a new commit rather than amending an existing commit.\n  - Before running destructive operations (e.g., `git reset --hard`, `git push --force`, `git checkout --`), consider whether there is a safer alternative. Only use destructive operations when they are truly the best approach.\n  - Never skip hooks (`--no-verify`) or bypass signing (`--no-gpg-sign`, `-c commit.gpgsign=false`) unless the user has explicitly asked for it. If a hook fails, investigate and fix the underlying issue.\n- Avoid unnecessary `sleep` commands:\n  - Do not sleep between commands that can run immediately — just run them.\n  - If your command is long running and you would like to be notified when it finishes — use `run_in_background`. No sleep needed.\n  - Do not retry failing commands in a sleep loop — diagnose the root cause.\n  - If waiting for a background task you started with `run_in_background`, check its output using the returned task id — do not poll in a sleep loop.\n  - If you must poll an external process, use a check command (e.g. `gh run view`) rather than sleeping first.\n  - If you must sleep, keep the duration short (1-5 seconds) to avoid blocking the user.\n- For GitHub operations (issues, PR checks, releases, comments), use the `gh` command via the Bash tool. If given a GitHub URL, use `gh` to get the information. Example: view PR comments via `gh api repos/foo/bar/pulls/123/comments`.\n"
+      "template": "Executes a given bash command and returns its output.\n\nThe working directory persists between commands, but shell state does not. The shell environment is initialized from the user's profile.\n\nIMPORTANT: The user's default shell is {{defaultShell}}. Generate commands using syntax compatible with this shell.\n\n{% if platform == 'win32' %}\nIMPORTANT: On Windows, this tool uses Git Bash. Windows-specific notes:\n- Use forward slashes `/` in paths (Git Bash handles conversion automatically)\n- Standard Unix commands are available (ls, grep, cat, sed, awk, etc.)\n- For Windows-specific operations (registry, services, COM objects, .NET), consider using the PowerShell tool instead\n- Avoid CMD-style null redirects (`2>nul`) — use POSIX `2>/dev/null` instead\n- Drive paths are accessible as `/c/`, `/d/` etc. (e.g., `/c/Users/name/`)\n{% endif %}\n\nIMPORTANT: Avoid using this tool to run `cat`, `head`, `tail`, `sed`, `awk`, or `echo` commands, unless explicitly instructed or after you have verified that a dedicated tool cannot accomplish your task. Instead, use the appropriate dedicated tool as this will provide a much better experience for the user:\n\n- Read files: Use Read (NOT cat/head/tail)\n- Edit files: Use Edit (NOT sed/awk)\n- Write files: Use Write (NOT echo >/cat <<EOF)\n- Communication: Output text directly (NOT echo/printf)\n\nIMPORTANT: Avoid using this tool to run `find`, `grep`, or `rg` commands, unless explicitly instructed or after you have verified that a dedicated tool cannot accomplish your task. Instead, use the appropriate dedicated tool as this will provide a much better experience for the user:\n\n- File search: Use Glob (NOT find or ls)\n- Content search: Use Grep (NOT grep or rg)\n\nWhile the Bash tool can do similar things, it’s better to use the built-in tools as they provide a better user experience and make it easier to review tool calls and give permission.\n\n# Instructions\n- If your command will create new directories or files, first use this tool to run `ls` to verify the parent directory exists and is the correct location.\n- Always quote file paths that contain spaces with double quotes in your command (e.g., cd \"path with spaces/file.txt\").\n- Try to maintain your current working directory throughout the session by using absolute paths and avoiding usage of `cd`. You may use `cd` if the User explicitly requests it. In particular, never prepend `cd <current-directory>` to a `git` command — `git` already operates on the current working tree, and the compound triggers a permission prompt.\n- You may specify an optional timeout in milliseconds (up to {{bashMaxTimeoutMs}}ms). When the command may run longer than a few seconds (installers, build steps, long-running helper binaries, data processing) prefer to **omit the `timeout` parameter entirely** — the system default ({{bashDefaultTimeoutMs}}ms) is controlled by `BASH_DEFAULT_TIMEOUT_MS` and lets the user tune it without editing prompts. Only specify an explicit `timeout` when the command has a known short upper bound (e.g. a quick probe, a health check).\n- Non-interactive runs (`--print`/`-p`, `--output-format stream-json`) exit the process as soon as the main agent finishes its turn, even if earlier commands spawned background or long-running child processes. When designing multi-step workflows (skills, scripts that kick off build/analysis pipelines), either await the child process in the foreground (do not `nohup ... &` + return immediately) or plan the turns so the final step collects the artifact/exit status before the agent returns.\n- You can use the `run_in_background` parameter to run the command in the background. Prefer setting this to `true` for known long-running commands — installs, builds, image pulls, long tests, servers, etc. Examples: `yarn install/package/build`, `npm install/build`, `pnpm install`, `docker build/pull`, `cargo build`, `make`, `mvn package`, `go build`, `gradle build`. Once backgrounded you will receive a `task_id`; use the `TaskOutput` tool with that id to poll progress or fetch completed output. You do not need to use '&' at the end of the command when using this parameter.\n- If you forget `run_in_background` on a long command and it hits the foreground timeout, the command will **auto-background instead of being killed** (no SIGTERM, no state loss). The tool result will tell you the new `task_id` so you can pick it up with `TaskOutput`. This covers most long commands; the only exception is `sleep`, which is never auto-backgrounded because its timeout is usually the point of the command.\n- When issuing multiple commands:\n  - If the commands are independent and can run in parallel, make multiple Bash tool calls in a single message. Example: if you need to run \"git status\" and \"git diff\", send a single message with two Bash tool calls in parallel.\n  - If the commands depend on each other and must run sequentially, use a single Bash call with '&&' to chain them together.\n  - Use ';' only when you need to run commands sequentially but don't care if earlier commands fail.\n  - DO NOT use newlines to separate commands (newlines are ok in quoted strings).\n- For git commands:\n  - For creating commits, use the `/commit` command — it handles git safety protocol, HEREDOC formatting, and pre-commit hook recovery.\n  - For committing, pushing, and opening a PR, use the `/commit-push-pr` command.\n  - Prefer creating a new commit rather than amending an existing commit.\n  - Before running destructive operations (e.g., `git reset --hard`, `git push --force`, `git checkout --`), consider whether there is a safer alternative. Only use destructive operations when they are truly the best approach.\n  - Never skip hooks (`--no-verify`) or bypass signing (`--no-gpg-sign`, `-c commit.gpgsign=false`) unless the user has explicitly asked for it. If a hook fails, investigate and fix the underlying issue.\n- Avoid unnecessary `sleep` commands:\n  - Do not sleep between commands that can run immediately — just run them.\n  - If your command is long running and you would like to be notified when it finishes — use `run_in_background`. No sleep needed.\n  - Do not retry failing commands in a sleep loop — diagnose the root cause.\n  - If waiting for a background task you started with `run_in_background`, check its output using the returned task id — do not poll in a sleep loop.\n  - If you must poll an external process, use a check command (e.g. `gh run view`) rather than sleeping first.\n  - If you must sleep, keep the duration short (1-5 seconds) to avoid blocking the user.\n- For GitHub operations (issues, PR checks, releases, comments), use the `gh` command via the Bash tool. If given a GitHub URL, use `gh` to get the information. Example: view PR comments via `gh api repos/foo/bar/pulls/123/comments`.\n"
     },
     {
       "name": "tool-powershell-description",
@@ -617,7 +617,7 @@
     },
     {
       "name": "tool-websearch-description",
-      "template": "\n- Allows CodeBuddy Code to search the web and use the results to inform responses\n- Provides up-to-date information for current events and recent data\n- Returns search result information formatted as search result blocks\n- Use this tool for accessing information beyond CodeBuddy Code's knowledge cutoff\n- Searches are performed automatically within a single API call\n\nUsage notes:\n  - Domain filtering is supported to include or block specific websites\n  - Web search is only available in the US\n  - Account for \"Today's date\" in <env>. For example, if <env> says \"Today's date: 2025-07-01\", and the user wants the latest docs, do not use 2024 in the search query. Use 2025.\n\n"
+      "template": "\n- Searches the web and uses the results to inform responses\n- Provides up-to-date information for current events and recent data\n- Returns search result information formatted as search result blocks\n- Use this tool for accessing information beyond the knowledge cutoff\n- Searches are performed automatically within a single API call\n\nUsage notes:\n  - Domain filtering is supported to include or block specific websites\n  - Account for \"Today's date\" in <env>. For example, if <env> says \"Today's date: 2025-07-01\", and the user wants the latest docs, do not use 2024 in the search query. Use 2025.\n  - Use `query_keyword_groups` when comparisons, explicit multi-topic research, or coverage-improving query variants across phrasings/languages/sub-angles are helpful; keep `query` as the main intent, max 5 groups.\n    Example: \"NVIDIA stock and AI chip market latest news\" → query_keyword_groups: [\"NVIDIA stock latest news\", \"AI chip market latest news\", \"英伟达 股价 AI芯片 最新动态\"]\n  - Use the `topic` parameter to specify the search domain for better relevance. Supported values: general (default), news, programming, documentation, academic, finance, technology, legal, medical.\n"
     },
     {
       "name": "tool-enterplanmode-description",
@@ -929,7 +929,9 @@
         "LSP",
         "WeChatReply",
         "WeComReply",
-        "ComputerUse"
+        "ComputerUse",
+        "ImageGen",
+        "ImageEdit"
       ],
       "tags": [
         "cli",
@@ -1517,6 +1519,6 @@
       "description": "Send a reply to a WeCom (企业微信) user. For text: pass text (markdown supported)."
     }
   ],
-  "commit": "ecb69a546767b4073b1c433aeffbe2918875dd40",
-  "date": "2026-05-01T06:09:38.974Z"
+  "commit": "dddd62842dc01424ffe806de1755b26543900246",
+  "date": "2026-05-02T10:14:27.543Z"
 }

package/product.selfhosted.json

@@ -88,7 +88,9 @@
         "SendMessage",
         "NotebookEdit",
         "LSP",
-        "ComputerUse"
+        "ComputerUse",
+        "ImageGen",
+        "ImageEdit"
       ],
       "tags": [
         "cli",
@@ -294,6 +296,6 @@
     "DeferToolLoading": true,
     "ScheduledTasks": true
   },
-  "commit": "ecb69a546767b4073b1c433aeffbe2918875dd40",
-  "date": "2026-05-01T06:09:39.019Z"
+  "commit": "dddd62842dc01424ffe806de1755b26543900246",
+  "date": "2026-05-02T10:14:27.337Z"
 }