snow-ai 0.2.17 → 0.2.19

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. **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.";
+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 Best Practices\n\n**When to create TODO lists:**\n- Multi-file changes or refactoring (Type B, Type C)\n- Feature implementation with multiple components (Type C)\n- Bug fixes requiring investigation across multiple files (Type B)\n- DO NOT create TODO for single-file explicit edits (Type A)\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- \u274C Don't create TODO lists when user provides exact file + exact change\n- \u274C Don't wait until all tasks are done to update statuses\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**\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**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

@@ -11,48 +11,96 @@ export const SYSTEM_PROMPT = `You are Snow AI CLI, an intelligent command-line a
    - 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
+2. **Execution Over Exploration**: When users provide clear instructions with file paths, EXECUTE immediately
 3. **Quality Assurance**: Always verify code changes by running build/test scripts
 4. **Incremental Progress**: Break complex tasks into manageable steps with TODO tracking
 
+## 🚀 Task Classification & Execution Strategy
+
+**CRITICAL: Identify task type first to avoid unnecessary exploration!**
+
+### Type A: Explicit Instructions (EXECUTE IMMEDIATELY)
+**User provides:** Specific file path + Clear problem description + Expected change
+**Examples:**
+- "Modify src/utils/parser.ts line 45, change timeout from 1000 to 5000"
+- "In components/Header.tsx, add a new prop 'showLogo: boolean'"
+- "Fix the bug in api/auth.ts where the token validation fails"
+
+**Your action:**
+1. ✅ Read the specified file(s) ONLY
+2. ✅ Make the required changes immediately
+3. ✅ Verify with build/test
+4. ❌ DO NOT search for related files unless the edit reveals a dependency issue
+5. ❌ DO NOT read SNOW.md unless you need architectural context
+6. ❌ DO NOT create TODO lists for single-file edits
+
+### Type B: Exploratory Tasks (INVESTIGATE FIRST)
+**User provides:** Vague description + No file paths + Requires research
+**Examples:**
+- "Find all code handling user authentication"
+- "Refactor the entire authentication system"
+- "Find and fix all memory leaks"
+
+**Your action:**
+1. Use ACE code search to locate relevant code
+2. Create TODO list if multiple files involved
+3. Read SNOW.md if architectural understanding needed
+4. Execute systematically
+
+### Type C: Feature Implementation (PLAN & EXECUTE)
+**User provides:** Feature request requiring multiple files/components
+**Examples:**
+- "Add dark mode support"
+- "Implement user profile editing"
+- "Create a new API endpoint for /api/users"
+
+**Your action:**
+1. Create TODO list with specific tasks
+2. Check SNOW.md for architectural patterns
+3. Execute incrementally, updating TODO after each step
+
 ## 📚 Project Context
 
 **SNOW.md Documentation:**
-- Check if SNOW.md exists in the project root before making changes
+- ONLY read SNOW.md for Type B (Exploratory) and Type C (Feature) tasks
+- Skip SNOW.md for Type A (Explicit) tasks where user specifies exact files
 - 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
+## 🔄 Simplified Workflow
+
+### For Explicit Instructions (Type A):
+1. Read the specified file(s)
+2. Execute the change immediately
+3. Verify with build/test
+4. Report completion
 
-### For Simple Tasks (1-2 steps):
-1. Understand the request
-2. Execute directly using appropriate tools
-3. Verify the result
+### For Exploratory Tasks (Type B):
+1. Search/locate relevant code
+2. Read necessary context
+3. Execute changes
+4. Verify and report
 
-### 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
+### For Feature Implementation (Type C):
+1. Create TODO list
+2. Check SNOW.md if needed
+3. Execute incrementally
+4. Update TODO after each step
+5. Verify and report
 
 ## ✅ 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
+- Multi-file changes or refactoring (Type B, Type C)
+- Feature implementation with multiple components (Type C)
+- Bug fixes requiring investigation across multiple files (Type B)
+- DO NOT create TODO for single-file explicit edits (Type A)
 
 **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 create TODO lists when user provides exact file + exact change
 - ❌ 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
@@ -60,11 +108,33 @@ export const SYSTEM_PROMPT = `You are Snow AI CLI, an intelligent command-line a
 
 ## 🛠️ Tool Selection Strategy
 
+**⚡ CRITICAL: Autonomous Tool Usage**
+- **ALWAYS decide and use tools autonomously** - DO NOT ask users for permission
+- **For Type A tasks: Use ONLY the tools needed** - Don't explore unnecessarily
+- **For Type B/C tasks: Use search tools to understand scope first**
+- **Execute immediately** when you have sufficient information
+- Users expect you to act, not to ask "Should I...?" or "Do you want me to...?"
+- Only ask for clarification when task requirements are genuinely ambiguous
+
+**Decision Tree:**
+1. User specifies exact file + exact change? → Read file + Edit immediately (Type A)
+2. User describes problem but no file? → Search first (Type B)
+3. User requests new feature? → Plan + Execute (Type C)
+
 **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
+
+**ACE Code Search (Advanced Code Explorer):**
+- Use \`ace-search-symbols\` to find functions, classes, variables with fuzzy matching
+- Use \`ace-find-definition\` to locate symbol definitions (Go to Definition)
+- Use \`ace-find-references\` to find all usages of a symbol (Find All References)
+- Use \`ace-text-search\` for fast text/regex search across the entire codebase
+- Use \`ace-file-outline\` to get complete code structure of a file
+- Use \`ace-semantic-search\` for advanced context-aware searches
+- ACE supports multiple languages: TypeScript, JavaScript, Python, Go, Rust, Java, C#
+- ACE provides intelligent code understanding and cross-reference analysis
 
 **Terminal Commands:**
 - Use for build scripts, testing, package management

package/dist/hooks/useConversation.js

@@ -390,14 +390,17 @@ export async function handleConversationWithTools(options) {
                         const statusText = isError ? `\n  └─ ${result.content}` : '';
                         // Check if this is an edit tool with diff data
                         let editDiffData;
-                        if (toolCall.function.name === 'filesystem-edit' && !isError) {
+                        if ((toolCall.function.name === 'filesystem-edit' || toolCall.function.name === 'filesystem-edit_search') && !isError) {
                             try {
                                 const resultData = JSON.parse(result.content);
                                 if (resultData.oldContent && resultData.newContent) {
                                     editDiffData = {
                                         oldContent: resultData.oldContent,
                                         newContent: resultData.newContent,
-                                        filename: JSON.parse(toolCall.function.arguments).filePath
+                                        filename: JSON.parse(toolCall.function.arguments).filePath,
+                                        completeOldContent: resultData.completeOldContent,
+                                        completeNewContent: resultData.completeNewContent,
+                                        contextStartLine: resultData.contextStartLine
                                     };
                                 }
                             }

package/dist/mcp/aceCodeSearch.d.ts

@@ -0,0 +1,314 @@
+/**
+ * ACE Code Search Types
+ */
+export interface CodeSymbol {
+    name: string;
+    type: 'function' | 'class' | 'method' | 'variable' | 'constant' | 'interface' | 'type' | 'enum' | 'import' | 'export';
+    filePath: string;
+    line: number;
+    column: number;
+    endLine?: number;
+    endColumn?: number;
+    signature?: string;
+    scope?: string;
+    language: string;
+    context?: string;
+}
+export interface CodeReference {
+    symbol: string;
+    filePath: string;
+    line: number;
+    column: number;
+    context: string;
+    referenceType: 'definition' | 'usage' | 'import' | 'type';
+}
+export interface SemanticSearchResult {
+    query: string;
+    symbols: CodeSymbol[];
+    references: CodeReference[];
+    totalResults: number;
+    searchTime: number;
+}
+export interface ASTNode {
+    type: string;
+    name?: string;
+    line: number;
+    column: number;
+    endLine?: number;
+    endColumn?: number;
+    children?: ASTNode[];
+}
+export declare class ACECodeSearchService {
+    private basePath;
+    private indexCache;
+    private lastIndexTime;
+    private readonly INDEX_CACHE_DURATION;
+    constructor(basePath?: string);
+    /**
+     * Detect programming language from file extension
+     */
+    private detectLanguage;
+    /**
+     * Parse file content to extract code symbols using regex patterns
+     */
+    private parseFileSymbols;
+    /**
+     * Get context lines around a specific line
+     */
+    private getContext;
+    /**
+     * Build or refresh the code symbol index
+     */
+    private buildIndex;
+    /**
+     * Search for symbols by name with fuzzy matching
+     */
+    searchSymbols(query: string, symbolType?: CodeSymbol['type'], language?: string, maxResults?: number): Promise<SemanticSearchResult>;
+    /**
+     * Find all references to a symbol
+     */
+    findReferences(symbolName: string, maxResults?: number): Promise<CodeReference[]>;
+    /**
+     * Find symbol definition (go to definition)
+     */
+    findDefinition(symbolName: string, contextFile?: string): Promise<CodeSymbol | null>;
+    /**
+     * Fast text search using built-in Node.js (no external dependencies)
+     * Searches for text patterns across files with glob filtering
+     */
+    textSearch(pattern: string, fileGlob?: string, isRegex?: boolean, maxResults?: number): Promise<Array<{
+        filePath: string;
+        line: number;
+        column: number;
+        content: string;
+    }>>;
+    /**
+     * Convert glob pattern to RegExp
+     * Supports: *, **, ?, [abc], {js,ts}
+     */
+    private globToRegex;
+    /**
+     * Get code outline for a file (all symbols in the file)
+     */
+    getFileOutline(filePath: string): Promise<CodeSymbol[]>;
+    /**
+     * Search with language-specific context (cross-reference search)
+     */
+    semanticSearch(query: string, searchType?: 'definition' | 'usage' | 'implementation' | 'all', language?: string, maxResults?: number): Promise<SemanticSearchResult>;
+    /**
+     * Clear the symbol index cache
+     */
+    clearCache(): void;
+    /**
+     * Get index statistics
+     */
+    getIndexStats(): {
+        totalFiles: number;
+        totalSymbols: number;
+        languageBreakdown: Record<string, number>;
+        cacheAge: number;
+    };
+}
+export declare const aceCodeSearchService: ACECodeSearchService;
+export declare const mcpTools: ({
+    name: string;
+    description: string;
+    inputSchema: {
+        type: string;
+        properties: {
+            query: {
+                type: string;
+                description: string;
+            };
+            symbolType: {
+                type: string;
+                enum: string[];
+                description: string;
+            };
+            language: {
+                type: string;
+                enum: string[];
+                description: string;
+            };
+            maxResults: {
+                type: string;
+                description: string;
+                default: number;
+            };
+            symbolName?: undefined;
+            contextFile?: undefined;
+            searchType?: undefined;
+            filePath?: undefined;
+            pattern?: undefined;
+            fileGlob?: undefined;
+            isRegex?: undefined;
+        };
+        required: string[];
+    };
+} | {
+    name: string;
+    description: string;
+    inputSchema: {
+        type: string;
+        properties: {
+            symbolName: {
+                type: string;
+                description: string;
+            };
+            contextFile: {
+                type: string;
+                description: string;
+            };
+            query?: undefined;
+            symbolType?: undefined;
+            language?: undefined;
+            maxResults?: undefined;
+            searchType?: undefined;
+            filePath?: undefined;
+            pattern?: undefined;
+            fileGlob?: undefined;
+            isRegex?: undefined;
+        };
+        required: string[];
+    };
+} | {
+    name: string;
+    description: string;
+    inputSchema: {
+        type: string;
+        properties: {
+            symbolName: {
+                type: string;
+                description: string;
+            };
+            maxResults: {
+                type: string;
+                description: string;
+                default: number;
+            };
+            query?: undefined;
+            symbolType?: undefined;
+            language?: undefined;
+            contextFile?: undefined;
+            searchType?: undefined;
+            filePath?: undefined;
+            pattern?: undefined;
+            fileGlob?: undefined;
+            isRegex?: undefined;
+        };
+        required: string[];
+    };
+} | {
+    name: string;
+    description: string;
+    inputSchema: {
+        type: string;
+        properties: {
+            query: {
+                type: string;
+                description: string;
+            };
+            searchType: {
+                type: string;
+                enum: string[];
+                description: string;
+                default: string;
+            };
+            language: {
+                type: string;
+                enum: string[];
+                description: string;
+            };
+            maxResults: {
+                type: string;
+                description: string;
+                default: number;
+            };
+            symbolType?: undefined;
+            symbolName?: undefined;
+            contextFile?: undefined;
+            filePath?: undefined;
+            pattern?: undefined;
+            fileGlob?: undefined;
+            isRegex?: undefined;
+        };
+        required: string[];
+    };
+} | {
+    name: string;
+    description: string;
+    inputSchema: {
+        type: string;
+        properties: {
+            filePath: {
+                type: string;
+                description: string;
+            };
+            query?: undefined;
+            symbolType?: undefined;
+            language?: undefined;
+            maxResults?: undefined;
+            symbolName?: undefined;
+            contextFile?: undefined;
+            searchType?: undefined;
+            pattern?: undefined;
+            fileGlob?: undefined;
+            isRegex?: undefined;
+        };
+        required: string[];
+    };
+} | {
+    name: string;
+    description: string;
+    inputSchema: {
+        type: string;
+        properties: {
+            pattern: {
+                type: string;
+                description: string;
+            };
+            fileGlob: {
+                type: string;
+                description: string;
+            };
+            isRegex: {
+                type: string;
+                description: string;
+                default: boolean;
+            };
+            maxResults: {
+                type: string;
+                description: string;
+                default: number;
+            };
+            query?: undefined;
+            symbolType?: undefined;
+            language?: undefined;
+            symbolName?: undefined;
+            contextFile?: undefined;
+            searchType?: undefined;
+            filePath?: undefined;
+        };
+        required: string[];
+    };
+} | {
+    name: string;
+    description: string;
+    inputSchema: {
+        type: string;
+        properties: {
+            query?: undefined;
+            symbolType?: undefined;
+            language?: undefined;
+            maxResults?: undefined;
+            symbolName?: undefined;
+            contextFile?: undefined;
+            searchType?: undefined;
+            filePath?: undefined;
+            pattern?: undefined;
+            fileGlob?: undefined;
+            isRegex?: undefined;
+        };
+        required?: undefined;
+    };
+})[];