@tencent-ai/agent-sdk 0.3.116 → 0.3.117

package/cli/dist/web-ui/index.html

@@ -14,7 +14,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-KUgjjYF4.js"></script>
+  <script type="module" crossorigin src="/assets/index-CcRN0PLN.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-C7MTLJe8.css">

package/cli/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tencent-ai/codebuddy-code",
-  "version": "2.79.1",
+  "version": "2.80.0",
   "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/cli/product.cloudhosted.json

@@ -27,6 +27,7 @@
         "Edit",
         "MultiEdit",
         "Bash",
+        "PowerShell",
         "Glob",
         "Grep",
         "EnterPlanMode",
@@ -75,6 +76,7 @@
         "Edit",
         "MultiEdit",
         "Bash",
+        "PowerShell",
         "Glob",
         "Grep",
         "TaskCreate",
@@ -130,6 +132,19 @@
       ],
       "tools": []
     },
+    {
+      "name": "memorySelector",
+      "instructions": "memory-selector-instructions",
+      "description": "Select relevant memories for the current query.",
+      "models": [
+        "lite"
+      ],
+      "tags": [
+        "cli",
+        "memory-selector"
+      ],
+      "tools": []
+    },
     {
       "name": "summaryGenerator",
       "instructions": "summary-generator-instructions",
@@ -200,6 +215,7 @@
       "tools": [
         "Read",
         "Bash",
+        "PowerShell",
         "Glob",
         "Grep",
         "TaskCreate",
@@ -246,6 +262,7 @@
         "Edit",
         "MultiEdit",
         "Bash",
+        "PowerShell",
         "Glob",
         "Grep",
         "TaskCreate",
@@ -404,6 +421,6 @@
     "ImageGen": true,
     "ScheduledTasks": true
   },
-  "commit": "3de3779896f576ac9240401c36b131fbe99753cd",
-  "date": "2026-04-07T07:06:07.051Z"
+  "commit": "ebe2e1f5361cb47c7cb9b4b68396cbabffc7f6ab",
+  "date": "2026-04-07T16:40:34.172Z"
 }

package/cli/product.internal.json

@@ -7,6 +7,7 @@
       "instructions": "cli-agent-prompt",
       "description": "cli agent",
       "models": [
+        "glm-5.1",
         "glm-5.0",
         "glm-5.0-turbo",
         "glm-5v-turbo",
@@ -33,6 +34,7 @@
         "Edit",
         "MultiEdit",
         "Bash",
+        "PowerShell",
         "Glob",
         "Grep",
         "EnterPlanMode",
@@ -81,6 +83,7 @@
         "Edit",
         "MultiEdit",
         "Bash",
+        "PowerShell",
         "Glob",
         "Grep",
         "TaskCreate",
@@ -136,6 +139,19 @@
       ],
       "tools": []
     },
+    {
+      "name": "memorySelector",
+      "instructions": "memory-selector-instructions",
+      "description": "Select relevant memories for the current query.",
+      "models": [
+        "lite"
+      ],
+      "tags": [
+        "cli",
+        "memory-selector"
+      ],
+      "tools": []
+    },
     {
       "name": "summaryGenerator",
       "instructions": "summary-generator-instructions",
@@ -206,6 +222,7 @@
       "tools": [
         "Read",
         "Bash",
+        "PowerShell",
         "Glob",
         "Grep",
         "TaskCreate",
@@ -341,6 +358,24 @@
         "summary": "auto"
       }
     },
+    {
+      "credits": "x1.06 credits",
+      "id": "glm-5.1",
+      "name": "GLM-5.1",
+      "vendor": "e",
+      "maxOutputTokens": 48000,
+      "maxInputTokens": 200000,
+      "supportsToolCall": true,
+      "supportsImages": false,
+      "maxAllowedSize": 200000,
+      "supportsReasoning": true,
+      "onlyReasoning": true,
+      "temperature": 1,
+      "reasoning": {
+        "effort": "medium",
+        "summary": "auto"
+      }
+    },
     {
       "credits": "x0.80 credits",
       "id": "glm-5.0",
@@ -553,6 +588,6 @@
       }
     }
   },
-  "commit": "3de3779896f576ac9240401c36b131fbe99753cd",
-  "date": "2026-04-07T07:06:07.063Z"
+  "commit": "ebe2e1f5361cb47c7cb9b4b68396cbabffc7f6ab",
+  "date": "2026-04-07T16:40:34.170Z"
 }

package/cli/product.ioa.json

@@ -30,6 +30,7 @@
         "gpt-5.1-codex",
         "gpt-5.1-codex-max",
         "gpt-5.1-codex-mini",
+        "glm-5.1-ioa",
         "glm-5.0-turbo-ioa",
         "glm-5v-turbo-ioa",
         "glm-5.0-ioa",
@@ -56,6 +57,7 @@
         "Edit",
         "MultiEdit",
         "Bash",
+        "PowerShell",
         "Glob",
         "Grep",
         "EnterPlanMode",
@@ -105,6 +107,7 @@
         "Edit",
         "MultiEdit",
         "Bash",
+        "PowerShell",
         "Glob",
         "Grep",
         "TaskCreate",
@@ -166,6 +169,19 @@
       ],
       "tools": []
     },
+    {
+      "name": "memorySelector",
+      "instructions": "memory-selector-instructions",
+      "description": "Select relevant memories for the current query.",
+      "models": [
+        "lite"
+      ],
+      "tags": [
+        "cli",
+        "memory-selector"
+      ],
+      "tools": []
+    },
     {
       "name": "summaryGenerator",
       "instructions": "summary-generator-instructions",
@@ -239,6 +255,7 @@
       "tools": [
         "Read",
         "Bash",
+        "PowerShell",
         "Glob",
         "Grep",
         "TaskCreate",
@@ -285,6 +302,7 @@
         "Edit",
         "MultiEdit",
         "Bash",
+        "PowerShell",
         "Glob",
         "Grep",
         "TaskCreate",
@@ -415,6 +433,28 @@
         "reasoning": "kimi-k2.5-ioa"
       }
     },
+    {
+      "credits": "x0.00 credits",
+      "id": "glm-5.1-ioa",
+      "name": "GLM-5.1",
+      "vendor": "e",
+      "maxOutputTokens": 48000,
+      "maxInputTokens": 200000,
+      "supportsToolCall": true,
+      "supportsImages": false,
+      "maxAllowedSize": 200000,
+      "supportsReasoning": true,
+      "onlyReasoning": true,
+      "temperature": 1,
+      "reasoning": {
+        "effort": "medium",
+        "summary": "auto"
+      },
+      "relatedModels": {
+        "lite": "glm-5.1-ioa",
+        "reasoning": "glm-5.1-ioa"
+      }
+    },
     {
       "credits": "x0.00 credits",
       "id": "glm-5.0-ioa",
@@ -915,6 +955,6 @@
       }
     }
   },
-  "commit": "3de3779896f576ac9240401c36b131fbe99753cd",
-  "date": "2026-04-07T07:06:07.079Z"
+  "commit": "ebe2e1f5361cb47c7cb9b4b68396cbabffc7f6ab",
+  "date": "2026-04-07T16:40:34.176Z"
 }

package/cli/product.json

@@ -540,6 +540,10 @@
       "name": "terminal-title-generator-instructions",
       "template": "You are a topic analyzer. Your ONLY purpose is to identify conversation topics.\n\nYour job:\n1. Read the user message\n2. Determine if it starts a NEW conversation topic (compared to previous context if any)\n3. If yes, extract a 2-3 word title for the topic\n\nCRITICAL CONSTRAINTS:\n- You are NOT a code generator, writer, or task executor\n- You MUST respond ONLY with JSON in this exact format:\n  {\"isNewTopic\": boolean, \"title\": string or null}\n- NEVER generate, implement, code, or produce any content\n- NEVER provide explanations, reasoning, or extra text\n- NEVER engage with the user's actual request beyond identifying the topic\n\nExamples:\nUser: \"Can you build an HTML5 game?\" → {\"isNewTopic\": true, \"title\": \"Game Development\"}\nUser: \"Add more features\" → {\"isNewTopic\": false, \"title\": null}\n\nReturn only the JSON object. Nothing else.\n"
     },
+    {
+      "name": "memory-selector-instructions",
+      "template": "You are selecting memories that will be useful to the AI assistant as it processes a user's query. You will be given the user's query and a list of available memory files with their filenames and descriptions.\n\nReturn a JSON object with a \"selected_memories\" array containing the filenames of memories that will clearly be useful (up to 5). Only include memories that you are certain will be helpful based on their name and description.\n- If you are unsure if a memory will be useful, do not include it.\n- If there are no useful memories, return an empty list.\n- If a list of recently-used tools is provided, do not select memories that are usage reference or API documentation for those tools. DO still select memories containing warnings, gotchas, or known issues about those tools.\n\nRespond ONLY with the JSON object, no other text.\n"
+    },
     {
       "name": "summary-generator-instructions",
       "template": "Analyze the following conversation and generate a concise summary that captures the main topic or task being discussed.\n\nRequirements:\n- Generate a short, descriptive summary (5-10 words maximum)\n- Focus on the primary task, feature, or topic being worked on\n- Use action-oriented language when applicable (e.g., \"Implementing dark mode feature\", \"Debugging API authentication issue\")\n- The summary should help users quickly identify what this conversation is about\n\nFormat your response as a JSON object with one field:\n- 'summary' (string): A concise description of the conversation topic\n\nONLY generate the JSON object, no other text (e.g., no markdown).\n\nExamples of good summaries:\n- \"Implementing user authentication flow\"\n- \"Fixing TypeScript compilation errors\"\n- \"Adding dark mode toggle feature\"\n- \"Debugging database connection issue\"\n- \"Refactoring payment module\"\n{%- if language -%}\n\nIMPORTANT: The summary MUST be written in {{language}}. Do not use English for the summary even though the instructions above are in English.\n{%- endif -%}\n"
@@ -570,7 +574,11 @@
     },
     {
       "name": "tool-bash-description",
-      "template": "Executes a given command in a persistent shell session with optional timeout, ensuring proper handling and security measures.\n\nIMPORTANT: The user's default shell is {{defaultShell}}. Generate commands using syntax compatible with this shell.\n\nIMPORTANT: This tool is for terminal operations like git, npm, docker, etc. DO NOT use it for file operations (reading, writing, editing, searching, finding files) - use the specialized tools for this instead.\n\nBefore executing the command, please follow these steps:\n\n1. Directory Verification:\n   - If the command will create new directories or files, first use `ls` to verify the parent directory exists and is the correct location\n   - For example, before running \"mkdir foo/bar\", first use `ls foo` to check that \"foo\" exists and is the intended parent directory\n\n2. Command Execution:\n   - Always quote file paths that contain spaces with double quotes (e.g., cd \"path with spaces/file.txt\")\n   - Examples of proper quoting:\n     - cd \"/Users/name/My Documents\" (correct)\n     - cd /Users/name/My Documents (incorrect - will fail)\n     - python \"/path/with spaces/script.py\" (correct)\n     - python /path/with spaces/script.py (incorrect - will fail)\n   - After ensuring proper quoting, execute the command.\n   - Capture the output of the command.\n\nUsage notes:\n  - The command argument is required.\n  - You can specify an optional timeout in milliseconds (up to 600000ms / 10 minutes). If not specified, commands will timeout after 120000ms (2 minutes).\n  - It is very helpful if you write a clear, concise description of what this command does in 5-10 words.\n  - If the output exceeds 20000 characters, output will be truncated before being returned to you.\n  - You can use the `run_in_background` parameter to run the command in the background, which allows you to continue working while the command runs. You can monitor the output using the Bash tool as it becomes available. You do not need to use '&' at the end of the command when using this parameter.\n  \n  - Avoid using Bash with the `find`, `grep`, `cat`, `head`, `tail`, `sed`, `awk`, or `echo` commands, unless explicitly instructed or when these commands are truly necessary for the task. Instead, always prefer using the dedicated tools for these commands:\n    - File search: Use Glob (NOT find or ls)\n    - Content search: Use Grep (NOT grep or rg)\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    - Archive extraction: If extraction fails with encoding errors (e.g., \"Illegal byte sequence\") for non-ASCII filenames, retry with `ditto -xk` on macOS or `7z x` on Linux.\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. For 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 (e.g., `git add . && git commit -m \"message\" && git push`). For instance, if one operation must complete before another starts (like mkdir before cp, Write before Bash for git operations, or git add before git commit), run these operations sequentially instead.\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  - 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.\n    <good-example>\n    pytest /foo/bar/tests\n    </good-example>\n    <bad-example>\n    cd /foo/bar && pytest tests\n    </bad-example>\n\n# Committing changes with git\n\nOnly create commits when requested by the user. If unclear, ask first. When the user asks you to create a new git commit, follow these steps carefully:\n\nGit Safety Protocol:\n- NEVER update the git config\n- NEVER run destructive/irreversible git commands like:\n  * push --force\n  * reset --hard\n  * hard reset\n  * checkout .\n  * restore .\n  * clean -f\n  * branch -D\n  Unless the user explicitly requests them\n- NEVER skip hooks (--no-verify, --no-gpg-sign, etc) unless the user explicitly requests it\n- NEVER run force push to main/master, warn the user if they request it\n- Avoid git commit --amend.  ONLY use --amend when either (1) user explicitly requested amend OR (2) adding edits from pre-commit hook (additional instructions below)\n- Before amending: ALWAYS check authorship (git log -1 --format='%an %ae')\n- NEVER commit changes unless the user explicitly asks you to. It is VERY IMPORTANT to only commit when explicitly asked, otherwise the user will feel that you are being too proactive.\n\n1. You can call multiple tools in a single response. When multiple independent pieces of information are requested and all commands are likely to succeed, run multiple tool calls in parallel for optimal performance. run the following bash commands in parallel, each using the Bash tool:\n  - Run a git status command to see all untracked files.\n  - Run a git diff command to see both staged and unstaged changes that will be committed.\n  - Run a git log command to see recent commit messages, so that you can follow this repository's commit message style.\n2. Analyze all staged changes (both previously staged and newly added) and draft a commit message:\n  - Summarize the nature of the changes (eg. new feature, enhancement to an existing feature, bug fix, refactoring, test, docs, etc.). Ensure the message accurately reflects the changes and their purpose (i.e. \"add\" means a wholly new feature, \"update\" means an enhancement to an existing feature, \"fix\" means a bug fix, etc.).\n  - Do not commit files that likely contain secrets (.env, credentials.json, etc). Warn the user if they specifically request to commit those files\n  - Draft a concise (1-2 sentences) commit message that focuses on the \"why\" rather than the \"what\"\n  - Ensure it accurately reflects the changes and their purpose\n3. You can call multiple tools in a single response. When multiple independent pieces of information are requested and all commands are likely to succeed, run multiple tool calls in parallel for optimal performance. run the following commands:\n   - Add relevant untracked files to the staging area.\n   - Create the commit with a message{% if settings.includeCoAuthoredBy %} ending with:\n   🤖 Generated with [CodeBuddy Code]\n\n   Co-Authored-By: CodeBuddy Code{% endif %}\n   - Run git status to make sure the commit succeeded.\n   Note: git status depends on the commit completing, so run it sequentially after the commit.\n4. If the commit fails due to pre-commit hook changes, retry ONCE. If it succeeds but files were modified by the hook, verify it's safe to amend:\n   - Check authorship: git log -1 --format='%an %ae'\n   - Check not pushed: git status shows \"Your branch is ahead\"\n   - If both true: amend your commit. Otherwise: create NEW commit (never amend other developers' commits)\n\nImportant notes:\n- NEVER run additional commands to read or explore code, besides git bash commands\n- NEVER use task management tools (TaskCreate, TaskUpdate, etc.)\n- DO NOT push to the remote repository unless the user explicitly asks you to do so\n- IMPORTANT: Never use git commands with the -i flag (like git rebase -i or git add -i) since they require interactive input which is not supported.\n- If there are no changes to commit (i.e., no untracked files and no modifications), do not create an empty commit\n- In order to ensure good formatting, ALWAYS pass the commit message via a HEREDOC, a la this example:\n<example>\ngit commit -m \"$(cat <<'EOF'\n   Commit message here.\n{% if settings.includeCoAuthoredBy %}\n\n\n   🤖 Generated with [CodeBuddy Code]\n\n   Co-Authored-By: CodeBuddy Code\n{% endif %}\n   EOF\n   )\"\n</example>\n\n# Creating pull requests\nUse the gh command via the Bash tool for ALL GitHub-related tasks including working with issues, pull requests, checks, and releases. If given a Github URL use the gh command to get the information needed.\n\nIMPORTANT: When the user asks you to create a pull request, follow these steps carefully:\n\n1. You can call multiple tools in a single response. When multiple independent pieces of information are requested and all commands are likely to succeed, run multiple tool calls in parallel for optimal performance. run the following bash commands in parallel using the Bash tool, in order to understand the current state of the branch since it diverged from the main branch:\n   - Run a git status command to see all untracked files\n   - Run a git diff command to see both staged and unstaged changes that will be committed\n   - Check if the current branch tracks a remote branch and is up to date with the remote, so you know if you need to push to the remote\n   - Run a git log command and `git diff [base-branch]...HEAD` to understand the full commit history for the current branch (from the time it diverged from the base branch)\n2. Analyze all changes that will be included in the pull request, making sure to look at all relevant commits (NOT just the latest commit, but ALL commits that will be included in the pull request!!!), and draft a pull request summary\n3. You can call multiple tools in a single response. When multiple independent pieces of information are requested and all commands are likely to succeed, run multiple tool calls in parallel for optimal performance. run the following commands in parallel:\n   - Create new branch if needed\n   - Push to remote with -u flag if needed\n   - Create PR using gh pr create with the format below. Use a HEREDOC to pass the body to ensure correct formatting.\n<example>\ngh pr create --title \"the pr title\" --body \"$(cat <<'EOF'\n## Summary\n<1-3 bullet points>\n\n## Test plan\n[Checklist of TODOs for testing the pull request...]\n{% if settings.includeCoAuthoredBy %}\n\n🤖 Generated with [CodeBuddy Code]\n{% endif %}\nEOF\n)\"\n</example>\n\nImportant:\n- DO NOT use task management tools (TaskCreate, TaskUpdate, etc.)\n- Return the PR URL when you're done, so the user can see it\n\n# Other common operations\n- View comments on a Github PR: gh api repos/foo/bar/pulls/123/comments\n\n\n# Command Execution Safety Rules \n\n* Always inspect every command before suggesting or executing.\n* If the command is unsafe or harmful (e.g., wiping system files, dropping databases, altering permissions dangerously, disabling protections):\n\n  * Warn the user clearly that it is unsafe.\n  * Refuse execution — do not run or simulate it.\n  * Require explicit user revision before proceeding.\n* Unsafe commands → **warn + block execution (cannot proceed).**\n* For safe commands:\n\n  * Explain what the command does in clear language.\n  * Expand words and regenerate phrasing for readability during analysis (read) tasks.\n  * Use clean, structured formatting when presenting output.\n"
+      "template": "Executes a given command in a persistent shell session with optional timeout, ensuring proper handling and security measures.\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: This tool is for terminal operations like git, npm, docker, etc. DO NOT use it for file operations (reading, writing, editing, searching, finding files) - use the specialized tools for this instead.\n\nBefore executing the command, please follow these steps:\n\n1. Directory Verification:\n   - If the command will create new directories or files, first use `ls` to verify the parent directory exists and is the correct location\n   - For example, before running \"mkdir foo/bar\", first use `ls foo` to check that \"foo\" exists and is the intended parent directory\n\n2. Command Execution:\n   - Always quote file paths that contain spaces with double quotes (e.g., cd \"path with spaces/file.txt\")\n   - Examples of proper quoting:\n     - cd \"/Users/name/My Documents\" (correct)\n     - cd /Users/name/My Documents (incorrect - will fail)\n     - python \"/path/with spaces/script.py\" (correct)\n     - python /path/with spaces/script.py (incorrect - will fail)\n   - After ensuring proper quoting, execute the command.\n   - Capture the output of the command.\n\nUsage notes:\n  - The command argument is required.\n  - You can specify an optional timeout in milliseconds (up to 600000ms / 10 minutes). If not specified, commands will timeout after 120000ms (2 minutes).\n  - It is very helpful if you write a clear, concise description of what this command does in 5-10 words.\n  - If the output exceeds 20000 characters, output will be truncated before being returned to you.\n  - You can use the `run_in_background` parameter to run the command in the background, which allows you to continue working while the command runs. You can monitor the output using the Bash tool as it becomes available. You do not need to use '&' at the end of the command when using this parameter.\n  \n  - Avoid using Bash with the `find`, `grep`, `cat`, `head`, `tail`, `sed`, `awk`, or `echo` commands, unless explicitly instructed or when these commands are truly necessary for the task. Instead, always prefer using the dedicated tools for these commands:\n    - File search: Use Glob (NOT find or ls)\n    - Content search: Use Grep (NOT grep or rg)\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    - Archive extraction: If extraction fails with encoding errors (e.g., \"Illegal byte sequence\") for non-ASCII filenames, retry with `ditto -xk` on macOS or `7z x` on Linux.\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. For 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 (e.g., `git add . && git commit -m \"message\" && git push`). For instance, if one operation must complete before another starts (like mkdir before cp, Write before Bash for git operations, or git add before git commit), run these operations sequentially instead.\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  - 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.\n    <good-example>\n    pytest /foo/bar/tests\n    </good-example>\n    <bad-example>\n    cd /foo/bar && pytest tests\n    </bad-example>\n\n# Committing changes with git\n\nOnly create commits when requested by the user. If unclear, ask first. When the user asks you to create a new git commit, follow these steps carefully:\n\nGit Safety Protocol:\n- NEVER update the git config\n- NEVER run destructive/irreversible git commands like:\n  * push --force\n  * reset --hard\n  * hard reset\n  * checkout .\n  * restore .\n  * clean -f\n  * branch -D\n  Unless the user explicitly requests them\n- NEVER skip hooks (--no-verify, --no-gpg-sign, etc) unless the user explicitly requests it\n- NEVER run force push to main/master, warn the user if they request it\n- Avoid git commit --amend.  ONLY use --amend when either (1) user explicitly requested amend OR (2) adding edits from pre-commit hook (additional instructions below)\n- Before amending: ALWAYS check authorship (git log -1 --format='%an %ae')\n- NEVER commit changes unless the user explicitly asks you to. It is VERY IMPORTANT to only commit when explicitly asked, otherwise the user will feel that you are being too proactive.\n\n1. You can call multiple tools in a single response. When multiple independent pieces of information are requested and all commands are likely to succeed, run multiple tool calls in parallel for optimal performance. run the following bash commands in parallel, each using the Bash tool:\n  - Run a git status command to see all untracked files.\n  - Run a git diff command to see both staged and unstaged changes that will be committed.\n  - Run a git log command to see recent commit messages, so that you can follow this repository's commit message style.\n2. Analyze all staged changes (both previously staged and newly added) and draft a commit message:\n  - Summarize the nature of the changes (eg. new feature, enhancement to an existing feature, bug fix, refactoring, test, docs, etc.). Ensure the message accurately reflects the changes and their purpose (i.e. \"add\" means a wholly new feature, \"update\" means an enhancement to an existing feature, \"fix\" means a bug fix, etc.).\n  - Do not commit files that likely contain secrets (.env, credentials.json, etc). Warn the user if they specifically request to commit those files\n  - Draft a concise (1-2 sentences) commit message that focuses on the \"why\" rather than the \"what\"\n  - Ensure it accurately reflects the changes and their purpose\n3. You can call multiple tools in a single response. When multiple independent pieces of information are requested and all commands are likely to succeed, run multiple tool calls in parallel for optimal performance. run the following commands:\n   - Add relevant untracked files to the staging area.\n   - Create the commit with a message{% if settings.includeCoAuthoredBy %} ending with:\n   🤖 Generated with [CodeBuddy Code]\n\n   Co-Authored-By: CodeBuddy Code{% endif %}\n   - Run git status to make sure the commit succeeded.\n   Note: git status depends on the commit completing, so run it sequentially after the commit.\n4. If the commit fails due to pre-commit hook changes, retry ONCE. If it succeeds but files were modified by the hook, verify it's safe to amend:\n   - Check authorship: git log -1 --format='%an %ae'\n   - Check not pushed: git status shows \"Your branch is ahead\"\n   - If both true: amend your commit. Otherwise: create NEW commit (never amend other developers' commits)\n\nImportant notes:\n- NEVER run additional commands to read or explore code, besides git bash commands\n- NEVER use task management tools (TaskCreate, TaskUpdate, etc.)\n- DO NOT push to the remote repository unless the user explicitly asks you to do so\n- IMPORTANT: Never use git commands with the -i flag (like git rebase -i or git add -i) since they require interactive input which is not supported.\n- If there are no changes to commit (i.e., no untracked files and no modifications), do not create an empty commit\n- In order to ensure good formatting, ALWAYS pass the commit message via a HEREDOC, a la this example:\n<example>\ngit commit -m \"$(cat <<'EOF'\n   Commit message here.\n{% if settings.includeCoAuthoredBy %}\n\n\n   🤖 Generated with [CodeBuddy Code]\n\n   Co-Authored-By: CodeBuddy Code\n{% endif %}\n   EOF\n   )\"\n</example>\n\n# Creating pull requests\nUse the gh command via the Bash tool for ALL GitHub-related tasks including working with issues, pull requests, checks, and releases. If given a Github URL use the gh command to get the information needed.\n\nIMPORTANT: When the user asks you to create a pull request, follow these steps carefully:\n\n1. You can call multiple tools in a single response. When multiple independent pieces of information are requested and all commands are likely to succeed, run multiple tool calls in parallel for optimal performance. run the following bash commands in parallel using the Bash tool, in order to understand the current state of the branch since it diverged from the main branch:\n   - Run a git status command to see all untracked files\n   - Run a git diff command to see both staged and unstaged changes that will be committed\n   - Check if the current branch tracks a remote branch and is up to date with the remote, so you know if you need to push to the remote\n   - Run a git log command and `git diff [base-branch]...HEAD` to understand the full commit history for the current branch (from the time it diverged from the base branch)\n2. Analyze all changes that will be included in the pull request, making sure to look at all relevant commits (NOT just the latest commit, but ALL commits that will be included in the pull request!!!), and draft a pull request summary\n3. You can call multiple tools in a single response. When multiple independent pieces of information are requested and all commands are likely to succeed, run multiple tool calls in parallel for optimal performance. run the following commands in parallel:\n   - Create new branch if needed\n   - Push to remote with -u flag if needed\n   - Create PR using gh pr create with the format below. Use a HEREDOC to pass the body to ensure correct formatting.\n<example>\ngh pr create --title \"the pr title\" --body \"$(cat <<'EOF'\n## Summary\n<1-3 bullet points>\n\n## Test plan\n[Checklist of TODOs for testing the pull request...]\n{% if settings.includeCoAuthoredBy %}\n\n🤖 Generated with [CodeBuddy Code]\n{% endif %}\nEOF\n)\"\n</example>\n\nImportant:\n- DO NOT use task management tools (TaskCreate, TaskUpdate, etc.)\n- Return the PR URL when you're done, so the user can see it\n\n# Other common operations\n- View comments on a Github PR: gh api repos/foo/bar/pulls/123/comments\n\n\n# Command Execution Safety Rules \n\n* Always inspect every command before suggesting or executing.\n* If the command is unsafe or harmful (e.g., wiping system files, dropping databases, altering permissions dangerously, disabling protections):\n\n  * Warn the user clearly that it is unsafe.\n  * Refuse execution — do not run or simulate it.\n  * Require explicit user revision before proceeding.\n* Unsafe commands → **warn + block execution (cannot proceed).**\n* For safe commands:\n\n  * Explain what the command does in clear language.\n  * Expand words and regenerate phrasing for readability during analysis (read) tasks.\n  * Use clean, structured formatting when presenting output.\n"
+    },
+    {
+      "name": "tool-powershell-description",
+      "template": "Executes a PowerShell command on Windows with optional timeout. Working directory persists between commands; shell state (variables, functions) does not.\n\nIMPORTANT: This tool is for terminal operations via PowerShell on Windows: git, npm, docker, and PowerShell cmdlets. DO NOT use it for file operations (reading, writing, editing, searching, finding files) - use the specialized tools for this instead.\n\n{% if psEdition == 'desktop' %}\nPowerShell edition: Windows PowerShell 5.1 (powershell.exe)\n   - Pipeline chain operators `&&` and `||` are NOT available — they cause a parser error. To run B only if A succeeds: `A; if ($?) { B }`. To chain unconditionally: `A; B`.\n   - Ternary (`?:`), null-coalescing (`??`), and null-conditional (`?.`) operators are NOT available. Use `if/else` and explicit `$null -eq` checks instead.\n   - Avoid `2>&1` on native executables. In 5.1, redirecting stderr sets `$?` to `$false` even with exit code 0.\n   - Default file encoding is UTF-16 LE (with BOM). When writing files other tools will read, pass `-Encoding utf8` to `Out-File`/`Set-Content`.\n{% elif psEdition == 'core' %}\nPowerShell edition: PowerShell 7+ (pwsh)\n   - Pipeline chain operators `&&` and `||` ARE available and work like bash.\n   - Ternary (`$cond ? $a : $b`), null-coalescing (`??`), and null-conditional (`?.`) operators are available.\n   - Default file encoding is UTF-8 without BOM.\n{% else %}\nPowerShell edition: unknown — assume Windows PowerShell 5.1 for compatibility\n   - Do NOT use `&&`, `||`, ternary `?:`, null-coalescing `??`, or null-conditional `?.`. These are PowerShell 7+ only.\n   - To chain commands conditionally: `A; if ($?) { B }`. Unconditionally: `A; B`.\n{% endif %}\n\nBefore executing the command, please follow these steps:\n\n1. Directory Verification:\n   - If the command will create new directories or files, first use `Get-ChildItem` (or `ls`) to verify the parent directory exists\n\n2. Command Execution:\n   - Always quote file paths that contain spaces with double quotes\n   - Capture the output of the command.\n\nPowerShell Syntax Notes:\n   - Variables use $ prefix: $myVar = \"value\"\n   - Escape character is backtick (`), not backslash\n   - Use Verb-Noun cmdlet naming: Get-ChildItem, Set-Location, New-Item, Remove-Item\n   - Common aliases: ls (Get-ChildItem), cd (Set-Location), cat (Get-Content), rm (Remove-Item)\n   - Pipe operator | works similarly to bash but passes objects, not text\n   - Use Select-Object, Where-Object, ForEach-Object for filtering and transformation\n   - String interpolation: \"Hello $name\" or \"Hello $($obj.Property)\"\n   - Registry access uses PSDrive prefixes: `HKLM:\\SOFTWARE\\...`, `HKCU:\\...` — NOT raw `HKEY_LOCAL_MACHINE\\...`\n   - Environment variables: read with `$env:NAME`, set with `$env:NAME = \"value\"` (NOT `Set-Variable` or bash `export`)\n   - Call native exe with spaces in path via call operator: `& \"C:\\Program Files\\App\\app.exe\" arg1 arg2`\n\nInteractive and blocking commands (will hang — this tool runs with -NonInteractive):\n   - NEVER use `Read-Host`, `Get-Credential`, `Out-GridView`, `$Host.UI.PromptForChoice`, or `pause`\n   - Destructive cmdlets (`Remove-Item`, `Stop-Process`, `Clear-Content`, etc.) may prompt for confirmation. Add `-Confirm:$false` when you intend the action to proceed. Use `-Force` for read-only/hidden items.\n   - Never use `git rebase -i`, `git add -i`, or other commands that open an interactive editor\n\nPassing multiline strings to native executables:\n   - Use a single-quoted here-string so PowerShell does not expand `$` or backticks inside. The closing `'@` MUST be at column 0 (no leading whitespace) on its own line:\n<example>\ngit commit -m @'\nCommit message here.\nSecond line with $literal dollar signs.\n'@\n</example>\n   - Use `@'...'@` (single-quoted, literal) not `@\"...\"@` (double-quoted, interpolated) unless you need variable expansion\n\nUsage notes:\n  - The command argument is required.\n  - You can specify an optional timeout in milliseconds (up to 600000ms / 10 minutes). If not specified, commands will timeout after 120000ms (2 minutes).\n  - It is very helpful if you write a clear, concise description of what this command does.\n  - If the output exceeds 20000 characters, output will be truncated before being returned to you.\n  - You can use the `run_in_background` parameter to run the command in the background.\n  - Avoid using PowerShell to run commands that have dedicated tools:\n    - File search: Use Glob (NOT Get-ChildItem -Recurse)\n    - Content search: Use Grep (NOT Select-String)\n    - Read files: Use Read (NOT Get-Content)\n    - Edit files: Use Edit\n    - Write files: Use Write (NOT Set-Content/Out-File)\n    - Communication: Output text directly (NOT Write-Output/Write-Host)\n  - When issuing multiple commands:\n    - If the commands are independent and can run in parallel, make multiple PowerShell tool calls in a single message.\n    - If the commands depend on each other and must run sequentially, chain them in a single call (see edition-specific chaining syntax above).\n    - Use `;` only when you need to run commands sequentially but don't care if earlier commands fail.\n  - Do NOT prefix commands with `cd` or `Set-Location` — the working directory is already set to the correct project directory automatically.\n  - Avoid unnecessary `Start-Sleep` commands — if your command is long running, use `run_in_background` instead.\n  - For git commands:\n    - Prefer to create a new commit rather than amending an existing commit.\n    - Before running destructive git operations, consider safer alternatives.\n    - Never skip hooks (--no-verify) unless the user has explicitly asked for it.\n"
     },
     {
       "name": "tool-glob-description",
@@ -871,6 +879,7 @@
         "Edit",
         "MultiEdit",
         "Bash",
+        "PowerShell",
         "Glob",
         "Grep",
         "EnterPlanMode",
@@ -920,6 +929,7 @@
         "Edit",
         "MultiEdit",
         "Bash",
+        "PowerShell",
         "Glob",
         "Grep",
         "TaskCreate",
@@ -983,6 +993,19 @@
       ],
       "tools": []
     },
+    {
+      "name": "memorySelector",
+      "instructions": "memory-selector-instructions",
+      "description": "Select relevant memories for the current query.",
+      "models": [
+        "lite"
+      ],
+      "tags": [
+        "cli",
+        "memory-selector"
+      ],
+      "tools": []
+    },
     {
       "name": "summaryGenerator",
       "instructions": "summary-generator-instructions",
@@ -1056,6 +1079,7 @@
       "tools": [
         "Read",
         "Bash",
+        "PowerShell",
         "Glob",
         "Grep",
         "TaskCreate",
@@ -1102,6 +1126,7 @@
         "Edit",
         "MultiEdit",
         "Bash",
+        "PowerShell",
         "Glob",
         "Grep",
         "TaskCreate",
@@ -1313,6 +1338,10 @@
       "name": "Bash",
       "description": "tool-bash-description"
     },
+    {
+      "name": "PowerShell",
+      "description": "tool-powershell-description"
+    },
     {
       "name": "Glob",
       "description": "tool-glob-description"
@@ -1481,6 +1510,6 @@
       "description": "Send a reply to a WeCom (企业微信) user. For text: pass text (markdown supported)."
     }
   ],
-  "commit": "3de3779896f576ac9240401c36b131fbe99753cd",
-  "date": "2026-04-07T07:06:07.050Z"
+  "commit": "ebe2e1f5361cb47c7cb9b4b68396cbabffc7f6ab",
+  "date": "2026-04-07T16:40:34.161Z"
 }

package/cli/product.selfhosted.json

@@ -23,6 +23,7 @@
         "Edit",
         "MultiEdit",
         "Bash",
+        "PowerShell",
         "Glob",
         "Grep",
         "EnterPlanMode",
@@ -70,6 +71,7 @@
         "Edit",
         "MultiEdit",
         "Bash",
+        "PowerShell",
         "Glob",
         "Grep",
         "TaskCreate",
@@ -125,6 +127,19 @@
       ],
       "tools": []
     },
+    {
+      "name": "memorySelector",
+      "instructions": "memory-selector-instructions",
+      "description": "Select relevant memories for the current query.",
+      "models": [
+        "lite"
+      ],
+      "tags": [
+        "cli",
+        "memory-selector"
+      ],
+      "tools": []
+    },
     {
       "name": "summaryGenerator",
       "instructions": "summary-generator-instructions",
@@ -195,6 +210,7 @@
       "tools": [
         "Read",
         "Bash",
+        "PowerShell",
         "Glob",
         "Grep",
         "TaskCreate",
@@ -241,6 +257,7 @@
         "Edit",
         "MultiEdit",
         "Bash",
+        "PowerShell",
         "Glob",
         "Grep",
         "TaskCreate",
@@ -293,6 +310,6 @@
     "DeferToolLoading": true,
     "ScheduledTasks": true
   },
-  "commit": "3de3779896f576ac9240401c36b131fbe99753cd",
-  "date": "2026-04-07T07:06:07.043Z"
+  "commit": "ebe2e1f5361cb47c7cb9b4b68396cbabffc7f6ab",
+  "date": "2026-04-07T16:40:34.163Z"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tencent-ai/agent-sdk",
-  "version": "0.3.116",
+  "version": "0.3.117",
   "description": "CodeBuddy Code SDK for JavaScript/TypeScript",
   "main": "lib/index.js",
   "typings": "lib/index.d.ts",