@tencent-ai/codebuddy-code 0.0.1-beta.6 → 0.0.1-beta.8

package/lib/node/index.js

@@ -19,4 +19,5 @@ export * from './memory';
 export * from './trace';
 export * from './settings';
 export * from './update';
+export * from './client';
 //# sourceMappingURL=index.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tencent-ai/codebuddy-code",
-  "version": "0.0.1-beta.6",
+  "version": "0.0.1-beta.8",
   "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.json

@@ -38,7 +38,9 @@
     }
   ],
   "commitMessage": {},
-  "config": {},
+  "config": {
+    "disabled": true
+  },
   "links": {
     "craftShellHelpDocument": "https://cloud.tencent.com/document/product/1749/117896",
     "craftFeedback": "https://cloud.tencent.com/document/product/1749/104249",
@@ -78,16 +80,6 @@
       "supportsToolCall": true,
       "vendor": "e"
     },
-    {
-      "id": "o4-mini",
-      "maxAllowedSize": 80000,
-      "maxInputTokens": 200000,
-      "maxOutputTokens": 32000,
-      "name": "GPT-4o-mini",
-      "supportsImages": true,
-      "supportsToolCall": true,
-      "vendor": "e"
-    },
     {
       "id": "gemini-2.5-flash",
       "maxAllowedSize": 80000,
@@ -106,6 +98,16 @@
       "supportsImages": true,
       "supportsToolCall": true
     },
+    {
+      "id": "o4-mini",
+      "maxAllowedSize": 80000,
+      "maxInputTokens": 200000,
+      "maxOutputTokens": 32000,
+      "name": "GPT-4o-mini",
+      "supportsImages": true,
+      "supportsToolCall": true,
+      "vendor": "e"
+    },
     {
       "id": "gpt-5",
       "maxAllowedSize": 80000,
@@ -145,6 +147,14 @@
     {
       "name": "init-prompt",
       "template": "Please analyze this codebase and create a CODEBUDDY.md file, which will be given to future instances of CodeBuddy Code to operate in this repository.\n            \nWhat to add:\n1. Commands that will be commonly used, such as how to build, lint, and run tests. Include the necessary commands to develop in this codebase, such as how to run a single test.\n2. High-level code architecture and structure so that future instances can be productive more quickly. Focus on the \"big picture\" architecture that requires reading multiple files to understand\n\nUsage notes:\n- If there's already a CODEBUDDY.md, suggest improvements to it.\n- When you make the initial CODEBUDDY.md, do not repeat yourself and do not include obvious instructions like \"Provide helpful error messages to users\", \"Write unit tests for all new utilities\", \"Never include sensitive information (API keys, tokens) in code or commits\" \n- Avoid listing every component or file structure that can be easily discovered\n- Don't include generic development practices\n- If there are Claude Code rules (in ./CLAUDE.md) or Cursor rules (in .cursor/rules/ or .cursorrules) or Copilot rules (in .github/copilot-instructions.md), make sure to include the important parts.\n- If there is a README.md, make sure to include the important parts. \n- Do not make up information such as \"Common Development Tasks\", \"Tips for Development\", \"Support and Documentation\" unless this is expressly included in other files that you read.\n- Be sure to prefix the file with the following text:\n"
+    },
+    {
+      "name": "compact-agent-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 file names, full code snippets, function signatures, file edits, etc\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. Problem Solving: Document problems solved and any ongoing troubleshooting efforts.\n5. Pending Tasks: Outline any pending tasks that you have explicitly been asked to work on.\n6. 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.\n7. 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 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 without confirming with the user first.\n8. 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<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. Problem Solving:\n   [Description of solved problems and ongoing troubleshooting]\n\n5. Pending Tasks:\n   - [Task 1]\n   - [Task 2]\n   - [...]\n\n6. Current Work:\n   [Precise description of current work]\n\n7. Optional Next Step:\n   [Optional Next step to take]\n\n</summary>\n</example>\n"
+    },
+    {
+      "name": "compact-prompt",
+      "template": "Please provide your summary based on the conversation so far, following this structure and ensuring precision and thoroughness in your response."
     }
   ],
   "variables": [
@@ -187,15 +197,12 @@
       "models": [
         "claude-3.7",
         "claude-4.0",
-        "gpt-5",
-        "gpt-5-mini",
-        "gpt-5-nano",
-        "o4-mini",
         "gemini-2.5-flash",
         "gemini-2.5-pro"
       ],
       "commands": [
-        "init"
+        "init",
+        "compact"
       ],
       "tools": [
         "ReadFile",
@@ -214,6 +221,21 @@
         "cli",
         "default"
       ]
+    },
+    {
+      "name": "compact",
+      "instructions": "compact-agent-prompt",
+      "description": "compact agent",
+      "models": [
+        "o4-mini"
+      ],
+      "tools": [
+        "CompactSummary"
+      ],
+      "tags": [
+        "cli",
+        "compact"
+      ]
     }
   ],
   "commands": [
@@ -221,6 +243,14 @@
       "name": "init",
       "description": "init is analyzing your codebase…",
       "prompt": "init-prompt"
+    },
+    {
+      "name": "compact",
+      "description": "Clear conversation history but keep a summary in context. Optional: /compact [instructions for summarization]",
+      "prompt": "compact-prompt",
+      "tags": [
+        "compact-agent"
+      ]
     }
   ],
   "productFeatures": {
@@ -265,6 +295,6 @@
     }
   },
   "deploymentType": "SaaS",
-  "commit": "fa979485afca112c73f9d82606b6c4295c3ad348",
-  "date": "2025-08-08T10:44:09.609Z"
+  "commit": "170c4845e62be58e3de933012bc2aa0896438a4b",
+  "date": "2025-08-10T15:47:50.232Z"
 }