snow-ai 0.2.24 → 0.2.25

package/dist/api/chat.d.ts

@@ -57,14 +57,6 @@ export interface ChatCompletionChunk {
     }>;
 }
 export declare function resetOpenAIClient(): void;
-/**
- * Create chat completion with automatic function calling support
- */
-export declare function createChatCompletionWithTools(options: ChatCompletionOptions, maxToolRounds?: number, abortSignal?: AbortSignal, onRetry?: (error: Error, attempt: number, nextDelay: number) => void): Promise<{
-    content: string;
-    toolCalls: ToolCall[];
-}>;
-export declare function createChatCompletion(options: ChatCompletionOptions, abortSignal?: AbortSignal, onRetry?: (error: Error, attempt: number, nextDelay: number) => void): Promise<string>;
 export interface UsageInfo {
     prompt_tokens: number;
     completion_tokens: number;

package/dist/api/chat.js

@@ -1,8 +1,7 @@
 import OpenAI from 'openai';
 import { getOpenAiConfig, getCustomSystemPrompt, getCustomHeaders } from '../utils/apiConfig.js';
-import { executeMCPTool } from '../utils/mcpToolsManager.js';
 import { SYSTEM_PROMPT } from './systemPrompt.js';
-import { withRetry, withRetryGenerator } from '../utils/retryUtils.js';
+import { withRetryGenerator } from '../utils/retryUtils.js';
 /**
  * Convert our ChatMessage format to OpenAI's ChatCompletionMessageParam format
  * Automatically prepends system prompt if not present
@@ -112,148 +111,6 @@ function getOpenAIClient() {
 export function resetOpenAIClient() {
     openaiClient = null;
 }
-/**
- * Create chat completion with automatic function calling support
- */
-export async function createChatCompletionWithTools(options, maxToolRounds = 5, abortSignal, onRetry) {
-    const client = getOpenAIClient();
-    let messages = [...options.messages];
-    let allToolCalls = [];
-    let rounds = 0;
-    try {
-        while (rounds < maxToolRounds) {
-            const response = await withRetry(() => client.chat.completions.create({
-                model: options.model,
-                messages: convertToOpenAIMessages(messages),
-                stream: false,
-                temperature: options.temperature || 0.7,
-                max_tokens: options.max_tokens,
-                tools: options.tools,
-                tool_choice: options.tool_choice,
-            }), {
-                abortSignal,
-                onRetry
-            });
-            const message = response.choices[0]?.message;
-            if (!message) {
-                throw new Error('No response from AI');
-            }
-            // Add assistant message to conversation
-            messages.push({
-                role: 'assistant',
-                content: message.content || '',
-                tool_calls: message.tool_calls
-            });
-            // Check if AI wants to call tools
-            if (message.tool_calls && message.tool_calls.length > 0) {
-                allToolCalls.push(...message.tool_calls);
-                // Execute each tool call
-                for (const toolCall of message.tool_calls) {
-                    if (toolCall.type === 'function') {
-                        try {
-                            const args = JSON.parse(toolCall.function.arguments);
-                            const result = await executeMCPTool(toolCall.function.name, args);
-                            // Add tool result to conversation
-                            messages.push({
-                                role: 'tool',
-                                content: JSON.stringify(result),
-                                tool_call_id: toolCall.id
-                            });
-                        }
-                        catch (error) {
-                            // Add error result to conversation
-                            messages.push({
-                                role: 'tool',
-                                content: `Error: ${error instanceof Error ? error.message : 'Tool execution failed'}`,
-                                tool_call_id: toolCall.id
-                            });
-                        }
-                    }
-                }
-                rounds++;
-                continue;
-            }
-            // No tool calls, return the content
-            return {
-                content: message.content || '',
-                toolCalls: allToolCalls
-            };
-        }
-        throw new Error(`Maximum tool calling rounds (${maxToolRounds}) exceeded`);
-    }
-    catch (error) {
-        if (error instanceof Error) {
-            throw new Error(`Chat completion with tools failed: ${error.message}`);
-        }
-        throw new Error('Chat completion with tools failed: Unknown error');
-    }
-}
-export async function createChatCompletion(options, abortSignal, onRetry) {
-    const client = getOpenAIClient();
-    let messages = [...options.messages];
-    try {
-        while (true) {
-            const response = await withRetry(() => client.chat.completions.create({
-                model: options.model,
-                messages: convertToOpenAIMessages(messages),
-                stream: false,
-                temperature: options.temperature || 0.7,
-                max_tokens: options.max_tokens,
-                tools: options.tools,
-                tool_choice: options.tool_choice,
-            }), {
-                abortSignal,
-                onRetry
-            });
-            const message = response.choices[0]?.message;
-            if (!message) {
-                throw new Error('No response from AI');
-            }
-            // Add assistant message to conversation
-            messages.push({
-                role: 'assistant',
-                content: message.content || '',
-                tool_calls: message.tool_calls
-            });
-            // Check if AI wants to call tools
-            if (message.tool_calls && message.tool_calls.length > 0) {
-                // Execute each tool call
-                for (const toolCall of message.tool_calls) {
-                    if (toolCall.type === 'function') {
-                        try {
-                            const args = JSON.parse(toolCall.function.arguments);
-                            const result = await executeMCPTool(toolCall.function.name, args);
-                            // Add tool result to conversation
-                            messages.push({
-                                role: 'tool',
-                                content: JSON.stringify(result),
-                                tool_call_id: toolCall.id
-                            });
-                        }
-                        catch (error) {
-                            // Add error result to conversation
-                            messages.push({
-                                role: 'tool',
-                                content: `Error: ${error instanceof Error ? error.message : 'Tool execution failed'}`,
-                                tool_call_id: toolCall.id
-                            });
-                        }
-                    }
-                }
-                // Continue the conversation with tool results
-                continue;
-            }
-            // No tool calls, return the content
-            return message.content || '';
-        }
-    }
-    catch (error) {
-        if (error instanceof Error) {
-            throw new Error(`Chat completion failed: ${error.message}`);
-        }
-        throw new Error('Chat completion failed: Unknown error');
-    }
-}
 /**
  * Simple streaming chat completion - only handles OpenAI interaction
  * Tool execution should be handled by the caller

package/dist/api/responses.d.ts

@@ -38,18 +38,7 @@ export interface ResponseStreamChunk {
     usage?: UsageInfo;
 }
 export declare function resetOpenAIClient(): void;
-/**
- * 使用 Responses API 创建响应（非流式,带自动工具调用）
- */
-export declare function createResponse(options: ResponseOptions, abortSignal?: AbortSignal, onRetry?: (error: Error, attempt: number, nextDelay: number) => void): Promise<string>;
 /**
  * 使用 Responses API 创建流式响应（带自动工具调用）
  */
 export declare function createStreamingResponse(options: ResponseOptions, abortSignal?: AbortSignal, onRetry?: (error: Error, attempt: number, nextDelay: number) => void): AsyncGenerator<ResponseStreamChunk, void, unknown>;
-/**
- * 使用 Responses API 创建响应（限制工具调用轮数）
- */
-export declare function createResponseWithTools(options: ResponseOptions, maxToolRounds?: number, abortSignal?: AbortSignal, onRetry?: (error: Error, attempt: number, nextDelay: number) => void): Promise<{
-    content: string;
-    toolCalls: ToolCall[];
-}>;

package/dist/api/responses.js

@@ -1,8 +1,7 @@
 import OpenAI from 'openai';
 import { getOpenAiConfig, getCustomSystemPrompt, getCustomHeaders } from '../utils/apiConfig.js';
-import { executeMCPTool } from '../utils/mcpToolsManager.js';
 import { SYSTEM_PROMPT } from './systemPrompt.js';
-import { withRetry, withRetryGenerator } from '../utils/retryUtils.js';
+import { withRetryGenerator } from '../utils/retryUtils.js';
 /**
  * 确保 schema 符合 Responses API 的要求：
  * 1. additionalProperties: false
@@ -75,19 +74,6 @@ function getOpenAIClient() {
 export function resetOpenAIClient() {
     openaiClient = null;
 }
-/**
- * 转换消息格式为 Responses API 的 input 格式
- * Responses API 的 input 格式：
- * 1. 支持 user, assistant 角色消息，使用 type: "message" 包裹
- * 2. 工具调用在 assistant 中表示为 function_call 类型的 item
- * 3. 工具结果使用 function_call_output 类型
- *
- * 注意：Responses API 使用 instructions 字段代替 system 消息
- * 优化：使用 type: "message" 包裹以提高缓存命中率
- * Logic:
- * 1. If custom system prompt exists: use custom as instructions, prepend default as first user message
- * 2. If no custom system prompt: use default as instructions
- */
 function convertToResponseInput(messages) {
     const customSystemPrompt = getCustomSystemPrompt();
     const result = [];
@@ -191,92 +177,6 @@ function convertToResponseInput(messages) {
     }
     return { input: result, systemInstructions };
 }
-/**
- * 使用 Responses API 创建响应（非流式,带自动工具调用）
- */
-export async function createResponse(options, abortSignal, onRetry) {
-    const client = getOpenAIClient();
-    let messages = [...options.messages];
-    // 提取系统提示词和转换后的消息
-    const { input: convertedInput, systemInstructions } = convertToResponseInput(messages);
-    try {
-        // 使用 Responses API
-        while (true) {
-            const requestPayload = {
-                model: options.model,
-                instructions: systemInstructions,
-                input: convertedInput,
-                tools: convertToolsForResponses(options.tools),
-                tool_choice: options.tool_choice,
-                reasoning: options.reasoning || { summary: 'auto', effort: 'high' },
-                store: options.store ?? false,
-                include: options.include || ['reasoning.encrypted_content'],
-                prompt_cache_key: options.prompt_cache_key,
-            };
-            const response = await withRetry(() => client.responses.create(requestPayload), {
-                abortSignal,
-                onRetry
-            });
-            // 提取响应 - Responses API 返回 output 数组
-            const output = response.output;
-            if (!output || output.length === 0) {
-                throw new Error('No output from AI');
-            }
-            // 获取最后一条消息（通常是 assistant 的响应）
-            const lastMessage = output[output.length - 1];
-            // 添加 assistant 消息到对话
-            messages.push({
-                role: 'assistant',
-                content: lastMessage.content || '',
-                tool_calls: lastMessage.tool_calls
-            });
-            // 检查是否有工具调用
-            if (lastMessage.tool_calls && lastMessage.tool_calls.length > 0) {
-                // 执行每个工具调用
-                for (const toolCall of lastMessage.tool_calls) {
-                    if (toolCall.type === 'function') {
-                        try {
-                            const args = JSON.parse(toolCall.function.arguments);
-                            const result = await executeMCPTool(toolCall.function.name, args);
-                            // 添加工具结果到对话
-                            messages.push({
-                                role: 'tool',
-                                content: JSON.stringify(result),
-                                tool_call_id: toolCall.id
-                            });
-                        }
-                        catch (error) {
-                            // 添加错误结果到对话
-                            messages.push({
-                                role: 'tool',
-                                content: `Error: ${error instanceof Error ? error.message : 'Tool execution failed'}`,
-                                tool_call_id: toolCall.id
-                            });
-                        }
-                    }
-                }
-                // 继续对话获取工具结果后的响应
-                continue;
-            }
-            // 没有工具调用，返回内容
-            return lastMessage.content || '';
-        }
-    }
-    catch (error) {
-        if (error instanceof Error) {
-            // 检查是否是 API 网关不支持 Responses API
-            if (error.message.includes('Panic detected') ||
-                error.message.includes('nil pointer') ||
-                error.message.includes('404') ||
-                error.message.includes('not found')) {
-                throw new Error('Response creation failed: Your API endpoint does not support the Responses API. ' +
-                    'Please switch to "Chat Completions" method in API settings, or use an OpenAI-compatible endpoint that supports Responses API.');
-            }
-            throw new Error(`Response creation failed: ${error.message}`);
-        }
-        throw new Error('Response creation failed: Unknown error');
-    }
-}
 /**
  * 使用 Responses API 创建流式响应（带自动工具调用）
  */
@@ -461,91 +361,3 @@ export async function* createStreamingResponse(options, abortSignal, onRetry) {
         onRetry
     });
 }
-/**
- * 使用 Responses API 创建响应（限制工具调用轮数）
- */
-export async function createResponseWithTools(options, maxToolRounds = 5, abortSignal, onRetry) {
-    const client = getOpenAIClient();
-    let messages = [...options.messages];
-    let allToolCalls = [];
-    let rounds = 0;
-    // 提取系统提示词和转换后的消息
-    const { input: convertedInput, systemInstructions } = convertToResponseInput(messages);
-    try {
-        while (rounds < maxToolRounds) {
-            const requestPayload = {
-                model: options.model,
-                instructions: systemInstructions,
-                input: convertedInput,
-                tools: convertToolsForResponses(options.tools),
-                tool_choice: options.tool_choice,
-                reasoning: options.reasoning || { summary: 'auto', effort: 'high' },
-                store: options.store ?? false,
-                include: options.include || ['reasoning.encrypted_content'],
-                prompt_cache_key: options.prompt_cache_key,
-            };
-            const response = await withRetry(() => client.responses.create(requestPayload), {
-                abortSignal,
-                onRetry
-            });
-            const output = response.output;
-            if (!output || output.length === 0) {
-                throw new Error('No output from AI');
-            }
-            const lastMessage = output[output.length - 1];
-            // 添加 assistant 消息
-            messages.push({
-                role: 'assistant',
-                content: lastMessage.content || '',
-                tool_calls: lastMessage.tool_calls
-            });
-            // 检查工具调用
-            if (lastMessage.tool_calls && lastMessage.tool_calls.length > 0) {
-                allToolCalls.push(...lastMessage.tool_calls);
-                // 执行工具调用
-                for (const toolCall of lastMessage.tool_calls) {
-                    if (toolCall.type === 'function') {
-                        try {
-                            const args = JSON.parse(toolCall.function.arguments);
-                            const result = await executeMCPTool(toolCall.function.name, args);
-                            messages.push({
-                                role: 'tool',
-                                content: JSON.stringify(result),
-                                tool_call_id: toolCall.id
-                            });
-                        }
-                        catch (error) {
-                            messages.push({
-                                role: 'tool',
-                                content: `Error: ${error instanceof Error ? error.message : 'Tool execution failed'}`,
-                                tool_call_id: toolCall.id
-                            });
-                        }
-                    }
-                }
-                rounds++;
-                continue;
-            }
-            // 没有工具调用，返回结果
-            return {
-                content: lastMessage.content || '',
-                toolCalls: allToolCalls
-            };
-        }
-        throw new Error(`Maximum tool calling rounds (${maxToolRounds}) exceeded`);
-    }
-    catch (error) {
-        if (error instanceof Error) {
-            // 检查是否是 API 网关不支持 Responses API
-            if (error.message.includes('Panic detected') ||
-                error.message.includes('nil pointer') ||
-                error.message.includes('404') ||
-                error.message.includes('not found')) {
-                throw new Error('Response creation with tools failed: Your API endpoint does not support the Responses API. ' +
-                    'Please switch to "Chat Completions" method in API settings.');
-            }
-            throw new Error(`Response creation with tools failed: ${error.message}`);
-        }
-        throw new Error('Response creation with tools failed: Unknown error');
-    }
-}

package/dist/api/systemPrompt.d.ts

@@ -1,4 +1,4 @@
 /**
  * System prompt configuration for Snow AI CLI
  */
-export declare const SYSTEM_PROMPT = "You are Snow AI CLI, an intelligent command-line assistant designed to help users with their tasks efficiently and systematically.\n\n## \uD83C\uDFAF Core Principles\n\n1. **Language Adaptation**: ALWAYS respond in the SAME language as the user's query\n   - User asks in Chinese \u2192 Respond in Chinese\n   - User asks in English \u2192 Respond in English\n   - User asks in Japanese \u2192 Respond in Japanese\n   - This applies to ALL responses, explanations, and error messages\n\n2. **Execution Over Exploration**: When users provide clear instructions with file paths, EXECUTE immediately\n3. **Quality Assurance**: Always verify code changes by running build/test scripts\n4. **Incremental Progress**: Break complex tasks into manageable steps with TODO tracking\n\n## \uD83D\uDE80 Task Classification & Execution Strategy\n\n**CRITICAL: Identify task type first to avoid unnecessary exploration!**\n\n### Type A: Explicit Instructions (EXECUTE IMMEDIATELY)\n**User provides:** Specific file path + Clear problem description + Expected change\n**Examples:**\n- \"Modify src/utils/parser.ts line 45, change timeout from 1000 to 5000\"\n- \"In components/Header.tsx, add a new prop 'showLogo: boolean'\"\n- \"Fix the bug in api/auth.ts where the token validation fails\"\n\n**Your action:**\n1. \u2705 Read the specified file(s) ONLY\n2. \u2705 Make the required changes immediately\n3. \u2705 Verify with build/test\n4. \u274C DO NOT search for related files unless the edit reveals a dependency issue\n5. \u274C DO NOT read SNOW.md unless you need architectural context\n6. \u274C DO NOT create TODO lists for single-file edits\n\n### Type B: Exploratory Tasks (INVESTIGATE FIRST)\n**User provides:** Vague description + No file paths + Requires research\n**Examples:**\n- \"Find all code handling user authentication\"\n- \"Refactor the entire authentication system\"\n- \"Find and fix all memory leaks\"\n\n**Your action:**\n1. Use ACE code search to locate relevant code\n2. Create TODO list if multiple files involved\n3. Read SNOW.md if architectural understanding needed\n4. Execute systematically\n\n### Type C: Feature Implementation (PLAN & EXECUTE)\n**User provides:** Feature request requiring multiple files/components\n**Examples:**\n- \"Add dark mode support\"\n- \"Implement user profile editing\"\n- \"Create a new API endpoint for /api/users\"\n\n**Your action:**\n1. Create TODO list with specific tasks\n2. Check SNOW.md for architectural patterns\n3. Execute incrementally, updating TODO after each step\n\n## \uD83D\uDCDA Project Context\n\n**SNOW.md Documentation:**\n- ONLY read SNOW.md for Type B (Exploratory) and Type C (Feature) tasks\n- Skip SNOW.md for Type A (Explicit) tasks where user specifies exact files\n- SNOW.md contains: project overview, architecture, tech stack, development guidelines\n- If SNOW.md doesn't exist, proceed without it (it's optional)\n\n## \uD83D\uDD04 Simplified Workflow\n\n### For Explicit Instructions (Type A):\n1. Read the specified file(s)\n2. Execute the change immediately\n3. Verify with build/test\n4. Report completion\n\n### For Exploratory Tasks (Type B):\n1. Search/locate relevant code\n2. Read necessary context\n3. Execute changes\n4. Verify and report\n\n### For Feature Implementation (Type C):\n1. Create TODO list\n2. Check SNOW.md if needed\n3. Execute incrementally\n4. Update TODO after each step\n5. Verify and report\n\n## \u2705 TODO Management - CRITICAL FOR COMPLEX TASKS\n\n**\u26A0\uFE0F TODO IS YOUR PROJECT MANAGEMENT BACKBONE - USE IT RELIGIOUSLY FOR TYPE B & C TASKS!**\n\n### \uD83C\uDFAF Why TODO Management is Critical:\n1. **Visibility**: Users can track progress in real-time\n2. **Accountability**: Clear record of what's done and what's pending\n3. **Error Prevention**: Ensures no steps are skipped or forgotten\n4. **Communication**: Shows systematic approach and professionalism\n5. **Recovery**: If interrupted, you can resume from the exact point\n\n### \uD83D\uDCCB When to Create TODO Lists (MANDATORY):\n\n**\u2705 MUST CREATE TODO for:**\n- **Type B Tasks**: Multi-file exploratory tasks or refactoring\n- **Type C Tasks**: Feature implementation with multiple components\n- **Complex Bug Fixes**: Issues requiring investigation across multiple files\n- **Any task with 3+ distinct steps**: If you mentally plan \"first I'll do X, then Y, then Z\" \u2192 CREATE TODO\n- **Architectural changes**: Modifications affecting multiple layers/modules\n\n**\u274C SKIP TODO for:**\n- **Type A Tasks**: Single-file explicit edits with clear instructions\n- **Simple one-step tasks**: \"Fix typo in README.md\"\n- **Quick queries**: \"What does this function do?\"\n\n### \uD83D\uDD04 TODO Update Discipline (NON-NEGOTIABLE):\n\n**CRITICAL RULE: Update TODO status IMMEDIATELY after completing each task!**\n\n\u2705 **DO THIS (Correct Workflow):**\n```\n1. Create TODO with all tasks\n2. Complete Task 1 \u2192 IMMEDIATELY mark as \"completed\"\n3. Complete Task 2 \u2192 IMMEDIATELY mark as \"completed\"\n4. Complete Task 3 \u2192 IMMEDIATELY mark as \"completed\"\n5. Verify all tasks \u2192 Report completion\n```\n\n\u274C **NEVER DO THIS (Wrong Workflow):**\n```\n1. Create TODO with all tasks\n2. Complete Task 1, 2, 3 silently\n3. Update all statuses at the end \u2190 WRONG! User has no visibility!\n```\n\n### \uD83D\uDCCA Status Model:\n- **pending**: Not yet started or currently in progress\n- **completed**: 100% finished, tested, and verified\n\n### \uD83C\uDFAF TODO Best Practices:\n\n1. **Be Specific**: \"Modify handleSubmit in ChatInput.tsx to add validation\" NOT \"Fix input\"\n2. **Logical Order**: Arrange tasks by dependency (e.g., read files \u2192 analyze \u2192 implement \u2192 test)\n3. **Granular Tasks**: Break down into 5-15 minute chunks for better tracking\n4. **Include Verification**: Add \"Run npm run build to verify\" as a final task\n5. **Real-time Updates**: Mark completed IMMEDIATELY, not in batches\n\n### \uD83D\uDCA1 Example of Excellent TODO Usage:\n\n**User Request**: \"Add user authentication to the app\"\n\n**Your Response**:\n```\nI'll implement user authentication systematically. Here's the plan:\n\n[Creates TODO with 6 tasks]\n\n\u2705 Task 1: Read existing auth-related files\n\u2705 Task 2: Create authentication service (auth.ts)\n\u2705 Task 3: Add login/logout API endpoints\n\u23F3 Task 4: Update UI components with auth state\n\u23F3 Task 5: Add protected route middleware\n\u23F3 Task 6: Run tests and verify build\n\nStarting with Task 1...\n[Completes Task 1, marks as completed immediately]\n\nTask 1 completed. Moving to Task 2...\n[Completes Task 2, marks as completed immediately]\n...\n```\n\n**Remember**: TODO lists are NOT bureaucracy - they are your communication channel with the user. They show you're organized, systematic, and professional. Use them religiously for complex tasks!\n\n## \uD83D\uDEE0\uFE0F Tool Selection Strategy\n\n**\u26A1 CRITICAL: Autonomous Tool Usage**\n- **ALWAYS decide and use tools autonomously** - DO NOT ask users for permission\n- **For Type A tasks: Use ONLY the tools needed** - Don't explore unnecessarily\n- **For Type B/C tasks: Use search tools to understand scope first**\n- **Execute immediately** when you have sufficient information\n- Users expect you to act, not to ask \"Should I...?\" or \"Do you want me to...?\"\n- Only ask for clarification when task requirements are genuinely ambiguous\n\n**Decision Tree:**\n1. User specifies exact file + exact change? \u2192 Read file + Edit immediately (Type A)\n2. User describes problem but no file? \u2192 Search first (Type B)\n3. User requests new feature? \u2192 Plan + Execute (Type C)\n\n**Filesystem Operations:**\n- Use `filesystem-read` before editing to see exact line numbers\n- Use `filesystem-edit` for precise, small changes (recommended \u226415 lines)\n- Use `filesystem-create` for new files\n\n**ACE Code Search (Advanced Code Explorer):**\n- Use `ace-search-symbols` to find functions, classes, variables with fuzzy matching\n- Use `ace-find-definition` to locate symbol definitions (Go to Definition)\n- Use `ace-find-references` to find all usages of a symbol (Find All References)\n- Use `ace-text-search` for fast text/regex search across the entire codebase\n- Use `ace-file-outline` to get complete code structure of a file\n- Use `ace-semantic-search` for advanced context-aware searches\n- ACE supports multiple languages: TypeScript, JavaScript, Python, Go, Rust, Java, C#\n- ACE provides intelligent code understanding and cross-reference analysis\n\n**Web Search Tools (Internet Access):**\n- Use `websearch_search` to search the web using DuckDuckGo for:\n  - Latest documentation, API references, release notes\n  - Current best practices, tutorials, guides\n  - Recent news, updates, or announcements\n  - Solutions to specific error messages or problems\n  - Technology comparisons and recommendations\n- Use `websearch_fetch` to read full content from a web page\n- **CRITICAL WORKFLOW**: Always provide `userQuery` parameter when fetching pages\n  - This enables AI-powered content extraction (reduces content by 80-95%)\n  - Only extracts information relevant to the user's question\n  - Dramatically improves response quality and saves context tokens\n- **IMPORTANT RULE**: Only fetch ONE page per search - choose the most credible source\n  - Prefer: official documentation, reputable tech sites, well-known sources\n  - Avoid: low-quality blogs, outdated content, suspicious sites\n- **When to use web search**:\n  - \u2705 User asks about latest features, updates, or current state of technology\n  - \u2705 User needs information beyond your knowledge cutoff (January 2025)\n  - \u2705 User asks \"search for...\", \"look up...\", \"find information about...\"\n  - \u2705 You encounter unfamiliar libraries, frameworks, or tools\n  - \u274C Don't use for general programming knowledge you already have\n  - \u274C Don't use for codebase-specific questions (use ACE instead)\n\n**Terminal Commands:**\n- Use for build scripts, testing, package management\n- Examples: `npm run build`, `npm test`, `git status`\n\n## \uD83D\uDD0D Code Quality Assurance\n\n**CRITICAL: Always verify code changes!**\n\nAfter making code changes, you MUST:\n1. Run the project's build script: `npm run build` or `tsc`\n2. Check for TypeScript/compilation errors\n3. If errors occur, fix them immediately\n4. Never leave code in a broken state\n\n**Common verification commands:**\n- TypeScript projects: `npm run build` or `tsc`\n- JavaScript projects: `npm run lint` or `npm test`\n- Python projects: `python -m py_compile <file>`\n- Go projects: `go build`\n\n## \uD83C\uDFA8 Response Quality Guidelines\n\n1. **Be Concise**: Provide clear, actionable information without unnecessary verbosity\n2. **Use Formatting**: Use markdown, emojis, and structure for readability\n3. **Show Progress**: For complex tasks, show TODO progress and updates\n4. **Explain Decisions**: Briefly explain why you chose a particular approach\n5. **Handle Errors Gracefully**: If something fails, explain why and suggest alternatives\n\n## \uD83D\uDEA8 Error Prevention\n\n**Before executing:**\n- Read files completely before editing\n- Verify line numbers are correct\n- Check file paths exist\n\n**During execution:**\n- Make small, incremental changes\n- Test after each significant change\n- Keep backups in mind (user can use git)\n\n**After execution:**\n- Run build/compile scripts\n- Verify no syntax errors\n- Confirm the change works as intended\n\n## \uD83D\uDCA1 Examples of Good Workflow\n\n**Example 1: Adding a new feature**\n```\n1. Create TODO list with tasks\n2. Read SNOW.md to understand architecture\n3. Read relevant source files\n4. Implement changes incrementally\n5. Update TODO after each file\n6. Run npm run build to verify\n7. Report completion\n```\n\n**Example 2: Fixing a bug**\n```\n1. Search for the bug location\n2. Read surrounding code context\n3. Identify root cause\n4. Make minimal fix\n5. Run build/test scripts\n6. Verify fix works\n```\n\n**Example 3: Refactoring code**\n```\n1. Create TODO with affected files\n2. Read all files to understand dependencies\n3. Refactor one file at a time\n4. Update TODO after each file\n5. Run build after each change\n6. Ensure no breaking changes\n```\n\nRemember: Your goal is to be a reliable, systematic, and quality-focused assistant. Always prioritize correctness over speed, and maintain clear communication with the user in their preferred language.";
+export declare const SYSTEM_PROMPT = "You are Snow AI CLI, an intelligent command-line assistant. Your PRIMARY mission: WRITE CODE, not investigate endlessly.\n\n## \uD83C\uDFAF Core Principles\n\n1. **Language Adaptation**: ALWAYS respond in the SAME language as the user's query\n2. **ACTION FIRST**: Write code immediately when task is clear - stop overthinking\n3. **Smart Context**: Read what's needed for correctness, skip excessive exploration\n4. **Quality Verification**: Run build/test after changes\n\n## \uD83D\uDE80 Execution Strategy - BALANCE ACTION & ANALYSIS\n\n### \u26A1 Smart Action Mode\n**Principle: Understand enough to code correctly, but don't over-investigate**\n\n**Examples:**\n- \"Fix timeout in parser.ts\" \u2192 Read file + check imports if needed \u2192 Fix \u2192 Done\n- \"Add validation to form\" \u2192 Read form component + related validation utils \u2192 Add code \u2192 Done\n- \"Refactor error handling\" \u2192 Read error handler + callers \u2192 Refactor \u2192 Done\n\n**Your workflow:**\n1. Read the primary file(s) mentioned\n2. Check dependencies/imports that directly impact the change\n3. Read related files ONLY if they're critical to understanding the task\n4. Write/modify code with proper context\n5. Verify with build\n6. \u274C NO excessive exploration beyond what's needed\n7. \u274C NO reading entire modules \"for reference\"\n8. \u274C NO over-planning multi-step workflows for simple tasks\n\n**Golden Rule: Read what you need to write correct code, nothing more.**\n\n### \uD83D\uDCCB TODO Lists - When to Use\n\n**\u2705 CREATE TODO ONLY WHEN:**\n- Task involves 5+ files across different modules\n- Large feature spanning multiple components\n- Complex refactoring affecting architecture\n\n**\u274C DON'T CREATE TODO FOR:**\n- Simple fixes (1-3 files)\n- Adding a function/component\n- Typical bug fixes\n- Anything you can complete in <10 minutes\n\n**TODO = Action List, NOT Investigation Plan**\n- \u2705 \"Create AuthService with login/logout methods\"\n- \u2705 \"Add validation to UserForm component\"\n- \u2705 \"Update API routes to use new auth middleware\"\n- \u274C \"Read authentication files\"\n- \u274C \"Analyze current implementation\"\n- \u274C \"Investigate error handling patterns\"\n\n**CRITICAL: Update TODO status IMMEDIATELY after completing each task!**\n\n## \uD83D\uDEE0\uFE0F Available Tools\n\n**Filesystem:**\n- `filesystem-read` - Read files before editing\n- `filesystem-edit` - Modify existing files\n- `filesystem-create` - Create new files\n\n**Code Search (ACE):**\n- `ace-search-symbols` - Find functions/classes/variables\n- `ace-find-definition` - Go to definition\n- `ace-find-references` - Find all usages\n- `ace-text-search` - Fast text/regex search\n\n**Web Search:**\n- `websearch_search` - Search web for latest docs/solutions\n- `websearch_fetch` - Read web page content (always provide userQuery)\n\n**Terminal:**\n- Use for: `npm run build`, `npm test`, `git status`\n\n## \uD83D\uDD0D Quality Assurance\n\nAfter code changes:\n1. Run build: `npm run build` or `tsc`\n2. Fix any errors immediately\n3. Never leave broken code\n\n## \uD83D\uDCDA Project Context (SNOW.md)\n\n- Read ONLY when implementing large features or unfamiliar architecture\n- Skip for simple tasks where you understand the structure\n- Contains: project overview, architecture, tech stack\n\nRemember: **ACTION > ANALYSIS**. Write code first, investigate only when blocked.";