@tencent-ai/codebuddy-code 2.72.0 → 2.74.0

package/package.json

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

@@ -404,6 +404,6 @@
     "ImageGen": true,
     "ScheduledTasks": true
   },
-  "commit": "277deb67cf55c3da0c467152a68351baeb810355",
-  "date": "2026-04-01T19:03:51.939Z"
+  "commit": "c3438a704868be5c7a92611d5866d4da1d8bf7e5",
+  "date": "2026-04-03T04:02:40.548Z"
 }

package/product.internal.json

@@ -534,6 +534,6 @@
       }
     }
   },
-  "commit": "277deb67cf55c3da0c467152a68351baeb810355",
-  "date": "2026-04-01T19:03:52.052Z"
+  "commit": "c3438a704868be5c7a92611d5866d4da1d8bf7e5",
+  "date": "2026-04-03T04:02:40.627Z"
 }

package/product.ioa.json

@@ -892,6 +892,6 @@
       }
     }
   },
-  "commit": "277deb67cf55c3da0c467152a68351baeb810355",
-  "date": "2026-04-01T19:03:52.005Z"
+  "commit": "c3438a704868be5c7a92611d5866d4da1d8bf7e5",
+  "date": "2026-04-03T04:02:40.629Z"
 }

package/product.json

@@ -478,7 +478,7 @@
     },
     {
       "name": "compact-prompt",
-      "template": "Your task is to create a detailed summary of the conversation so far, paying close attention to the user's explicit requests and your previous actions.\nThis summary should be thorough in capturing technical details, code patterns, and architectural decisions that would be essential for continuing development work without losing context.\n\nBefore providing your final summary, wrap your analysis in <analysis> tags to organize your thoughts and ensure you've covered all necessary points. In your analysis process:\n\n1. Chronologically analyze each message and section of the conversation. For each section thoroughly identify:\n   - The user's explicit requests and intents\n   - Your approach to addressing the user's requests\n   - Key decisions, technical concepts and code patterns\n   - Specific details like:\n     - file names\n     - full code snippets\n     - function signatures\n     - file edits\n   - Errors that you ran into and how you fixed them\n   - Pay special attention to specific user feedback that you received, especially if the user told you to do something differently.\n2. Double-check for technical accuracy and completeness, addressing each required element thoroughly.\n\nYour summary should include the following sections:\n\n1. Primary Request and Intent: Capture all of the user's explicit requests and intents in detail\n2. Key Technical Concepts: List all important technical concepts, technologies, and frameworks discussed.\n3. Files and Code Sections: Enumerate specific files and code sections examined, modified, or created. Pay special attention to the most recent messages and include full code snippets where applicable and include a summary of why this file read or edit is important.\n4. Errors and fixes: List all errors that you ran into, and how you fixed them. Pay special attention to specific user feedback that you received, especially if the user told you to do something differently.\n5. Problem Solving: Document problems solved and any ongoing troubleshooting efforts.\n6. All user messages: List ALL user messages that are not tool results. These are critical for understanding the users' feedback and changing intent.\n7. Pending Tasks: Outline any pending tasks that you have explicitly been asked to work on.\n8. Current Work: Describe in detail precisely what was being worked on immediately before this summary request, paying special attention to the most recent messages from both user and assistant. Include file names and code snippets where applicable.\n9. Optional Next Step: List the next step that you will take that is related to the most recent work you were doing. IMPORTANT: ensure that this step is DIRECTLY in line with the user's most recent explicit requests, and the task you were working on immediately before this summary request. If your last task was concluded, then only list next steps if they are explicitly in line with the users request. Do not start on tangential requests or really old requests that were already completed without confirming with the user first.\n                       If there is a next step, include direct quotes from the most recent conversation showing exactly what task you were working on and where you left off. This should be verbatim to ensure there's no drift in task interpretation.\n\nHere's an example of how your output should be structured:\n\n<example>\n<conversation_history_summary>\n<analysis>\n[Your thought process, ensuring all points are covered thoroughly and accurately]\n</analysis>\n\n<summary>\n1. Primary Request and Intent:\n   [Detailed description]\n\n2. Key Technical Concepts:\n   - [Concept 1]\n   - [Concept 2]\n   - [...]\n\n3. Files and Code Sections:\n   - [File Name 1]\n      - [Summary of why this file is important]\n      - [Summary of the changes made to this file, if any]\n      - [Important Code Snippet]\n   - [File Name 2]\n      - [Important Code Snippet]\n   - [...]\n\n4. Errors and fixes:\n    - [Detailed description of error 1]:\n      - [How you fixed the error]\n      - [User feedback on the error if any]\n    - [...]\n\n5. Problem Solving:\n   [Description of solved problems and ongoing troubleshooting]\n\n6. All user messages: \n    - [Detailed non tool use user message]\n    - [...]\n\n7. Pending Tasks:\n   - [Task 1]\n   - [Task 2]\n   - [...]\n\n8. Current Work:\n   [Precise description of current work]\n\n9. Optional Next Step:\n   [Optional Next step to take]\n\n</summary>\n</conversation_history_summary>\n</example>\n\nPlease provide your summary based on the conversation so far, following this structure and ensuring precision and thoroughness in your response. \n\nThere may be additional summarization instructions provided in the included context. If so, remember to follow these instructions when creating the above summary. Examples of instructions include:\n<example>\n## Compact Instructions\nWhen summarizing the conversation focus on typescript code changes and also remember the mistakes you made and how you fixed them.\n</example>\n\n<example>\n# Summary instructions\nWhen you are using compact - please focus on test output and code changes. Include file reads verbatim.\n</example>\n\n\nIMPORTANT: Do NOT use any tools. You MUST respond with the complete <conversation_history_summary> structure as shown in the example above. Your output MUST follow this exact format:\n\n<conversation_history_summary>\n<analysis>\n[Your analysis here]\n</analysis>\n\n<summary>\n[Your summary here following the 9-section structure]\n</summary>\n</conversation_history_summary>\n"
+      "template": "**IMPORTANT CONSTRAINTS:**\n- Do NOT use any tools (Read, Write, Execute, etc.)\n- Do NOT run any commands\n- Your ONLY output should be the <conversation_history_summary> structure\n- Focus on precise extraction and synthesis, not regeneration\n\nYour task is to create a detailed summary of the conversation so far, paying close attention to the user's explicit requests and your previous actions.\nThis summary should be thorough in capturing technical details, code patterns, architectural decisions, and implementation specifics that would be essential for continuing development work without losing context.\n\nBefore providing your final summary, organize your thoughts in <analysis> tags to ensure you've covered all necessary points. In your analysis process:\n\n1. Chronologically analyze each message and section of the conversation. For each section thoroughly identify:\n   - The user's explicit requests and intents (verbatim if crucial)\n   - Your approach to addressing the user's requests\n   - Key decisions, technical concepts and code patterns\n   - Specific implementation details:\n     - exact file paths (not just file names)\n     - complete code snippets (with line numbers if referencing existing files)\n     - function signatures and parameters\n     - actual file edits with before/after\n   - Errors that you ran into and how you fixed them\n   - Specific user feedback you received, especially corrections or changed directions\n2. Double-check for technical accuracy and completeness\n3. Verify all file paths, code snippets, and technical details are precise and not paraphrased\n\nYour summary should include the following sections (be thorough and specific in each):\n\n1. **Primary Request and Intent**: Capture ALL of the user's explicit requests and intents in detail. Include the exact wording of critical requirements, success criteria, and any constraints. This is what the conversation exists to accomplish.\n\n2. **Key Technical Concepts**: List ALL important technical concepts, technologies, frameworks, libraries, and patterns discussed or used. Include version numbers, specific features, and trade-offs discussed.\n\n3. **Files and Code Sections**: Enumerate EVERY file examined, modified, or created. For each file:\n   - Include the EXACT file path (not relative, full path)\n   - Summarize why this file was important or what changes were made\n   - Include complete code snippets (or at least the changed lines) with context\n   - If it's a modification, note what changed and why\n\n4. **Errors and Fixes**: List ALL errors or problems encountered, including:\n   - Exact error messages (verbatim if possible)\n   - What caused the error\n   - How it was fixed\n   - Any specific user feedback about the error or fix\n\n5. **Problem Solving**: Document the problems solved and any ongoing troubleshooting efforts. Include:\n   - Root causes identified\n   - Trade-offs considered\n   - Why certain solutions were chosen over others\n\n6. **All User Messages**: List ALL explicit user messages that are not tool results. These are critical for understanding user feedback and intent changes. Keep the exact wording of important directives.\n\n7. **Pending Tasks**: Outline any tasks that the user has explicitly asked to work on but which have not yet been completed. Include any ambiguities or open questions.\n\n8. **Current Work**: Describe in precise detail what was being worked on IMMEDIATELY before this summary request. Include:\n   - What you were doing (exact actions)\n   - What file(s) you were modifying and how\n   - What you were about to do next\n   - Current state of the code/work\n   - Any unfinished steps in a larger task\n\n9. **Optional Next Step**: If there are clear next steps aligned with the user's most recent requests, list them. IMPORTANT: Do NOT start on tangential requests or old work without confirmation. Include direct quotes from the conversation showing exactly where you left off.\n\nHere's an example of how your output should be structured:\n\n<example>\n<conversation_history_summary>\n<analysis>\n[Your thought process, ensuring all points are covered thoroughly and accurately]\n</analysis>\n\n<summary>\n1. Primary Request and Intent:\n   [Detailed description]\n\n2. Key Technical Concepts:\n   - [Concept 1]\n   - [Concept 2]\n   - [...]\n\n3. Files and Code Sections:\n   - [File Name 1]\n      - [Summary of why this file is important]\n      - [Summary of the changes made to this file, if any]\n      - [Important Code Snippet]\n   - [File Name 2]\n      - [Important Code Snippet]\n   - [...]\n\n4. Errors and fixes:\n    - [Detailed description of error 1]:\n      - [How you fixed the error]\n      - [User feedback on the error if any]\n    - [...]\n\n5. Problem Solving:\n   [Description of solved problems and ongoing troubleshooting]\n\n6. All user messages: \n    - [Detailed non tool use user message]\n    - [...]\n\n7. Pending Tasks:\n   - [Task 1]\n   - [Task 2]\n   - [...]\n\n8. Current Work:\n   [Precise description of current work]\n\n9. Optional Next Step:\n   [Optional Next step to take]\n\n</summary>\n</conversation_history_summary>\n</example>\n\nPlease provide your summary based on the conversation so far, following this structure and ensuring precision and thoroughness in your response. \n\nThere may be additional summarization instructions provided in the included context. If so, remember to follow these instructions when creating the above summary. Examples of instructions include:\n<example>\n## Compact Instructions\nWhen summarizing the conversation focus on typescript code changes and also remember the mistakes you made and how you fixed them.\n</example>\n\n<example>\n# Summary instructions\nWhen you are using compact - please focus on test output and code changes. Include file reads verbatim.\n</example>\n\n\n⚠️ CRITICAL REQUIREMENTS:\n1. Do NOT use any tools. Do NOT attempt to read, write, or execute anything\n2. You MUST respond with the complete <conversation_history_summary> structure as shown in the example above\n3. Your output MUST follow this exact XML format - do not deviate\n4. Delete the <analysis> block before returning (it's only for your thinking process)\n5. Return only the <conversation_history_summary> with a single <summary> block inside\n\nREQUIRED OUTPUT FORMAT (final output after removing <analysis>):\n\n<conversation_history_summary>\n<summary>\n1. Primary Request and Intent:\n   [Detailed, specific description of user's requests and success criteria]\n\n2. Key Technical Concepts:\n   - [Concept 1 with version/specifics]\n   - [Concept 2]\n   - [...]\n\n3. Files and Code Sections:\n   - `/exact/file/path.ts` (line 45-78):\n      - [Why this file matters]\n      - [What changed and why]\n      - [Key code snippets]\n   - [...]\n\n4. Errors and Fixes:\n   - [Error 1: exact error message]\n     - Cause: [Root cause]\n     - Fix: [How it was fixed]\n     - User feedback: [Any specific feedback]\n   - [...]\n\n5. Problem Solving:\n   [Detailed explanation of problems solved and ongoing issues]\n\n6. All User Messages:\n   - [Critical user message #1]\n   - [Critical user message #2]\n   - [...]\n\n7. Pending Tasks:\n   - [Task 1 with any open questions]\n   - [Task 2]\n   - [...]\n\n8. Current Work:\n   [Precise description of what was being worked on immediately before summary request]\n\n9. Optional Next Step:\n   [Next steps if clearly defined, with supporting quotes]\n</summary>\n</conversation_history_summary>\n"
     },
     {
       "name": "command-security-review-prompt",
@@ -1480,6 +1480,6 @@
       "description": "Send a reply to a WeCom (企业微信) user. For text: pass text (markdown supported)."
     }
   ],
-  "commit": "277deb67cf55c3da0c467152a68351baeb810355",
-  "date": "2026-04-01T19:03:52.050Z"
+  "commit": "c3438a704868be5c7a92611d5866d4da1d8bf7e5",
+  "date": "2026-04-03T04:02:40.536Z"
 }

package/product.selfhosted.json

@@ -293,6 +293,6 @@
     "DeferToolLoading": true,
     "ScheduledTasks": true
   },
-  "commit": "277deb67cf55c3da0c467152a68351baeb810355",
-  "date": "2026-04-01T19:03:52.042Z"
+  "commit": "c3438a704868be5c7a92611d5866d4da1d8bf7e5",
+  "date": "2026-04-03T04:02:40.484Z"
 }