2fb1c9dcd8
* feat: 第一版大重构 * fix: 修复类型问题 * chore: 更新版本到 1.3.2 * Add brave as alternative WebSearchTool * fix: 修正顺序 * fix: 修复对穷鬼模式的 auto dream 和 session memory 越过 * feat: 穷鬼模式去除 session-summary * feat: 创建 builtin-tools 包，搬运所有工具实现 将 src/tools/ 下的全部 60 个工具目录迁移至 packages/builtin-tools/src/tools/， 内部导入路径已更新为 src/ alias 模式。 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * refactor: 更新 src/ 中所有工具引用至 builtin-tools 包，删除 src/tools/ - src/tools.ts 及 178 个 src/ 文件的 import 路径从 ./tools/ 改为 builtin-tools/tools/ - 删除 src/tools/ 整个目录（已迁移至 packages/builtin-tools/） Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * chore: 添加 builtin-tools 路径别名至 tsconfig，更新 bun.lock - tsconfig.json 新增 builtin-tools/* 和 builtin-tools 路径映射 - 新增 packages/builtin-tools/src 至 include Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * refactor: 为 builtin-tools、mcp-client、agent-tools 添加 @claude-code-best 作用域前缀 所有包名及 import 路径统一添加 @claude-code-best/ 前缀： - builtin-tools → @claude-code-best/builtin-tools - mcp-client → @claude-code-best/mcp-client - agent-tools → @claude-code-best/agent-tools Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: 修复 node 环境没有 bun 的问题 --------- Co-authored-by: Eric-Guo <eric.guocz@gmail.com> Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
45 lines
2.8 KiB
TypeScript
45 lines
2.8 KiB
TypeScript
import { EXIT_PLAN_MODE_TOOL_NAME } from '../ExitPlanModeTool/constants.js'
|
|
|
|
export const ASK_USER_QUESTION_TOOL_NAME = 'AskUserQuestion'
|
|
|
|
export const ASK_USER_QUESTION_TOOL_CHIP_WIDTH = 12
|
|
|
|
export const DESCRIPTION =
|
|
'Asks the user multiple choice questions to gather information, clarify ambiguity, understand preferences, make decisions or offer them choices.'
|
|
|
|
export const PREVIEW_FEATURE_PROMPT = {
|
|
markdown: `
|
|
Preview feature:
|
|
Use the optional \`preview\` field on options when presenting concrete artifacts that users need to visually compare:
|
|
- ASCII mockups of UI layouts or components
|
|
- Code snippets showing different implementations
|
|
- Diagram variations
|
|
- Configuration examples
|
|
|
|
Preview content is rendered as markdown in a monospace box. Multi-line text with newlines is supported. When any option has a preview, the UI switches to a side-by-side layout with a vertical option list on the left and preview on the right. Do not use previews for simple preference questions where labels and descriptions suffice. Note: previews are only supported for single-select questions (not multiSelect).
|
|
`,
|
|
html: `
|
|
Preview feature:
|
|
Use the optional \`preview\` field on options when presenting concrete artifacts that users need to visually compare:
|
|
- HTML mockups of UI layouts or components
|
|
- Formatted code snippets showing different implementations
|
|
- Visual comparisons or diagrams
|
|
|
|
Preview content must be a self-contained HTML fragment (no <html>/<body> wrapper, no <script> or <style> tags — use inline style attributes instead). Do not use previews for simple preference questions where labels and descriptions suffice. Note: previews are only supported for single-select questions (not multiSelect).
|
|
`,
|
|
} as const
|
|
|
|
export const ASK_USER_QUESTION_TOOL_PROMPT = `Use this tool when you need to ask the user questions during execution. This allows you to:
|
|
1. Gather user preferences or requirements
|
|
2. Clarify ambiguous instructions
|
|
3. Get decisions on implementation choices as you work
|
|
4. Offer choices to the user about what direction to take.
|
|
|
|
Usage notes:
|
|
- Users will always be able to select "Other" to provide custom text input
|
|
- Use multiSelect: true to allow multiple answers to be selected for a question
|
|
- If you recommend a specific option, make that the first option in the list and add "(Recommended)" at the end of the label
|
|
|
|
Plan mode note: In plan mode, use this tool to clarify requirements or choose between approaches BEFORE finalizing your plan. Do NOT use this tool to ask "Is my plan ready?" or "Should I proceed?" - use ${EXIT_PLAN_MODE_TOOL_NAME} for plan approval. IMPORTANT: Do not reference "the plan" in your questions (e.g., "Do you have feedback about the plan?", "Does the plan look good?") because the user cannot see the plan in the UI until you call ${EXIT_PLAN_MODE_TOOL_NAME}. If you need plan approval, use ${EXIT_PLAN_MODE_TOOL_NAME} instead.
|
|
`
|