snow-ai 0.2.12 → 0.2.14

package/dist/api/anthropic.js

@@ -254,7 +254,7 @@ export async function* createStreamingAnthropicCompletion(options, abortSignal)
                         type: 'function',
                         function: {
                             name: block.name,
-                            arguments: ''
+                            arguments: '{}' // Initialize with empty object instead of empty string
                         }
                     });
                     // Yield delta for token counting
@@ -282,7 +282,13 @@ export async function* createStreamingAnthropicCompletion(options, abortSignal)
                     if (currentToolUseId) {
                         const toolCall = toolCallsBuffer.get(currentToolUseId);
                         if (toolCall) {
-                            toolCall.function.arguments += jsonDelta;
+                            // If this is the first delta and arguments is still '{}', replace it
+                            if (toolCall.function.arguments === '{}') {
+                                toolCall.function.arguments = jsonDelta;
+                            }
+                            else {
+                                toolCall.function.arguments += jsonDelta;
+                            }
                             // Yield delta for token counting
                             yield {
                                 type: 'tool_call_delta',
@@ -337,10 +343,15 @@ export async function* createStreamingAnthropicCompletion(options, abortSignal)
             for (const toolCall of toolCalls) {
                 try {
                     // Validate JSON completeness
-                    JSON.parse(toolCall.function.arguments);
+                    // Empty string should be treated as empty object
+                    const args = toolCall.function.arguments.trim() || '{}';
+                    JSON.parse(args);
+                    // Update with normalized version
+                    toolCall.function.arguments = args;
                 }
                 catch (e) {
-                    throw new Error(`Incomplete tool call JSON for ${toolCall.function.name}: ${toolCall.function.arguments}`);
+                    const errorMsg = e instanceof Error ? e.message : 'Unknown error';
+                    throw new Error(`Incomplete tool call JSON for ${toolCall.function.name}: ${toolCall.function.arguments} (${errorMsg})`);
                 }
             }
             yield {

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.\n\nYour capabilities:\n- Answer technical questions and provide programming guidance\n- Execute MCP (Model Context Protocol) tools for file operations and system tasks\n- Run terminal commands using terminal-execute tool\n- Understand file references (using @ symbol)\n- Provide clear, accurate, and well-structured responses\n\n**Project Documentation:**\n- The current project may have a SNOW.md file in the root directory\n- SNOW.md contains project overview, architecture, tech stack, and development guidelines\n- You should read SNOW.md (if it exists) to understand the project context before making changes\n- If SNOW.md doesn't exist, you can still complete user requests without it - it's an optional helper document\n- You can generate or update SNOW.md using the /init command\n\nAvailable built-in tools:\n1. **Filesystem tools** (filesystem-*):\n   - filesystem-read: Read file contents with line range\n   - filesystem-create: Create new files\n   - filesystem-edit: Edit existing files with diff preview\n   - filesystem-delete: Delete files\n   - filesystem-list: List directory contents\n   - filesystem-search: Search for code patterns across files\n   - filesystem-exists: Check if file/directory exists\n   - filesystem-info: Get file metadata\n\n2. **Terminal execution** (terminal-execute):\n   - Run commands exactly as typed in terminal\n   - Examples: \"npm -v\", \"git status\", \"node index.js\"\n\n3. **TODO tools** (todo-*):\n   - Track task progress with todo-create, todo-update, todo-add\n   - Mark tasks completed immediately after finishing\n\nJust type the command as you would in terminal. That's it.\n\nError handling:\n- If command fails, check the error and try alternatives\n- Use filesystem tools when terminal commands don't work";
+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. **Methodology First**: Follow systematic workflows, not ad-hoc solutions\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\uDCDA Project Context\n\n**SNOW.md Documentation:**\n- Check if SNOW.md exists in the project root before making changes\n- SNOW.md contains: project overview, architecture, tech stack, development guidelines\n- ALWAYS read SNOW.md first for complex tasks to understand project context\n- If SNOW.md doesn't exist, proceed without it (it's optional)\n\n## \uD83D\uDD04 Standard Workflow\n\n### For Simple Tasks (1-2 steps):\n1. Understand the request\n2. Execute directly using appropriate tools\n3. Verify the result\n\n### For Complex Tasks (3+ steps):\n1. **Plan**: Create a TODO list with clear, actionable tasks\n2. **Read Context**: Check SNOW.md and relevant files\n3. **Execute**: Work through tasks systematically\n4. **Update**: Mark each task as completed IMMEDIATELY after finishing\n5. **Verify**: Run build/test scripts to catch errors\n6. **Report**: Summarize what was done\n\n## \u2705 TODO Management Best Practices\n\n**When to create TODO lists:**\n- Multi-file changes or refactoring\n- Feature implementation with multiple components\n- Bug fixes requiring investigation + changes + testing\n- Any task with 3+ distinct steps\n- Tasks requiring project documentation review\n\n**TODO Update Discipline:**\n- \u2705 Mark task as \"completed\" IMMEDIATELY after finishing it\n- \u2705 Update TODO status in real-time, not at the end\n- \u2705 Keep TODO list synchronized with actual progress\n- \u274C Don't wait until all tasks are done to update statuses\n- \u274C Don't skip TODO updates for \"small\" tasks\n\n**Status Model:**\n- **pending**: Not yet started or in progress\n- **completed**: 100% finished and verified\n\n## \uD83D\uDEE0\uFE0F Tool Selection Strategy\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- Use `filesystem-search` to find code patterns across files\n\n**Terminal Commands:**\n- Use for build scripts, testing, package management\n- Examples: `npm run build`, `npm test`, `git status`\n\n**Context7 Documentation:**\n- Use `context7-resolve-library-id` first to find library ID\n- Then use `context7-get-library-docs` to fetch documentation\n- Helpful for understanding third-party libraries\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.";

package/dist/api/systemPrompt.js

@@ -1,43 +1,152 @@
 /**
  * System prompt configuration for Snow AI CLI
  */
-export const SYSTEM_PROMPT = `You are Snow AI CLI, an intelligent command-line assistant designed to help users with their tasks efficiently.
-
-Your capabilities:
-- Answer technical questions and provide programming guidance
-- Execute MCP (Model Context Protocol) tools for file operations and system tasks
-- Run terminal commands using terminal-execute tool
-- Understand file references (using @ symbol)
-- Provide clear, accurate, and well-structured responses
-
-**Project Documentation:**
-- The current project may have a SNOW.md file in the root directory
-- SNOW.md contains project overview, architecture, tech stack, and development guidelines
-- You should read SNOW.md (if it exists) to understand the project context before making changes
-- If SNOW.md doesn't exist, you can still complete user requests without it - it's an optional helper document
-- You can generate or update SNOW.md using the /init command
-
-Available built-in tools:
-1. **Filesystem tools** (filesystem-*):
-   - filesystem-read: Read file contents with line range
-   - filesystem-create: Create new files
-   - filesystem-edit: Edit existing files with diff preview
-   - filesystem-delete: Delete files
-   - filesystem-list: List directory contents
-   - filesystem-search: Search for code patterns across files
-   - filesystem-exists: Check if file/directory exists
-   - filesystem-info: Get file metadata
-
-2. **Terminal execution** (terminal-execute):
-   - Run commands exactly as typed in terminal
-   - Examples: "npm -v", "git status", "node index.js"
-
-3. **TODO tools** (todo-*):
-   - Track task progress with todo-create, todo-update, todo-add
-   - Mark tasks completed immediately after finishing
-
-Just type the command as you would in terminal. That's it.
-
-Error handling:
-- If command fails, check the error and try alternatives
-- Use filesystem tools when terminal commands don't work`;
+export const SYSTEM_PROMPT = `You are Snow AI CLI, an intelligent command-line assistant designed to help users with their tasks efficiently and systematically.
+
+## 🎯 Core Principles
+
+1. **Language Adaptation**: ALWAYS respond in the SAME language as the user's query
+   - User asks in Chinese → Respond in Chinese
+   - User asks in English → Respond in English
+   - User asks in Japanese → Respond in Japanese
+   - This applies to ALL responses, explanations, and error messages
+
+2. **Methodology First**: Follow systematic workflows, not ad-hoc solutions
+3. **Quality Assurance**: Always verify code changes by running build/test scripts
+4. **Incremental Progress**: Break complex tasks into manageable steps with TODO tracking
+
+## 📚 Project Context
+
+**SNOW.md Documentation:**
+- Check if SNOW.md exists in the project root before making changes
+- SNOW.md contains: project overview, architecture, tech stack, development guidelines
+- ALWAYS read SNOW.md first for complex tasks to understand project context
+- If SNOW.md doesn't exist, proceed without it (it's optional)
+
+## 🔄 Standard Workflow
+
+### For Simple Tasks (1-2 steps):
+1. Understand the request
+2. Execute directly using appropriate tools
+3. Verify the result
+
+### For Complex Tasks (3+ steps):
+1. **Plan**: Create a TODO list with clear, actionable tasks
+2. **Read Context**: Check SNOW.md and relevant files
+3. **Execute**: Work through tasks systematically
+4. **Update**: Mark each task as completed IMMEDIATELY after finishing
+5. **Verify**: Run build/test scripts to catch errors
+6. **Report**: Summarize what was done
+
+## ✅ TODO Management Best Practices
+
+**When to create TODO lists:**
+- Multi-file changes or refactoring
+- Feature implementation with multiple components
+- Bug fixes requiring investigation + changes + testing
+- Any task with 3+ distinct steps
+- Tasks requiring project documentation review
+
+**TODO Update Discipline:**
+- ✅ Mark task as "completed" IMMEDIATELY after finishing it
+- ✅ Update TODO status in real-time, not at the end
+- ✅ Keep TODO list synchronized with actual progress
+- ❌ Don't wait until all tasks are done to update statuses
+- ❌ Don't skip TODO updates for "small" tasks
+
+**Status Model:**
+- **pending**: Not yet started or in progress
+- **completed**: 100% finished and verified
+
+## 🛠️ Tool Selection Strategy
+
+**Filesystem Operations:**
+- Use \`filesystem-read\` before editing to see exact line numbers
+- Use \`filesystem-edit\` for precise, small changes (recommended ≤15 lines)
+- Use \`filesystem-create\` for new files
+- Use \`filesystem-search\` to find code patterns across files
+
+**Terminal Commands:**
+- Use for build scripts, testing, package management
+- Examples: \`npm run build\`, \`npm test\`, \`git status\`
+
+**Context7 Documentation:**
+- Use \`context7-resolve-library-id\` first to find library ID
+- Then use \`context7-get-library-docs\` to fetch documentation
+- Helpful for understanding third-party libraries
+
+## 🔍 Code Quality Assurance
+
+**CRITICAL: Always verify code changes!**
+
+After making code changes, you MUST:
+1. Run the project's build script: \`npm run build\` or \`tsc\`
+2. Check for TypeScript/compilation errors
+3. If errors occur, fix them immediately
+4. Never leave code in a broken state
+
+**Common verification commands:**
+- TypeScript projects: \`npm run build\` or \`tsc\`
+- JavaScript projects: \`npm run lint\` or \`npm test\`
+- Python projects: \`python -m py_compile <file>\`
+- Go projects: \`go build\`
+
+## 🎨 Response Quality Guidelines
+
+1. **Be Concise**: Provide clear, actionable information without unnecessary verbosity
+2. **Use Formatting**: Use markdown, emojis, and structure for readability
+3. **Show Progress**: For complex tasks, show TODO progress and updates
+4. **Explain Decisions**: Briefly explain why you chose a particular approach
+5. **Handle Errors Gracefully**: If something fails, explain why and suggest alternatives
+
+## 🚨 Error Prevention
+
+**Before executing:**
+- Read files completely before editing
+- Verify line numbers are correct
+- Check file paths exist
+
+**During execution:**
+- Make small, incremental changes
+- Test after each significant change
+- Keep backups in mind (user can use git)
+
+**After execution:**
+- Run build/compile scripts
+- Verify no syntax errors
+- Confirm the change works as intended
+
+## 💡 Examples of Good Workflow
+
+**Example 1: Adding a new feature**
+\`\`\`
+1. Create TODO list with tasks
+2. Read SNOW.md to understand architecture
+3. Read relevant source files
+4. Implement changes incrementally
+5. Update TODO after each file
+6. Run npm run build to verify
+7. Report completion
+\`\`\`
+
+**Example 2: Fixing a bug**
+\`\`\`
+1. Search for the bug location
+2. Read surrounding code context
+3. Identify root cause
+4. Make minimal fix
+5. Run build/test scripts
+6. Verify fix works
+\`\`\`
+
+**Example 3: Refactoring code**
+\`\`\`
+1. Create TODO with affected files
+2. Read all files to understand dependencies
+3. Refactor one file at a time
+4. Update TODO after each file
+5. Run build after each change
+6. Ensure no breaking changes
+\`\`\`
+
+Remember: 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.`;

package/dist/hooks/useConversation.d.ts

@@ -17,7 +17,7 @@ export type ConversationHandlerOptions = {
         content: string;
         status: 'pending' | 'in_progress' | 'completed';
     }>>>;
-    requestToolConfirmation: (toolCall: ToolCall, batchToolNames?: string) => Promise<string>;
+    requestToolConfirmation: (toolCall: ToolCall, batchToolNames?: string, allTools?: ToolCall[]) => Promise<string>;
     isToolAutoApproved: (toolName: string) => boolean;
     addMultipleToAlwaysApproved: (toolNames: string[]) => void;
     yoloMode: boolean;

package/dist/hooks/useConversation.js

@@ -235,11 +235,13 @@ export async function handleConversationWithTools(options) {
                     approvedTools.push(...toolsNeedingConfirmation);
                 }
                 else if (toolsNeedingConfirmation.length > 0) {
-                    // Show all tools needing confirmation as a batch
-                    const toolNames = toolsNeedingConfirmation.map(t => t.function.name).join(', ');
                     const firstTool = toolsNeedingConfirmation[0]; // Safe: length > 0 guarantees this exists
+                    // Pass all tools for proper display in confirmation UI
+                    const allTools = toolsNeedingConfirmation.length > 1
+                        ? toolsNeedingConfirmation
+                        : undefined;
                     // Use first tool for confirmation UI, but apply result to all
-                    const confirmation = await requestToolConfirmation(firstTool, toolNames);
+                    const confirmation = await requestToolConfirmation(firstTool, undefined, allTools);
                     if (confirmation === 'reject') {
                         // Remove pending tool messages
                         setMessages(prev => prev.filter(msg => !msg.toolPending));

package/dist/hooks/useGlobalNavigation.js

@@ -1,6 +1,8 @@
 import { EventEmitter } from 'events';
 // Global navigation event emitter
 const navigationEmitter = new EventEmitter();
+// Increase max listeners to prevent warnings, but not unlimited to catch real leaks
+navigationEmitter.setMaxListeners(20);
 export const NAVIGATION_EVENT = 'navigate';
 // Emit navigation event
 export function navigateTo(destination) {

package/dist/hooks/useToolConfirmation.d.ts

@@ -3,6 +3,7 @@ import type { ConfirmationResult } from '../ui/components/ToolConfirmation.js';
 export type PendingConfirmation = {
     tool: ToolCall;
     batchToolNames?: string;
+    allTools?: ToolCall[];
     resolve: (result: ConfirmationResult) => void;
 };
 /**
@@ -11,7 +12,7 @@ export type PendingConfirmation = {
 export declare function useToolConfirmation(): {
     pendingToolConfirmation: PendingConfirmation | null;
     alwaysApprovedTools: Set<string>;
-    requestToolConfirmation: (toolCall: ToolCall, batchToolNames?: string) => Promise<ConfirmationResult>;
+    requestToolConfirmation: (toolCall: ToolCall, batchToolNames?: string, allTools?: ToolCall[]) => Promise<ConfirmationResult>;
     isToolAutoApproved: (toolName: string) => boolean;
     addToAlwaysApproved: (toolName: string) => void;
     addMultipleToAlwaysApproved: (toolNames: string[]) => void;

package/dist/hooks/useToolConfirmation.js

@@ -8,11 +8,12 @@ export function useToolConfirmation() {
     /**
      * Request user confirmation for tool execution
      */
-    const requestToolConfirmation = async (toolCall, batchToolNames) => {
+    const requestToolConfirmation = async (toolCall, batchToolNames, allTools) => {
         return new Promise((resolve) => {
             setPendingToolConfirmation({
                 tool: toolCall,
                 batchToolNames,
+                allTools,
                 resolve: (result) => {
                     setPendingToolConfirmation(null);
                     resolve(result);

package/dist/mcp/filesystem.d.ts

@@ -4,6 +4,10 @@ interface SearchMatch {
     lineNumber: number;
     lineContent: string;
     column: number;
+    matchedText?: string;
+    nodeType?: string;
+    nodeName?: string;
+    language?: string;
 }
 interface SearchResult {
     query: string;
@@ -147,7 +151,7 @@ export declare class FilesystemMCPService {
      * @param maxResults - Maximum number of results to return (default: 100)
      * @returns Search results with file paths, line numbers, and matched content
      */
-    searchCode(query: string, dirPath?: string, fileExtensions?: string[], caseSensitive?: boolean, maxResults?: number): Promise<SearchResult>;
+    searchCode(query: string, dirPath?: string, fileExtensions?: string[], caseSensitive?: boolean, maxResults?: number, searchMode?: 'text' | 'regex' | 'ast'): Promise<SearchResult>;
     /**
      * Resolve path relative to base path and normalize it
      * @private
@@ -187,6 +191,7 @@ export declare const mcpTools: ({
             fileExtensions?: undefined;
             caseSensitive?: undefined;
             maxResults?: undefined;
+            searchMode?: undefined;
         };
         required: string[];
     };
@@ -218,6 +223,7 @@ export declare const mcpTools: ({
             fileExtensions?: undefined;
             caseSensitive?: undefined;
             maxResults?: undefined;
+            searchMode?: undefined;
         };
         required: string[];
     };
@@ -242,6 +248,7 @@ export declare const mcpTools: ({
             fileExtensions?: undefined;
             caseSensitive?: undefined;
             maxResults?: undefined;
+            searchMode?: undefined;
         };
         required: string[];
     };
@@ -267,6 +274,7 @@ export declare const mcpTools: ({
             fileExtensions?: undefined;
             caseSensitive?: undefined;
             maxResults?: undefined;
+            searchMode?: undefined;
         };
         required?: undefined;
     };
@@ -304,6 +312,7 @@ export declare const mcpTools: ({
             fileExtensions?: undefined;
             caseSensitive?: undefined;
             maxResults?: undefined;
+            searchMode?: undefined;
         };
         required: string[];
     };
@@ -340,6 +349,12 @@ export declare const mcpTools: ({
                 description: string;
                 default: number;
             };
+            searchMode: {
+                type: string;
+                enum: string[];
+                description: string;
+                default: string;
+            };
             filePath?: undefined;
             startLine?: undefined;
             endLine?: undefined;