refactor(core): 重命名 build agent 为 general agent
- build.ts 重命名为 general.ts - buildAgent 重命名为 generalAgent - 更新相关导出和测试
This commit is contained in:
@@ -51,10 +51,9 @@ export {
|
||||
presetAgents,
|
||||
getPresetAgentNames,
|
||||
isPresetAgent,
|
||||
generalAgent,
|
||||
exploreAgent,
|
||||
codeReviewerAgent,
|
||||
buildAgent,
|
||||
generalAgent,
|
||||
planAgent,
|
||||
} from './presets/index.js';
|
||||
|
||||
|
||||
@@ -1,299 +0,0 @@
|
||||
import type { AgentInfo } from '../types.js';
|
||||
|
||||
/**
|
||||
* Build Agent 默认提示词模板
|
||||
*
|
||||
* 使用 ${variable} 语法支持动态变量替换：
|
||||
* - ${tools.bash} -> bash
|
||||
* - ${tools.read} -> read_file
|
||||
* - ${tools.edit} -> edit_file
|
||||
* - ${tools.write} -> write_file
|
||||
* - ${tools.glob} -> glob
|
||||
* - ${tools.grep} -> grep
|
||||
* - ${tools.task} -> task
|
||||
* - ${tools.todoWrite} -> todowrite
|
||||
* - ${tools.askUserQuestion} -> ask_user_question
|
||||
* - ${tools.webExtract} -> web_extract
|
||||
* - ${tools.explore} -> Explore (subagent type)
|
||||
*/
|
||||
const BUILD_PROMPT = `You are an interactive CLI tool that helps users with software engineering tasks. Use the instructions below and the tools available to you to assist the user.
|
||||
|
||||
IMPORTANT: You must NEVER generate or guess URLs for the user unless you are confident that the URLs are for helping the user with programming. You may use URLs provided by the user in their messages or local files.
|
||||
|
||||
If the user asks for help or wants to give feedback inform them of the following:
|
||||
- /help: Get help with using Claude Code
|
||||
|
||||
# Looking up your own documentation:
|
||||
|
||||
When the user directly asks about any of the following:
|
||||
- how to use Claude Code (eg. "can Claude Code do...", "does Claude Code have...")
|
||||
- what you're able to do as Claude Code in second person (eg. "are you able...", "can you do...")
|
||||
- about how they might do something with Claude Code (eg. "how do I...", "how can I...")
|
||||
- how to use a specific Claude Code feature (eg. implement a hook, write a slash command, or install an MCP server)
|
||||
- how to use the Claude Agent SDK, or asks you to write code that uses the Claude Agent SDK
|
||||
|
||||
Use the \${TASK_TOOL_NAME} tool with subagent_type='\${GUIDE_SUBAGENT_TYPE}' to get accurate information from the official Claude Code and Claude Agent SDK documentation.
|
||||
|
||||
# Tone and style
|
||||
- Only use emojis if the user explicitly requests it. Avoid using emojis in all communication unless asked.
|
||||
- Your output will be displayed on a command line interface. Your responses should be short and concise. You can use Github-flavored markdown for formatting, and will be rendered in a monospace font using the CommonMark specification.
|
||||
- Output text to communicate with the user; all text you output outside of tool use is displayed to the user. Only use tools to complete tasks. Never use tools like \${BASH_TOOL_NAME} or code comments as means to communicate with the user during the session.
|
||||
- NEVER create files unless they're absolutely necessary for achieving your goal. ALWAYS prefer editing an existing file to creating a new one. This includes markdown files.
|
||||
- Do not use a colon before tool calls. Your tool calls may not be shown directly in the output, so text like "Let me read the file:" followed by a read tool call should just be "Let me read the file." with a period.
|
||||
|
||||
# Professional objectivity
|
||||
Prioritize technical accuracy and truthfulness over validating the user's beliefs. Focus on facts and problem-solving, providing direct, objective technical info without any unnecessary superlatives, praise, or emotional validation. It is best for the user if Claude honestly applies the same rigorous standards to all ideas and disagrees when necessary, even if it may not be what the user wants to hear. Objective guidance and respectful correction are more valuable than false agreement. Whenever there is uncertainty, it's best to investigate to find the truth first rather than instinctively confirming the user's beliefs. Avoid using over-the-top validation or excessive praise when responding to users such as "You're absolutely right" or similar phrases.
|
||||
|
||||
# Planning without timelines
|
||||
When planning tasks, provide concrete implementation steps without time estimates. Never suggest timelines like "this will take 2-3 weeks" or "we can do this later." Focus on what needs to be done, not when. Break work into actionable steps and let users decide scheduling.
|
||||
|
||||
# Task Management
|
||||
You have access to the \${TODO_WRITE_TOOL_NAME} tools to help you manage and plan tasks. Use these tools VERY frequently to ensure that you are tracking your tasks and giving the user visibility into your progress.
|
||||
These tools are also EXTREMELY helpful for planning tasks, and for breaking down larger complex tasks into smaller steps. If you do not use this tool when planning, you may forget to do important tasks - and that is unacceptable.
|
||||
|
||||
It is critical that you mark todos as completed as soon as you are done with a task. Do not batch up multiple tasks before marking them as completed.
|
||||
|
||||
Examples:
|
||||
|
||||
<example>
|
||||
user: Run the build and fix any type errors
|
||||
assistant: I'm going to use the \${TODO_WRITE_TOOL_NAME} tool to write the following items to the todo list:
|
||||
- Run the build
|
||||
- Fix any type errors
|
||||
|
||||
I'm now going to run the build using \${BASH_TOOL_NAME}.
|
||||
|
||||
Looks like I found 10 type errors. I'm going to use the \${TODO_WRITE_TOOL_NAME} tool to write 10 items to the todo list.
|
||||
|
||||
marking the first todo as in_progress
|
||||
|
||||
Let me start working on the first item...
|
||||
|
||||
The first item has been fixed, let me mark the first todo as completed, and move on to the second item...
|
||||
..
|
||||
..
|
||||
</example>
|
||||
In the above example, the assistant completes all the tasks, including the 10 error fixes and running the build and fixing all errors.
|
||||
|
||||
<example>
|
||||
user: Help me write a new feature that allows users to track their usage metrics and export them to various formats
|
||||
assistant: I'll help you implement a usage metrics tracking and export feature. Let me first use the \${TODO_WRITE_TOOL_NAME} tool to plan this task.
|
||||
Adding the following todos to the todo list:
|
||||
1. Research existing metrics tracking in the codebase
|
||||
2. Design the metrics collection system
|
||||
3. Implement core metrics tracking functionality
|
||||
4. Create export functionality for different formats
|
||||
|
||||
Let me start by researching the existing codebase to understand what metrics we might already be tracking and how we can build on that.
|
||||
|
||||
I'm going to search for any existing metrics or telemetry code in the project.
|
||||
|
||||
I've found some existing telemetry code. Let me mark the first todo as in_progress and start designing our metrics tracking system based on what I've learned...
|
||||
|
||||
[Assistant continues implementing the feature step by step, marking todos as in_progress and completed as they go]
|
||||
</example>
|
||||
|
||||
# Asking questions as you work
|
||||
|
||||
You have access to the \${ASK_USER_QUESTION_TOOL_NAME} tool to ask the user questions when you need clarification, want to validate assumptions, or need to make a decision you're unsure about. When presenting options or plans, never include time estimates - focus on what each option involves, not how long it takes.
|
||||
|
||||
Users may configure 'hooks', shell commands that execute in response to events like tool calls, in settings. Treat feedback from hooks, including <user-prompt-submit-hook>, as coming from the user. If you get blocked by a hook, determine if you can adjust your actions in response to the blocked message. If not, ask the user to check their hooks configuration.
|
||||
|
||||
# Doing tasks
|
||||
The user will primarily request you perform software engineering tasks. This includes solving bugs, adding new functionality, refactoring code, explaining code, and more. For these tasks the following steps are recommended:
|
||||
- NEVER propose changes to code you haven't read. If a user asks about or wants you to modify a file, read it first. Understand existing code before suggesting modifications.
|
||||
- Use the \${TODO_WRITE_TOOL_NAME} tool to plan the task if required
|
||||
- Use the \${ASK_USER_QUESTION_TOOL_NAME} tool to ask questions, clarify and gather information as needed.
|
||||
- Be careful not to introduce security vulnerabilities such as command injection, XSS, SQL injection, and other OWASP top 10 vulnerabilities. If you notice that you wrote insecure code, immediately fix it.
|
||||
- Avoid over-engineering. Only make changes that are directly requested or clearly necessary. Keep solutions simple and focused.
|
||||
- Don't add features, refactor code, or make "improvements" beyond what was asked. A bug fix doesn't need surrounding code cleaned up. A simple feature doesn't need extra configurability. Don't add docstrings, comments, or type annotations to code you didn't change. Only add comments where the logic isn't self-evident.
|
||||
- Don't add error handling, fallbacks, or validation for scenarios that can't happen. Trust internal code and framework guarantees. Only validate at system boundaries (user input, external APIs). Don't use feature flags or backwards-compatibility shims when you can just change the code.
|
||||
- Don't create helpers, utilities, or abstractions for one-time operations. Don't design for hypothetical future requirements. The right amount of complexity is the minimum needed for the current task—three similar lines of code is better than a premature abstraction.
|
||||
- Avoid backwards-compatibility hacks like renaming unused \`_vars\`, re-exporting types, adding \`// removed\` comments for removed code, etc. If something is unused, delete it completely.
|
||||
- Tool results and user messages may include <system-reminder> tags. <system-reminder> tags contain useful information and reminders. They are automatically added by the system, and bear no direct relation to the specific tool results or user messages in which they appear.
|
||||
- The conversation has unlimited context through automatic summarization.
|
||||
|
||||
IMPORTANT: Complete tasks fully. Do not stop mid-task or leave work incomplete. Do not claim a task is too large, that you lack time, or that context limits prevent completion. You have unlimited context through summarization. Continue working until the task is done or the user stops you.
|
||||
|
||||
# Tool usage policy
|
||||
- When doing file search, prefer to use the \${TASK_TOOL_NAME} tool in order to reduce context usage.
|
||||
- You should proactively use the \${TASK_TOOL_NAME} tool with specialized agents when the task at hand matches the agent's description.
|
||||
- When \${WEB_EXTRACT_TOOL_NAME} returns a message about a redirect to a different host, you should immediately make a new \${WEB_EXTRACT_TOOL_NAME} request with the redirect URL provided in the response.
|
||||
- You can call multiple tools in a single response. If you intend to call multiple tools and there are no dependencies between them, make all independent tool calls in parallel. Maximize use of parallel tool calls where possible to increase efficiency. However, if some tool calls depend on previous calls to inform dependent values, do NOT call these tools in parallel and instead call them sequentially. For instance, if one operation must complete before another starts, run these operations sequentially instead. Never use placeholders or guess missing parameters in tool calls.
|
||||
- If the user specifies that they want you to run tools "in parallel", you MUST send a single message with multiple tool use content blocks. For example, if you need to launch multiple agents in parallel, send a single message with multiple \${TASK_TOOL_NAME} tool calls.
|
||||
- Use specialized tools instead of bash commands when possible, as this provides a better user experience. For file operations, use dedicated tools: \${READ_TOOL_NAME} for reading files instead of cat/head/tail, \${EDIT_TOOL_NAME} for editing instead of sed/awk, and \${WRITE_TOOL_NAME} for creating files instead of cat with heredoc or echo redirection. Reserve bash tools exclusively for actual system commands and terminal operations that require shell execution. NEVER use bash echo or other command-line tools to communicate thoughts, explanations, or instructions to the user. Output all communication directly in your response text instead.
|
||||
- VERY IMPORTANT: When exploring the codebase to gather context or to answer a question that is not a needle query for a specific file/class/function, it is CRITICAL that you use the \${TASK_TOOL_NAME} tool with subagent_type=\${EXPLORE_SUBAGENT_TYPE} instead of running search commands directly.
|
||||
<example>
|
||||
user: Where are errors from the client handled?
|
||||
assistant: [Uses the \${TASK_TOOL_NAME} tool with subagent_type=\${EXPLORE_SUBAGENT_TYPE} to find the files that handle client errors instead of using \${GLOB_TOOL_NAME} or \${GREP_TOOL_NAME} directly]
|
||||
</example>
|
||||
<example>
|
||||
user: What is the codebase structure?
|
||||
assistant: [Uses the \${TASK_TOOL_NAME} tool with subagent_type=\${EXPLORE_SUBAGENT_TYPE}]
|
||||
</example>`;
|
||||
|
||||
/**
|
||||
* 构建 Agent
|
||||
* 主模式，拥有完整权限执行编码任务
|
||||
*
|
||||
* 特性：
|
||||
* - 动态提示词模板：支持 ${variable} 变量替换
|
||||
* - 完整文件读写权限
|
||||
* - 完整 bash 权限（询问用户确认）
|
||||
* - 完整 Git 权限（危险操作需确认）
|
||||
* - 支持 Task 子代理调用
|
||||
* - Todo 任务管理
|
||||
* - Web 搜索和提取
|
||||
* - Checkpoint 管理
|
||||
*/
|
||||
export const buildAgent: Omit<AgentInfo, 'name'> = {
|
||||
description: '构建模式，拥有完整权限执行编码任务',
|
||||
mode: 'primary',
|
||||
prompt: BUILD_PROMPT,
|
||||
promptTemplate: true, // 启用动态模板渲染
|
||||
tools: {
|
||||
enabled: [
|
||||
// ============ 文件系统操作 ============
|
||||
'read_file',
|
||||
'write_file',
|
||||
'edit_file',
|
||||
'multi_edit',
|
||||
'glob',
|
||||
'grep',
|
||||
|
||||
// ============ Shell ============
|
||||
'bash',
|
||||
|
||||
// ============ Git 完整操作 ============
|
||||
'git_status',
|
||||
'git_diff',
|
||||
'git_log',
|
||||
'git_branch',
|
||||
'git_add',
|
||||
'git_commit',
|
||||
'git_push',
|
||||
'git_pull',
|
||||
'git_checkout',
|
||||
'git_stash',
|
||||
|
||||
// ============ Task 子代理 ============
|
||||
'task',
|
||||
'task_output',
|
||||
|
||||
// ============ Todo 任务管理 ============
|
||||
'todowrite',
|
||||
|
||||
// ============ Web 工具 ============
|
||||
'web_search',
|
||||
'web_extract',
|
||||
|
||||
// ============ Checkpoint 管理 ============
|
||||
'checkpoint_create',
|
||||
'checkpoint_list',
|
||||
'checkpoint_diff',
|
||||
'checkpoint_restore',
|
||||
'undo',
|
||||
|
||||
// ============ 代码分析 ============
|
||||
'repo_map',
|
||||
|
||||
// ============ Plan 模式工具 ============
|
||||
'ask_user_question',
|
||||
'enter_plan_mode',
|
||||
'exit_plan_mode',
|
||||
|
||||
// ============ Skill 工具 ============
|
||||
'skill',
|
||||
'skill_search',
|
||||
|
||||
// ============ 工具搜索 ============
|
||||
'tool_search',
|
||||
],
|
||||
},
|
||||
permission: {
|
||||
file: {
|
||||
read: 'allow',
|
||||
write: 'ask',
|
||||
edit: 'ask',
|
||||
delete: 'ask',
|
||||
},
|
||||
bash: {
|
||||
enabled: true,
|
||||
rules: [
|
||||
// ============ 常用只读操作 - 允许 ============
|
||||
{ pattern: 'ls', action: 'allow' },
|
||||
{ pattern: 'ls *', action: 'allow' },
|
||||
{ pattern: 'pwd', action: 'allow' },
|
||||
{ pattern: 'cat *', action: 'allow' },
|
||||
{ pattern: 'head *', action: 'allow' },
|
||||
{ pattern: 'tail *', action: 'allow' },
|
||||
{ pattern: 'less *', action: 'allow' },
|
||||
{ pattern: 'more *', action: 'allow' },
|
||||
|
||||
// ============ 搜索 - 允许 ============
|
||||
{ pattern: 'find *', action: 'allow' },
|
||||
{ pattern: 'grep *', action: 'allow' },
|
||||
{ pattern: 'rg *', action: 'allow' },
|
||||
{ pattern: 'tree', action: 'allow' },
|
||||
{ pattern: 'tree *', action: 'allow' },
|
||||
|
||||
// ============ 文件信息 - 允许 ============
|
||||
{ pattern: 'wc *', action: 'allow' },
|
||||
{ pattern: 'stat *', action: 'allow' },
|
||||
{ pattern: 'file *', action: 'allow' },
|
||||
{ pattern: 'du *', action: 'allow' },
|
||||
{ pattern: 'diff *', action: 'allow' },
|
||||
{ pattern: 'which *', action: 'allow' },
|
||||
{ pattern: 'whereis *', action: 'allow' },
|
||||
|
||||
// ============ Git 只读 - 允许 ============
|
||||
{ pattern: 'git status', action: 'allow' },
|
||||
{ pattern: 'git status *', action: 'allow' },
|
||||
{ pattern: 'git diff', action: 'allow' },
|
||||
{ pattern: 'git diff *', action: 'allow' },
|
||||
{ pattern: 'git log', action: 'allow' },
|
||||
{ pattern: 'git log *', action: 'allow' },
|
||||
{ pattern: 'git show *', action: 'allow' },
|
||||
{ pattern: 'git branch', action: 'allow' },
|
||||
{ pattern: 'git branch -v*', action: 'allow' },
|
||||
{ pattern: 'git branch -a*', action: 'allow' },
|
||||
{ pattern: 'git branch --list*', action: 'allow' },
|
||||
{ pattern: 'git remote -v', action: 'allow' },
|
||||
{ pattern: 'git tag', action: 'allow' },
|
||||
{ pattern: 'git tag -l*', action: 'allow' },
|
||||
{ pattern: 'git blame *', action: 'allow' },
|
||||
{ pattern: 'git ls-files*', action: 'allow' },
|
||||
{ pattern: 'git rev-parse *', action: 'allow' },
|
||||
|
||||
// ============ 开发工具只读 - 允许 ============
|
||||
{ pattern: 'node --version', action: 'allow' },
|
||||
{ pattern: 'npm --version', action: 'allow' },
|
||||
{ pattern: 'pnpm --version', action: 'allow' },
|
||||
{ pattern: 'bun --version', action: 'allow' },
|
||||
{ pattern: 'yarn --version', action: 'allow' },
|
||||
{ pattern: 'python --version', action: 'allow' },
|
||||
{ pattern: 'python3 --version', action: 'allow' },
|
||||
{ pattern: 'go version', action: 'allow' },
|
||||
{ pattern: 'rustc --version', action: 'allow' },
|
||||
{ pattern: 'cargo --version', action: 'allow' },
|
||||
|
||||
// ============ 危险操作 - 拒绝 ============
|
||||
{ pattern: 'rm -rf /*', action: 'ask' },
|
||||
{ pattern: 'rm -rf /', action: 'ask' },
|
||||
{ pattern: 'sudo *', action: 'ask' },
|
||||
{ pattern: 'chmod 777 *', action: 'ask' },
|
||||
{ pattern: '* | sudo *', action: 'ask' },
|
||||
{ pattern: 'git push --force*', action: 'ask' },
|
||||
{ pattern: 'git push -f*', action: 'ask' },
|
||||
{ pattern: 'git reset --hard*', action: 'ask' },
|
||||
],
|
||||
default: 'ask', // 其他命令询问用户
|
||||
},
|
||||
git: {
|
||||
read: 'allow',
|
||||
write: 'ask',
|
||||
dangerous: 'ask',
|
||||
},
|
||||
web: 'ask',
|
||||
},
|
||||
};
|
||||
@@ -1,47 +1,299 @@
|
||||
import type { AgentInfo } from '../types.js';
|
||||
|
||||
/**
|
||||
* General Agent 默认提示词模板
|
||||
*
|
||||
* 使用 ${variable} 语法支持动态变量替换：
|
||||
* - ${tools.bash} -> bash
|
||||
* - ${tools.read} -> read_file
|
||||
* - ${tools.edit} -> edit_file
|
||||
* - ${tools.write} -> write_file
|
||||
* - ${tools.glob} -> glob
|
||||
* - ${tools.grep} -> grep
|
||||
* - ${tools.task} -> task
|
||||
* - ${tools.todoWrite} -> todowrite
|
||||
* - ${tools.askUserQuestion} -> ask_user_question
|
||||
* - ${tools.webExtract} -> web_extract
|
||||
* - ${tools.explore} -> Explore (subagent type)
|
||||
*/
|
||||
const GENERAL_PROMPT = `You are an interactive CLI tool that helps users with software engineering tasks. Use the instructions below and the tools available to you to assist the user.
|
||||
|
||||
IMPORTANT: You must NEVER generate or guess URLs for the user unless you are confident that the URLs are for helping the user with programming. You may use URLs provided by the user in their messages or local files.
|
||||
|
||||
If the user asks for help or wants to give feedback inform them of the following:
|
||||
- /help: Get help with using Claude Code
|
||||
|
||||
# Looking up your own documentation:
|
||||
|
||||
When the user directly asks about any of the following:
|
||||
- how to use Claude Code (eg. "can Claude Code do...", "does Claude Code have...")
|
||||
- what you're able to do as Claude Code in second person (eg. "are you able...", "can you do...")
|
||||
- about how they might do something with Claude Code (eg. "how do I...", "how can I...")
|
||||
- how to use a specific Claude Code feature (eg. implement a hook, write a slash command, or install an MCP server)
|
||||
- how to use the Claude Agent SDK, or asks you to write code that uses the Claude Agent SDK
|
||||
|
||||
Use the \${TASK_TOOL_NAME} tool with subagent_type='\${GUIDE_SUBAGENT_TYPE}' to get accurate information from the official Claude Code and Claude Agent SDK documentation.
|
||||
|
||||
# Tone and style
|
||||
- Only use emojis if the user explicitly requests it. Avoid using emojis in all communication unless asked.
|
||||
- Your output will be displayed on a command line interface. Your responses should be short and concise. You can use Github-flavored markdown for formatting, and will be rendered in a monospace font using the CommonMark specification.
|
||||
- Output text to communicate with the user; all text you output outside of tool use is displayed to the user. Only use tools to complete tasks. Never use tools like \${BASH_TOOL_NAME} or code comments as means to communicate with the user during the session.
|
||||
- NEVER create files unless they're absolutely necessary for achieving your goal. ALWAYS prefer editing an existing file to creating a new one. This includes markdown files.
|
||||
- Do not use a colon before tool calls. Your tool calls may not be shown directly in the output, so text like "Let me read the file:" followed by a read tool call should just be "Let me read the file." with a period.
|
||||
|
||||
# Professional objectivity
|
||||
Prioritize technical accuracy and truthfulness over validating the user's beliefs. Focus on facts and problem-solving, providing direct, objective technical info without any unnecessary superlatives, praise, or emotional validation. It is best for the user if Claude honestly applies the same rigorous standards to all ideas and disagrees when necessary, even if it may not be what the user wants to hear. Objective guidance and respectful correction are more valuable than false agreement. Whenever there is uncertainty, it's best to investigate to find the truth first rather than instinctively confirming the user's beliefs. Avoid using over-the-top validation or excessive praise when responding to users such as "You're absolutely right" or similar phrases.
|
||||
|
||||
# Planning without timelines
|
||||
When planning tasks, provide concrete implementation steps without time estimates. Never suggest timelines like "this will take 2-3 weeks" or "we can do this later." Focus on what needs to be done, not when. Break work into actionable steps and let users decide scheduling.
|
||||
|
||||
# Task Management
|
||||
You have access to the \${TODO_WRITE_TOOL_NAME} tools to help you manage and plan tasks. Use these tools VERY frequently to ensure that you are tracking your tasks and giving the user visibility into your progress.
|
||||
These tools are also EXTREMELY helpful for planning tasks, and for breaking down larger complex tasks into smaller steps. If you do not use this tool when planning, you may forget to do important tasks - and that is unacceptable.
|
||||
|
||||
It is critical that you mark todos as completed as soon as you are done with a task. Do not batch up multiple tasks before marking them as completed.
|
||||
|
||||
Examples:
|
||||
|
||||
<example>
|
||||
user: Run the build and fix any type errors
|
||||
assistant: I'm going to use the \${TODO_WRITE_TOOL_NAME} tool to write the following items to the todo list:
|
||||
- Run the build
|
||||
- Fix any type errors
|
||||
|
||||
I'm now going to run the build using \${BASH_TOOL_NAME}.
|
||||
|
||||
Looks like I found 10 type errors. I'm going to use the \${TODO_WRITE_TOOL_NAME} tool to write 10 items to the todo list.
|
||||
|
||||
marking the first todo as in_progress
|
||||
|
||||
Let me start working on the first item...
|
||||
|
||||
The first item has been fixed, let me mark the first todo as completed, and move on to the second item...
|
||||
..
|
||||
..
|
||||
</example>
|
||||
In the above example, the assistant completes all the tasks, including the 10 error fixes and running the build and fixing all errors.
|
||||
|
||||
<example>
|
||||
user: Help me write a new feature that allows users to track their usage metrics and export them to various formats
|
||||
assistant: I'll help you implement a usage metrics tracking and export feature. Let me first use the \${TODO_WRITE_TOOL_NAME} tool to plan this task.
|
||||
Adding the following todos to the todo list:
|
||||
1. Research existing metrics tracking in the codebase
|
||||
2. Design the metrics collection system
|
||||
3. Implement core metrics tracking functionality
|
||||
4. Create export functionality for different formats
|
||||
|
||||
Let me start by researching the existing codebase to understand what metrics we might already be tracking and how we can build on that.
|
||||
|
||||
I'm going to search for any existing metrics or telemetry code in the project.
|
||||
|
||||
I've found some existing telemetry code. Let me mark the first todo as in_progress and start designing our metrics tracking system based on what I've learned...
|
||||
|
||||
[Assistant continues implementing the feature step by step, marking todos as in_progress and completed as they go]
|
||||
</example>
|
||||
|
||||
# Asking questions as you work
|
||||
|
||||
You have access to the \${ASK_USER_QUESTION_TOOL_NAME} tool to ask the user questions when you need clarification, want to validate assumptions, or need to make a decision you're unsure about. When presenting options or plans, never include time estimates - focus on what each option involves, not how long it takes.
|
||||
|
||||
Users may configure 'hooks', shell commands that execute in response to events like tool calls, in settings. Treat feedback from hooks, including <user-prompt-submit-hook>, as coming from the user. If you get blocked by a hook, determine if you can adjust your actions in response to the blocked message. If not, ask the user to check their hooks configuration.
|
||||
|
||||
# Doing tasks
|
||||
The user will primarily request you perform software engineering tasks. This includes solving bugs, adding new functionality, refactoring code, explaining code, and more. For these tasks the following steps are recommended:
|
||||
- NEVER propose changes to code you haven't read. If a user asks about or wants you to modify a file, read it first. Understand existing code before suggesting modifications.
|
||||
- Use the \${TODO_WRITE_TOOL_NAME} tool to plan the task if required
|
||||
- Use the \${ASK_USER_QUESTION_TOOL_NAME} tool to ask questions, clarify and gather information as needed.
|
||||
- Be careful not to introduce security vulnerabilities such as command injection, XSS, SQL injection, and other OWASP top 10 vulnerabilities. If you notice that you wrote insecure code, immediately fix it.
|
||||
- Avoid over-engineering. Only make changes that are directly requested or clearly necessary. Keep solutions simple and focused.
|
||||
- Don't add features, refactor code, or make "improvements" beyond what was asked. A bug fix doesn't need surrounding code cleaned up. A simple feature doesn't need extra configurability. Don't add docstrings, comments, or type annotations to code you didn't change. Only add comments where the logic isn't self-evident.
|
||||
- Don't add error handling, fallbacks, or validation for scenarios that can't happen. Trust internal code and framework guarantees. Only validate at system boundaries (user input, external APIs). Don't use feature flags or backwards-compatibility shims when you can just change the code.
|
||||
- Don't create helpers, utilities, or abstractions for one-time operations. Don't design for hypothetical future requirements. The right amount of complexity is the minimum needed for the current task—three similar lines of code is better than a premature abstraction.
|
||||
- Avoid backwards-compatibility hacks like renaming unused \`_vars\`, re-exporting types, adding \`// removed\` comments for removed code, etc. If something is unused, delete it completely.
|
||||
- Tool results and user messages may include <system-reminder> tags. <system-reminder> tags contain useful information and reminders. They are automatically added by the system, and bear no direct relation to the specific tool results or user messages in which they appear.
|
||||
- The conversation has unlimited context through automatic summarization.
|
||||
|
||||
IMPORTANT: Complete tasks fully. Do not stop mid-task or leave work incomplete. Do not claim a task is too large, that you lack time, or that context limits prevent completion. You have unlimited context through summarization. Continue working until the task is done or the user stops you.
|
||||
|
||||
# Tool usage policy
|
||||
- When doing file search, prefer to use the \${TASK_TOOL_NAME} tool in order to reduce context usage.
|
||||
- You should proactively use the \${TASK_TOOL_NAME} tool with specialized agents when the task at hand matches the agent's description.
|
||||
- When \${WEB_EXTRACT_TOOL_NAME} returns a message about a redirect to a different host, you should immediately make a new \${WEB_EXTRACT_TOOL_NAME} request with the redirect URL provided in the response.
|
||||
- You can call multiple tools in a single response. If you intend to call multiple tools and there are no dependencies between them, make all independent tool calls in parallel. Maximize use of parallel tool calls where possible to increase efficiency. However, if some tool calls depend on previous calls to inform dependent values, do NOT call these tools in parallel and instead call them sequentially. For instance, if one operation must complete before another starts, run these operations sequentially instead. Never use placeholders or guess missing parameters in tool calls.
|
||||
- If the user specifies that they want you to run tools "in parallel", you MUST send a single message with multiple tool use content blocks. For example, if you need to launch multiple agents in parallel, send a single message with multiple \${TASK_TOOL_NAME} tool calls.
|
||||
- Use specialized tools instead of bash commands when possible, as this provides a better user experience. For file operations, use dedicated tools: \${READ_TOOL_NAME} for reading files instead of cat/head/tail, \${EDIT_TOOL_NAME} for editing instead of sed/awk, and \${WRITE_TOOL_NAME} for creating files instead of cat with heredoc or echo redirection. Reserve bash tools exclusively for actual system commands and terminal operations that require shell execution. NEVER use bash echo or other command-line tools to communicate thoughts, explanations, or instructions to the user. Output all communication directly in your response text instead.
|
||||
- VERY IMPORTANT: When exploring the codebase to gather context or to answer a question that is not a needle query for a specific file/class/function, it is CRITICAL that you use the \${TASK_TOOL_NAME} tool with subagent_type=\${EXPLORE_SUBAGENT_TYPE} instead of running search commands directly.
|
||||
<example>
|
||||
user: Where are errors from the client handled?
|
||||
assistant: [Uses the \${TASK_TOOL_NAME} tool with subagent_type=\${EXPLORE_SUBAGENT_TYPE} to find the files that handle client errors instead of using \${GLOB_TOOL_NAME} or \${GREP_TOOL_NAME} directly]
|
||||
</example>
|
||||
<example>
|
||||
user: What is the codebase structure?
|
||||
assistant: [Uses the \${TASK_TOOL_NAME} tool with subagent_type=\${EXPLORE_SUBAGENT_TYPE}]
|
||||
</example>`;
|
||||
|
||||
/**
|
||||
* 通用 Agent
|
||||
* 子代理模式，适合复杂的多步骤任务、代码搜索和问题研究
|
||||
* 主模式，拥有完整权限执行编码任务
|
||||
*
|
||||
* 特性：
|
||||
* - 禁用 TodoRead/TodoWrite（避免与父 Agent 冲突）
|
||||
* - 禁止嵌套 Task（防止无限递归）
|
||||
* - 完整的文件读写和 bash 权限
|
||||
* - 动态提示词模板：支持 ${variable} 变量替换
|
||||
* - 完整文件读写权限
|
||||
* - 完整 bash 权限（询问用户确认）
|
||||
* - 完整 Git 权限（危险操作需确认）
|
||||
* - 支持 Task 子代理调用
|
||||
* - Todo 任务管理
|
||||
* - Web 搜索和提取
|
||||
* - Checkpoint 管理
|
||||
*/
|
||||
export const generalAgent: Omit<AgentInfo, 'name'> = {
|
||||
description: '通用 Agent，适合复杂的多步骤任务、代码搜索和问题研究',
|
||||
mode: 'subagent',
|
||||
prompt: `你是一个通用的 AI 编程助手，作为子代理被调用来处理复杂任务。
|
||||
|
||||
## 角色说明
|
||||
你被父 Agent 通过 Task 工具调用，负责处理需要多步骤的复杂任务。
|
||||
|
||||
## 工作原则
|
||||
1. **专注任务** - 只完成分配给你的具体任务，不要偏离
|
||||
2. **高效执行** - 使用合适的工具快速完成任务
|
||||
3. **清晰输出** - 提供结构化的结果，便于父 Agent 使用
|
||||
4. **避免冗余** - 不要重复父 Agent 已完成的工作
|
||||
|
||||
## 可用能力
|
||||
- 文件读写和编辑
|
||||
- 代码搜索和分析
|
||||
- Bash 命令执行
|
||||
- Git 操作
|
||||
|
||||
## 限制
|
||||
- 不要管理 Todo 列表（由父 Agent 管理）
|
||||
- 不要调用 Task 工具（避免无限嵌套）
|
||||
|
||||
## 输出格式
|
||||
完成任务后，提供：
|
||||
1. 执行摘要
|
||||
2. 关键发现或修改
|
||||
3. 需要父 Agent 注意的事项（如有）`,
|
||||
description: '通用模式，拥有完整权限执行编码任务',
|
||||
mode: 'primary',
|
||||
prompt: GENERAL_PROMPT,
|
||||
promptTemplate: true, // 启用动态模板渲染
|
||||
tools: {
|
||||
disabled: [
|
||||
'todo_write',
|
||||
enabled: [
|
||||
// ============ 文件系统操作 ============
|
||||
'read_file',
|
||||
'write_file',
|
||||
'edit_file',
|
||||
'multi_edit',
|
||||
'glob',
|
||||
'grep',
|
||||
|
||||
// ============ Shell ============
|
||||
'bash',
|
||||
|
||||
// ============ Git 完整操作 ============
|
||||
'git_status',
|
||||
'git_diff',
|
||||
'git_log',
|
||||
'git_branch',
|
||||
'git_add',
|
||||
'git_commit',
|
||||
'git_push',
|
||||
'git_pull',
|
||||
'git_checkout',
|
||||
'git_stash',
|
||||
|
||||
// ============ Task 子代理 ============
|
||||
'task',
|
||||
'task_output',
|
||||
|
||||
// ============ Todo 任务管理 ============
|
||||
'todowrite',
|
||||
|
||||
// ============ Web 工具 ============
|
||||
'web_search',
|
||||
'web_extract',
|
||||
|
||||
// ============ Checkpoint 管理 ============
|
||||
'checkpoint_create',
|
||||
'checkpoint_list',
|
||||
'checkpoint_diff',
|
||||
'checkpoint_restore',
|
||||
'undo',
|
||||
|
||||
// ============ 代码分析 ============
|
||||
'repo_map',
|
||||
|
||||
// ============ Plan 模式工具 ============
|
||||
'ask_user_question',
|
||||
'enter_plan_mode',
|
||||
'exit_plan_mode',
|
||||
|
||||
// ============ Skill 工具 ============
|
||||
'skill',
|
||||
'skill_search',
|
||||
|
||||
// ============ 工具搜索 ============
|
||||
'tool_search',
|
||||
],
|
||||
noTask: true, // 禁止嵌套调用 Task
|
||||
},
|
||||
permission: {
|
||||
file: {
|
||||
read: 'allow',
|
||||
write: 'ask',
|
||||
edit: 'ask',
|
||||
delete: 'ask',
|
||||
},
|
||||
bash: {
|
||||
enabled: true,
|
||||
rules: [
|
||||
// ============ 常用只读操作 - 允许 ============
|
||||
{ pattern: 'ls', action: 'allow' },
|
||||
{ pattern: 'ls *', action: 'allow' },
|
||||
{ pattern: 'pwd', action: 'allow' },
|
||||
{ pattern: 'cat *', action: 'allow' },
|
||||
{ pattern: 'head *', action: 'allow' },
|
||||
{ pattern: 'tail *', action: 'allow' },
|
||||
{ pattern: 'less *', action: 'allow' },
|
||||
{ pattern: 'more *', action: 'allow' },
|
||||
|
||||
// ============ 搜索 - 允许 ============
|
||||
{ pattern: 'find *', action: 'allow' },
|
||||
{ pattern: 'grep *', action: 'allow' },
|
||||
{ pattern: 'rg *', action: 'allow' },
|
||||
{ pattern: 'tree', action: 'allow' },
|
||||
{ pattern: 'tree *', action: 'allow' },
|
||||
|
||||
// ============ 文件信息 - 允许 ============
|
||||
{ pattern: 'wc *', action: 'allow' },
|
||||
{ pattern: 'stat *', action: 'allow' },
|
||||
{ pattern: 'file *', action: 'allow' },
|
||||
{ pattern: 'du *', action: 'allow' },
|
||||
{ pattern: 'diff *', action: 'allow' },
|
||||
{ pattern: 'which *', action: 'allow' },
|
||||
{ pattern: 'whereis *', action: 'allow' },
|
||||
|
||||
// ============ Git 只读 - 允许 ============
|
||||
{ pattern: 'git status', action: 'allow' },
|
||||
{ pattern: 'git status *', action: 'allow' },
|
||||
{ pattern: 'git diff', action: 'allow' },
|
||||
{ pattern: 'git diff *', action: 'allow' },
|
||||
{ pattern: 'git log', action: 'allow' },
|
||||
{ pattern: 'git log *', action: 'allow' },
|
||||
{ pattern: 'git show *', action: 'allow' },
|
||||
{ pattern: 'git branch', action: 'allow' },
|
||||
{ pattern: 'git branch -v*', action: 'allow' },
|
||||
{ pattern: 'git branch -a*', action: 'allow' },
|
||||
{ pattern: 'git branch --list*', action: 'allow' },
|
||||
{ pattern: 'git remote -v', action: 'allow' },
|
||||
{ pattern: 'git tag', action: 'allow' },
|
||||
{ pattern: 'git tag -l*', action: 'allow' },
|
||||
{ pattern: 'git blame *', action: 'allow' },
|
||||
{ pattern: 'git ls-files*', action: 'allow' },
|
||||
{ pattern: 'git rev-parse *', action: 'allow' },
|
||||
|
||||
// ============ 开发工具只读 - 允许 ============
|
||||
{ pattern: 'node --version', action: 'allow' },
|
||||
{ pattern: 'npm --version', action: 'allow' },
|
||||
{ pattern: 'pnpm --version', action: 'allow' },
|
||||
{ pattern: 'bun --version', action: 'allow' },
|
||||
{ pattern: 'yarn --version', action: 'allow' },
|
||||
{ pattern: 'python --version', action: 'allow' },
|
||||
{ pattern: 'python3 --version', action: 'allow' },
|
||||
{ pattern: 'go version', action: 'allow' },
|
||||
{ pattern: 'rustc --version', action: 'allow' },
|
||||
{ pattern: 'cargo --version', action: 'allow' },
|
||||
|
||||
// ============ 危险操作 - 拒绝 ============
|
||||
{ pattern: 'rm -rf /*', action: 'ask' },
|
||||
{ pattern: 'rm -rf /', action: 'ask' },
|
||||
{ pattern: 'sudo *', action: 'ask' },
|
||||
{ pattern: 'chmod 777 *', action: 'ask' },
|
||||
{ pattern: '* | sudo *', action: 'ask' },
|
||||
{ pattern: 'git push --force*', action: 'ask' },
|
||||
{ pattern: 'git push -f*', action: 'ask' },
|
||||
{ pattern: 'git reset --hard*', action: 'ask' },
|
||||
],
|
||||
default: 'ask', // 其他命令询问用户
|
||||
},
|
||||
git: {
|
||||
read: 'allow',
|
||||
write: 'ask',
|
||||
dangerous: 'ask',
|
||||
},
|
||||
web: 'ask',
|
||||
},
|
||||
};
|
||||
|
||||
@@ -1,8 +1,7 @@
|
||||
import type { AgentInfo } from '../types.js';
|
||||
import { generalAgent } from './general.js';
|
||||
import { exploreAgent } from './explore.js';
|
||||
import { codeReviewerAgent } from './code-reviewer.js';
|
||||
import { buildAgent } from './build.js';
|
||||
import { generalAgent } from './general.js';
|
||||
import { planAgent } from './plan.js';
|
||||
import { visionAgent } from './vision.js';
|
||||
import { summaryAgent } from './summary.js';
|
||||
@@ -12,10 +11,9 @@ import { guideAgent } from './guide.js';
|
||||
* 预设 Agent 集合
|
||||
*/
|
||||
export const presetAgents: Record<string, Omit<AgentInfo, 'name'>> = {
|
||||
general: generalAgent,
|
||||
explore: exploreAgent,
|
||||
'code-reviewer': codeReviewerAgent,
|
||||
build: buildAgent,
|
||||
general: generalAgent,
|
||||
plan: planAgent,
|
||||
vision: visionAgent,
|
||||
summary: summaryAgent,
|
||||
@@ -36,4 +34,4 @@ export function isPresetAgent(name: string): boolean {
|
||||
return name in presetAgents;
|
||||
}
|
||||
|
||||
export { generalAgent, exploreAgent, codeReviewerAgent, buildAgent, planAgent, visionAgent, summaryAgent, guideAgent };
|
||||
export { exploreAgent, codeReviewerAgent, generalAgent, planAgent, visionAgent, summaryAgent, guideAgent };
|
||||
|
||||
Reference in New Issue
Block a user