@tencent-ai/codebuddy-code 2.47.0-next.879e41c.20260205 → 2.48.0-next.1bb657b.20260206

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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@tencent-ai/codebuddy-code",
3
- "version": "2.47.0-next.879e41c.20260205",
3
+ "version": "2.48.0-next.1bb657b.20260206",
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",
@@ -121,6 +121,19 @@
121
121
  ],
122
122
  "tools": []
123
123
  },
124
+ {
125
+ "name": "promptHookEvaluator",
126
+ "instructions": "prompt-hook-evaluator-instructions",
127
+ "description": "Evaluates prompt hooks using LLM to determine if conditions are met",
128
+ "models": [
129
+ "lite"
130
+ ],
131
+ "tags": [
132
+ "cli",
133
+ "prompt-hook-evaluator"
134
+ ],
135
+ "tools": []
136
+ },
124
137
  {
125
138
  "name": "agentInstructions",
126
139
  "instructions": "agent-instructions",
@@ -354,6 +367,6 @@
354
367
  "DeferToolLoading": true,
355
368
  "ImageGen": true
356
369
  },
357
- "commit": "879e41c308634f91108731937a71139c350ff4c3",
358
- "date": "2026-02-05T10:10:53.545Z"
370
+ "commit": "1bb657b9fd1ecb609b7efebf803675ec70bcdda6",
371
+ "date": "2026-02-06T10:10:55.846Z"
359
372
  }
@@ -124,6 +124,19 @@
124
124
  ],
125
125
  "tools": []
126
126
  },
127
+ {
128
+ "name": "promptHookEvaluator",
129
+ "instructions": "prompt-hook-evaluator-instructions",
130
+ "description": "Evaluates prompt hooks using LLM to determine if conditions are met",
131
+ "models": [
132
+ "lite"
133
+ ],
134
+ "tags": [
135
+ "cli",
136
+ "prompt-hook-evaluator"
137
+ ],
138
+ "tools": []
139
+ },
127
140
  {
128
141
  "name": "agentInstructions",
129
142
  "instructions": "agent-instructions",
@@ -375,6 +388,6 @@
375
388
  "DeferToolLoading": true,
376
389
  "ImageGen": true
377
390
  },
378
- "commit": "879e41c308634f91108731937a71139c350ff4c3",
379
- "date": "2026-02-05T10:10:50.895Z"
391
+ "commit": "1bb657b9fd1ecb609b7efebf803675ec70bcdda6",
392
+ "date": "2026-02-06T10:10:53.043Z"
380
393
  }
package/product.ioa.json CHANGED
@@ -149,6 +149,19 @@
149
149
  ],
150
150
  "tools": []
151
151
  },
152
+ {
153
+ "name": "promptHookEvaluator",
154
+ "instructions": "prompt-hook-evaluator-instructions",
155
+ "description": "Evaluates prompt hooks using LLM to determine if conditions are met",
156
+ "models": [
157
+ "lite"
158
+ ],
159
+ "tags": [
160
+ "cli",
161
+ "prompt-hook-evaluator"
162
+ ],
163
+ "tools": []
164
+ },
152
165
  {
153
166
  "name": "agentInstructions",
154
167
  "instructions": "agent-instructions",
@@ -550,6 +563,6 @@
550
563
  "ImageGen": true,
551
564
  "ImageEdit": true
552
565
  },
553
- "commit": "879e41c308634f91108731937a71139c350ff4c3",
554
- "date": "2026-02-05T10:10:52.204Z"
566
+ "commit": "1bb657b9fd1ecb609b7efebf803675ec70bcdda6",
567
+ "date": "2026-02-06T10:10:54.459Z"
555
568
  }
package/product.json CHANGED
@@ -368,6 +368,10 @@
368
368
  "name": "summary-generator-instructions",
369
369
  "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"
370
370
  },
371
+ {
372
+ "name": "prompt-hook-evaluator-instructions",
373
+ "template": "You are evaluating a hook in CodeBuddy Code.\n\nCRITICAL: You MUST return ONLY valid JSON with no other text, no markdown formatting, no code blocks.\n\nYour response must be a single JSON object matching one of the following schemas:\n1. If the condition is met, return: {\"ok\": true}\n2. If the condition is not met, return: {\"ok\": false, \"reason\": \"Reason for why it is not met\"}\n\nReturn the JSON object directly with no preamble or explanation.\n"
374
+ },
371
375
  {
372
376
  "name": "agent-instructions",
373
377
  "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"
@@ -736,6 +740,19 @@
736
740
  ],
737
741
  "tools": []
738
742
  },
743
+ {
744
+ "name": "promptHookEvaluator",
745
+ "instructions": "prompt-hook-evaluator-instructions",
746
+ "description": "Evaluates prompt hooks using LLM to determine if conditions are met",
747
+ "models": [
748
+ "lite"
749
+ ],
750
+ "tags": [
751
+ "cli",
752
+ "prompt-hook-evaluator"
753
+ ],
754
+ "tools": []
755
+ },
739
756
  {
740
757
  "name": "agentInstructions",
741
758
  "instructions": "agent-instructions",
@@ -1109,6 +1126,6 @@
1109
1126
  "description": "tool-imageedit-description"
1110
1127
  }
1111
1128
  ],
1112
- "commit": "879e41c308634f91108731937a71139c350ff4c3",
1113
- "date": "2026-02-05T10:10:49.597Z"
1129
+ "commit": "1bb657b9fd1ecb609b7efebf803675ec70bcdda6",
1130
+ "date": "2026-02-06T10:10:51.658Z"
1114
1131
  }
@@ -115,6 +115,19 @@
115
115
  ],
116
116
  "tools": []
117
117
  },
118
+ {
119
+ "name": "promptHookEvaluator",
120
+ "instructions": "prompt-hook-evaluator-instructions",
121
+ "description": "Evaluates prompt hooks using LLM to determine if conditions are met",
122
+ "models": [
123
+ "lite"
124
+ ],
125
+ "tags": [
126
+ "cli",
127
+ "prompt-hook-evaluator"
128
+ ],
129
+ "tools": []
130
+ },
118
131
  {
119
132
  "name": "agentInstructions",
120
133
  "instructions": "agent-instructions",
@@ -225,6 +238,6 @@
225
238
  "CustomModelsJSON": true,
226
239
  "DeferToolLoading": true
227
240
  },
228
- "commit": "879e41c308634f91108731937a71139c350ff4c3",
229
- "date": "2026-02-05T10:10:54.865Z"
241
+ "commit": "1bb657b9fd1ecb609b7efebf803675ec70bcdda6",
242
+ "date": "2026-02-06T10:10:57.232Z"
230
243
  }