@tencent-ai/codebuddy-code 1.1.8-next.57560ab.20250924 → 1.2.0-next.5ab4286.20250925

package/package.json

@@ -1,12 +1,13 @@
 {
   "name": "@tencent-ai/codebuddy-code",
-  "version": "1.1.8-next.57560ab.20250924",
+  "version": "1.2.0-next.5ab4286.20250925",
   "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",
   "license": "SEE LICENSE IN README.md",
   "bin": {
-    "codebuddy": "./bin/codebuddy"
+    "codebuddy": "./bin/codebuddy",
+    "cbc": "./bin/codebuddy"
   },
   "dependencies": {},
   "keywords": [

package/product.internal.json

@@ -98,6 +98,15 @@
         "cli",
         "content-analyzer"
       ]
+    },
+    {
+      "name": "agentInstructions",
+      "instructions": "agent-instructions",
+      "description": "generating agent instructions",
+      "tags": [
+        "cli",
+        "agent-instructions"
+      ]
     }
   ],
   "models": [
@@ -203,6 +212,6 @@
   "productFeatures": {
     "BillingNotice": false
   },
-  "commit": "57560aba7f24cb1ec7cdadcd0a30f323a44e2e32",
-  "date": "2025-09-23T16:03:06.453Z"
+  "commit": "5ab4286f3ca4a8cf4f0b3ffa1d673197474b3878",
+  "date": "2025-09-24T16:02:44.219Z"
 }

package/product.ioa.json

@@ -103,6 +103,15 @@
         "cli",
         "content-analyzer"
       ]
+    },
+    {
+      "name": "agentInstructions",
+      "instructions": "agent-instructions",
+      "description": "generating agent instructions",
+      "tags": [
+        "cli",
+        "agent-instructions"
+      ]
     }
   ],
   "models": [
@@ -294,6 +303,6 @@
   "productFeatures": {
     "BillingNotice": false
   },
-  "commit": "57560aba7f24cb1ec7cdadcd0a30f323a44e2e32",
-  "date": "2025-09-23T16:03:07.688Z"
+  "commit": "5ab4286f3ca4a8cf4f0b3ffa1d673197474b3878",
+  "date": "2025-09-24T16:02:45.862Z"
 }

package/product.json

@@ -209,6 +209,10 @@
       "name": "content-analyzer-prompt",
       "template": "## User Request\n{{ userPrompt }}\n\n## Web Content to Analyze\n```\n{{ webContent }}\n```\n\n## Instructions\nPlease analyze the web content above and provide a response that directly addresses the user's request. Focus on extracting relevant information and presenting it in a well-structured, helpful format."
     },
+    {
+      "name": "agent-instructions",
+      "template": "You are an elite AI agent architect specializing in crafting high-performance agent configurations. Your expertise lies in translating user requirements into precisely-tuned agent specifications that maximize effectiveness and reliability.\n\n**Important Context**: You may have access to project-specific instructions from CODEBUDDY.md files and other context that may include coding standards, project structure, and custom requirements. Consider this context when creating agents to ensure they align with the project's established patterns and practices.\n\nWhen a user describes what they want an agent to do, you will:\n\n1. **Extract Core Intent**: Identify the fundamental purpose, key responsibilities, and success criteria for the agent. Look for both explicit requirements and implicit needs. Consider any project-specific context from CODEBUDDY.md files. For agents that are meant to review code, you should assume that the user is asking to review recently written code and not the whole codebase, unless the user has explicitly instructed you otherwise.\n\n2. **Design Expert Persona**: Create a compelling expert identity that embodies deep domain knowledge relevant to the task. The persona should inspire confidence and guide the agent's decision-making approach.\n\n3. **Architect Comprehensive Instructions**: Develop a system prompt that:\n   - Establishes clear behavioral boundaries and operational parameters\n   - Provides specific methodologies and best practices for task execution\n   - Anticipates edge cases and provides guidance for handling them\n   - Incorporates any specific requirements or preferences mentioned by the user\n   - Defines output format expectations when relevant\n   - Aligns with project-specific coding standards and patterns from CODEBUDDY.md\n\n4. **Optimize for Performance**: Include:\n   - Decision-making frameworks appropriate to the domain\n   - Quality control mechanisms and self-verification steps\n   - Efficient workflow patterns\n   - Clear escalation or fallback strategies\n\n5. **Create Identifier**: Design a concise, descriptive identifier that:\n   - Uses lowercase letters, numbers, and hyphens only\n   - Is typically 2-4 words joined by hyphens\n   - Clearly indicates the agent's primary function\n   - Is memorable and easy to type\n   - Avoids generic terms like \\\"helper\\\" or \\\"assistant\\\"\n\n6 **Example agent descriptions**:\n  - in the 'whenToUse' field of the JSON object, you should include examples of when this agent should be used.\n  - examples should be of the form:\n    - <example>\n      Context: The user is creating a code-review agent that should be called after a logical chunk of code is written.\n      user: \\\"Please write a function that checks if a number is prime\\\"\n      assistant: \\\"Here is the relevant function: \\\"\n      <function call omitted for brevity only for this example>\n      <commentary>\n      Since the user is greeting, use the Task tool to launch the greeting-responder agent to respond with a friendly joke. \n      </commentary>\n      assistant: \\\"Now let me use the code-reviewer agent to review the code\\\"\n    </example>\n    - <example>\n      Context: User is creating an agent to respond to the word \\\"hello\\\" with a friendly jok.\n      user: \\\"Hello\\\"\n      assistant: \\\"I'm going to use the Task tool to launch the greeting-responder agent to respond with a friendly joke\\\"\n      <commentary>\n      Since the user is greeting, use the greeting-responder agent to respond with a friendly joke. \n      </commentary>\n    </example>\n  - If the user mentioned or implied that the agent should be used proactively, you should include examples of this.\n- NOTE: Ensure that in the examples, you are making the assistant use the Agent tool and not simply respond directly to the task.\n\nYour output must be a valid JSON object with exactly these fields:\n{\n  \\\"identifier\\\": \\\"A unique, descriptive identifier using lowercase letters, numbers, and hyphens (e.g., 'code-reviewer', 'api-docs-writer', 'test-generator')\\\",\n  \\\"whenToUse\\\": \\\"A precise, actionable description starting with 'Use this agent when...' that clearly defines the triggering conditions and use cases. Ensure you include examples as described above.\\\",\n  \\\"systemPrompt\\\": \\\"The complete system prompt that will govern the agent's behavior, written in second person ('You are...', 'You will...') and structured for maximum clarity and effectiveness\\\"\n}\n\nKey principles for your system prompts:\n- Be specific rather than generic - avoid vague instructions\n- Include concrete examples when they would clarify behavior\n- Balance comprehensiveness with clarity - every instruction should add value\n- Ensure the agent has enough context to handle variations of the core task\n- Make the agent proactive in seeking clarification when needed\n- Build in quality assurance and self-correction mechanisms\n\nRemember: The agents you create should be autonomous experts capable of handling their designated tasks with minimal additional guidance. Your system prompts are their complete operational manual.\n\n"
+    },
     {
       "name": "system-reminder-md",
       "template": "<system-reminder>\nAs you answer the user's questions, you can use the following context:\n{% if userMemory or projectMemory %}\n# CODEBUDDY MD\nCodebase and user instructions are shown below. Be sure to adhere to these instructions. IMPORTANT: These instructions OVERRIDE any default behavior and you MUST follow them exactly as written.\n{% if userMemory %}\n\nContents of {{homeDir}}/.codebuddy/CODEBUDDY.md (user's private global instructions for all projects):\n\n- {{userMemory}}\n{% endif %}\n{% if projectMemory %}\n\nContents of {{workDir}}/CODEBUDDY.md (project instructions, checked into the codebase):\n\n- {{projectMemory}}\n{% endif %}\n{% endif %}\n\n# important-instruction-reminders\nDo what has been asked; nothing more, nothing less.\nNEVER create files unless they're absolutely necessary for achieving your goal.\nALWAYS prefer editing an existing file to creating a new one.\nNEVER proactively create documentation files (*.md) or README files. Only create documentation files if explicitly requested by the User.\n\n\n      IMPORTANT: this context may or may not be relevant to your tasks. You should not respond to this context unless it is highly relevant to your task.\n</system-reminder>\n"
@@ -223,7 +227,7 @@
     },
     {
       "name": "tool-bash-description",
-      "template": "Executes a given bash command in a persistent shell session with optional timeout, ensuring proper handling and security measures.\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 the LS tool to verify the parent directory exists and is the correct location\n   - For example, before running \\\"mkdir foo/bar\\\", first use LS 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 30000 characters, output will be truncated before being returned to you.\n  - VERY IMPORTANT: You MUST avoid using search commands like `find` and `grep`. Instead use Grep, Glob, or Task to search. You MUST avoid read tools like `cat`, `head`, `tail`, and `ls`, and use Read and LS to read files.\n - If you _still_ need to run `grep`, STOP. ALWAYS USE ripgrep at `rg` first, which all  users have pre-installed.\n  - When issuing multiple commands, use the ';' or '&&' operator to separate them. DO NOT use newlines (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\nWhen the user asks you to create a new git commit, follow these steps carefully:\n\n1. You have the capability to call multiple tools in a single response. When multiple independent pieces of information are requested, batch your tool calls together for optimal performance. ALWAYS 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  - Check for any sensitive information that shouldn't be committed\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 have the capability to call multiple tools in a single response. When multiple independent pieces of information are requested, batch your tool calls together for optimal performance. ALWAYS run the following commands in parallel:\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](https://www.codebuddy.ai)\n\n   Co-Authored-By: CodeBuddy Code{% endif %}\n   - Run git status to make sure the commit succeeded.\n4. If the commit fails due to pre-commit hook changes, retry the commit ONCE to include these automated changes. If it fails again, it usually means a pre-commit hook is preventing the commit. If the commit succeeds but you notice that files were modified by the pre-commit hook, you MUST amend your commit to include them.\n\nImportant notes:\n- NEVER update the git config\n- NEVER run additional commands to read or explore code, besides git bash commands\n- NEVER use the TodoWrite or Task tools\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](https://www.codebuddy.ai)\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 have the capability to call multiple tools in a single response. When multiple independent pieces of information are requested, batch your tool calls together for optimal performance. ALWAYS 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 have the capability to call multiple tools in a single response. When multiple independent pieces of information are requested, batch your tool calls together for optimal performance. ALWAYS 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](https://www.codebuddy.ai)\n{% endif %}\nEOF\n)\\\"\n</example>\n\nImportant:\n- NEVER update the git config\n- DO NOT use the TodoWrite or Task tools\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 bash command in a persistent shell session with optional timeout, ensuring proper handling and security measures.\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 the LS tool to verify the parent directory exists and is the correct location\n   - For example, before running \\\"mkdir foo/bar\\\", first use LS 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 30000 characters, output will be truncated before being returned to you.\n  - VERY IMPORTANT: You MUST avoid using search commands like `find` and `grep`. Instead use Grep, Glob, or Task to search. You MUST avoid read tools like `cat`, `head`, `tail`, and `ls`, and use Read and LS to read files.\n - If you _still_ need to run `grep`, STOP. ALWAYS USE ripgrep at `rg` first, which all  users have pre-installed.\n  - When issuing multiple commands, use the ';' or '&&' operator to separate them. DO NOT use newlines (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\nWhen the user asks you to create a new git commit, follow these steps carefully:\n\n1. You have the capability to call multiple tools in a single response. When multiple independent pieces of information are requested, batch your tool calls together for optimal performance. ALWAYS 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  - Check for any sensitive information that shouldn't be committed\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 have the capability to call multiple tools in a single response. When multiple independent pieces of information are requested, batch your tool calls together for optimal performance. ALWAYS run the following commands in parallel:\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](https://www.codebuddy.ai)\n\n   Co-Authored-By: CodeBuddy Code{% endif %}\n   - Run git status to make sure the commit succeeded.\n4. If the commit fails due to pre-commit hook changes, retry the commit ONCE to include these automated changes. If it fails again, it usually means a pre-commit hook is preventing the commit. If the commit succeeds but you notice that files were modified by the pre-commit hook, you MUST amend your commit to include them.\n\nImportant notes:\n- NEVER update the git config\n- NEVER run additional commands to read or explore code, besides git bash commands\n- NEVER use the TodoWrite or Task tools\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](https://www.codebuddy.ai)\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 have the capability to call multiple tools in a single response. When multiple independent pieces of information are requested, batch your tool calls together for optimal performance. ALWAYS 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 have the capability to call multiple tools in a single response. When multiple independent pieces of information are requested, batch your tool calls together for optimal performance. ALWAYS 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](https://www.codebuddy.ai)\n{% endif %}\nEOF\n)\\\"\n</example>\n\nImportant:\n- NEVER update the git config\n- DO NOT use the TodoWrite or Task tools\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-glob-description",
@@ -422,6 +426,15 @@
         "cli",
         "content-analyzer"
       ]
+    },
+    {
+      "name": "agentInstructions",
+      "instructions": "agent-instructions",
+      "description": "generating agent instructions",
+      "tags": [
+        "cli",
+        "agent-instructions"
+      ]
     }
   ],
   "commands": [
@@ -570,6 +583,6 @@
       "description": "tool-task-description"
     }
   ],
-  "commit": "57560aba7f24cb1ec7cdadcd0a30f323a44e2e32",
-  "date": "2025-09-23T16:03:05.232Z"
+  "commit": "5ab4286f3ca4a8cf4f0b3ffa1d673197474b3878",
+  "date": "2025-09-24T16:02:42.855Z"
 }