@tencent-ai/codebuddy-code 2.42.2 → 2.42.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +10 -0
- package/dist/codebuddy.js +8 -8
- package/lib/node/index.js +1 -0
- package/package.json +1 -1
- package/product.cloudhosted.json +12 -2
- package/product.internal.json +12 -2
- package/product.ioa.json +15 -2
- package/product.json +19 -2
- package/product.selfhosted.json +12 -2
package/lib/node/index.js
CHANGED
|
@@ -53,6 +53,7 @@ export * from './output-style';
|
|
|
53
53
|
export * from './undo-redo';
|
|
54
54
|
export * from './prompt-suggestion';
|
|
55
55
|
export * from './structured-output';
|
|
56
|
+
export * from './summary';
|
|
56
57
|
export * from './cli/cli-view';
|
|
57
58
|
export * from './cli/composite-view';
|
|
58
59
|
//# sourceMappingURL=index.js.map
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@tencent-ai/codebuddy-code",
|
|
3
|
-
"version": "2.42.
|
|
3
|
+
"version": "2.42.3",
|
|
4
4
|
"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.",
|
|
5
5
|
"main": "lib/node/index.js",
|
|
6
6
|
"typings": "lib/node/index.d.ts",
|
package/product.cloudhosted.json
CHANGED
|
@@ -108,6 +108,16 @@
|
|
|
108
108
|
],
|
|
109
109
|
"tools": []
|
|
110
110
|
},
|
|
111
|
+
{
|
|
112
|
+
"name": "summaryGenerator",
|
|
113
|
+
"instructions": "summary-generator-instructions",
|
|
114
|
+
"description": "Generate session summaries from conversation content.",
|
|
115
|
+
"tags": [
|
|
116
|
+
"cli",
|
|
117
|
+
"summary-generator"
|
|
118
|
+
],
|
|
119
|
+
"tools": []
|
|
120
|
+
},
|
|
111
121
|
{
|
|
112
122
|
"name": "agentInstructions",
|
|
113
123
|
"instructions": "agent-instructions",
|
|
@@ -332,6 +342,6 @@
|
|
|
332
342
|
"CustomModelsJSON": true,
|
|
333
343
|
"ImageGen": true
|
|
334
344
|
},
|
|
335
|
-
"commit": "
|
|
336
|
-
"date": "2026-01-
|
|
345
|
+
"commit": "4261ad4fa958757640802ed6d690cd8925f69076",
|
|
346
|
+
"date": "2026-01-31T14:51:42.878Z"
|
|
337
347
|
}
|
package/product.internal.json
CHANGED
|
@@ -111,6 +111,16 @@
|
|
|
111
111
|
],
|
|
112
112
|
"tools": []
|
|
113
113
|
},
|
|
114
|
+
{
|
|
115
|
+
"name": "summaryGenerator",
|
|
116
|
+
"instructions": "summary-generator-instructions",
|
|
117
|
+
"description": "Generate session summaries from conversation content.",
|
|
118
|
+
"tags": [
|
|
119
|
+
"cli",
|
|
120
|
+
"summary-generator"
|
|
121
|
+
],
|
|
122
|
+
"tools": []
|
|
123
|
+
},
|
|
114
124
|
{
|
|
115
125
|
"name": "agentInstructions",
|
|
116
126
|
"instructions": "agent-instructions",
|
|
@@ -353,6 +363,6 @@
|
|
|
353
363
|
"CustomModelsJSON": true,
|
|
354
364
|
"ImageGen": true
|
|
355
365
|
},
|
|
356
|
-
"commit": "
|
|
357
|
-
"date": "2026-01-
|
|
366
|
+
"commit": "4261ad4fa958757640802ed6d690cd8925f69076",
|
|
367
|
+
"date": "2026-01-31T14:51:40.099Z"
|
|
358
368
|
}
|
package/product.ioa.json
CHANGED
|
@@ -134,6 +134,19 @@
|
|
|
134
134
|
],
|
|
135
135
|
"tools": []
|
|
136
136
|
},
|
|
137
|
+
{
|
|
138
|
+
"name": "summaryGenerator",
|
|
139
|
+
"instructions": "summary-generator-instructions",
|
|
140
|
+
"description": "Generate session summaries from conversation content.",
|
|
141
|
+
"models": [
|
|
142
|
+
"lite"
|
|
143
|
+
],
|
|
144
|
+
"tags": [
|
|
145
|
+
"cli",
|
|
146
|
+
"summary-generator"
|
|
147
|
+
],
|
|
148
|
+
"tools": []
|
|
149
|
+
},
|
|
137
150
|
{
|
|
138
151
|
"name": "agentInstructions",
|
|
139
152
|
"instructions": "agent-instructions",
|
|
@@ -518,6 +531,6 @@
|
|
|
518
531
|
"CustomModelsJSON": true,
|
|
519
532
|
"ImageGen": true
|
|
520
533
|
},
|
|
521
|
-
"commit": "
|
|
522
|
-
"date": "2026-01-
|
|
534
|
+
"commit": "4261ad4fa958757640802ed6d690cd8925f69076",
|
|
535
|
+
"date": "2026-01-31T14:51:41.534Z"
|
|
523
536
|
}
|
package/product.json
CHANGED
|
@@ -346,6 +346,10 @@
|
|
|
346
346
|
"name": "terminal-title-generator-instructions",
|
|
347
347
|
"template": "Analyze if this message indicates a new conversation topic. If it does, extract a 2-3 word title that captures the new topic.\n\nFormat your response as a JSON object with two fields:\n- 'isNewTopic' (boolean)\n- 'title' (string, or null if isNewTopic is false)\n\nONLY generate the JSON object, no other text (eg. no markdown).\n"
|
|
348
348
|
},
|
|
349
|
+
{
|
|
350
|
+
"name": "summary-generator-instructions",
|
|
351
|
+
"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"
|
|
352
|
+
},
|
|
349
353
|
{
|
|
350
354
|
"name": "agent-instructions",
|
|
351
355
|
"template": "You are CodeBuddy Code.\n\nYou 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"
|
|
@@ -669,6 +673,19 @@
|
|
|
669
673
|
],
|
|
670
674
|
"tools": []
|
|
671
675
|
},
|
|
676
|
+
{
|
|
677
|
+
"name": "summaryGenerator",
|
|
678
|
+
"instructions": "summary-generator-instructions",
|
|
679
|
+
"description": "Generate session summaries from conversation content.",
|
|
680
|
+
"models": [
|
|
681
|
+
"lite"
|
|
682
|
+
],
|
|
683
|
+
"tags": [
|
|
684
|
+
"cli",
|
|
685
|
+
"summary-generator"
|
|
686
|
+
],
|
|
687
|
+
"tools": []
|
|
688
|
+
},
|
|
672
689
|
{
|
|
673
690
|
"name": "agentInstructions",
|
|
674
691
|
"instructions": "agent-instructions",
|
|
@@ -1008,6 +1025,6 @@
|
|
|
1008
1025
|
"description": "tool-imagegen-description"
|
|
1009
1026
|
}
|
|
1010
1027
|
],
|
|
1011
|
-
"commit": "
|
|
1012
|
-
"date": "2026-01-
|
|
1028
|
+
"commit": "4261ad4fa958757640802ed6d690cd8925f69076",
|
|
1029
|
+
"date": "2026-01-31T14:51:38.673Z"
|
|
1013
1030
|
}
|
package/product.selfhosted.json
CHANGED
|
@@ -104,6 +104,16 @@
|
|
|
104
104
|
],
|
|
105
105
|
"tools": []
|
|
106
106
|
},
|
|
107
|
+
{
|
|
108
|
+
"name": "summaryGenerator",
|
|
109
|
+
"instructions": "summary-generator-instructions",
|
|
110
|
+
"description": "Generate session summaries from conversation content.",
|
|
111
|
+
"tags": [
|
|
112
|
+
"cli",
|
|
113
|
+
"summary-generator"
|
|
114
|
+
],
|
|
115
|
+
"tools": []
|
|
116
|
+
},
|
|
107
117
|
{
|
|
108
118
|
"name": "agentInstructions",
|
|
109
119
|
"instructions": "agent-instructions",
|
|
@@ -205,6 +215,6 @@
|
|
|
205
215
|
"BillingNotice": false,
|
|
206
216
|
"CustomModelsJSON": true
|
|
207
217
|
},
|
|
208
|
-
"commit": "
|
|
209
|
-
"date": "2026-01-
|
|
218
|
+
"commit": "4261ad4fa958757640802ed6d690cd8925f69076",
|
|
219
|
+
"date": "2026-01-31T14:51:44.168Z"
|
|
210
220
|
}
|