@triedotdev/mcp 1.0.128 → 1.0.129

package/dist/{chunk-4GPN2QZ4.js → chunk-VHQBL2I7.js}

@@ -5092,6 +5092,30 @@ var CHAT_TOOLS = [
       required: ["file", "goal", "violation"]
     }
   },
+  {
+    name: "trie_propose_fixes_batch",
+    description: "Propose fixes for multiple goal violations at once. More efficient than calling trie_propose_fix multiple times. Use when the user wants to fix multiple violations.",
+    input_schema: {
+      type: "object",
+      properties: {
+        fixes: {
+          type: "array",
+          description: "Array of fix proposals",
+          items: {
+            type: "object",
+            properties: {
+              file: { type: "string", description: "File path with the goal violation" },
+              goal: { type: "string", description: "The goal that was violated" },
+              violation: { type: "string", description: "Description of the violation" },
+              suggestedFix: { type: "string", description: "Suggested fix for the violation (optional)" }
+            },
+            required: ["file", "goal", "violation"]
+          }
+        }
+      },
+      required: ["fixes"]
+    }
+  },
   {
     name: "trie_search_files",
     description: "Search source code files for text patterns using ripgrep. Note: Requires ripgrep to be installed. For emoji detection, use trie_scan_for_goal_violations instead.",
@@ -5304,6 +5328,38 @@ Type "yes" to proceed, or "no" to cancel.
 
 [PENDING_FIX:${JSON.stringify(fixProposal)}]`;
       }
+      case "trie_propose_fixes_batch": {
+        const fixes = input.fixes;
+        if (!Array.isArray(fixes) || fixes.length === 0) {
+          return "At least one fix is required.";
+        }
+        for (const fix of fixes) {
+          if (!fix.file?.trim()) return "All fixes must have a file path.";
+          if (!fix.goal?.trim()) return "All fixes must have a goal.";
+          if (!fix.violation?.trim()) return "All fixes must have a violation description.";
+        }
+        const fixProposals = fixes.map((f) => ({
+          file: f.file.trim(),
+          goal: f.goal.trim(),
+          violation: f.violation.trim(),
+          suggestedFix: f.suggestedFix?.trim(),
+          directory
+        }));
+        let message = `Found ${fixes.length} violation(s) to fix:
+
+`;
+        for (const fix of fixProposals) {
+          message += `\u2022 ${fix.file}
+`;
+        }
+        message += `
+Type "yes to all" to fix all files, or "no" to cancel.`;
+        for (const fixProposal of fixProposals) {
+          message += `
+[PENDING_FIX:${JSON.stringify(fixProposal)}]`;
+        }
+        return message;
+      }
       case "trie_search_files": {
         const pattern = String(input.pattern || "").trim();
         const filePattern = input.filePattern ? String(input.filePattern).trim() : void 0;
@@ -5536,17 +5592,17 @@ var SYSTEM_PROMPT = `You are Trie, a code guardian assistant embedded in a termi
 
 **When user asks to fix violations:**
 1. Look in "Recent goal violations (nudges)" section of project context
-2. Extract: file path, goal description, and violation details
-3. Use trie_propose_fix ONCE per file to propose the fix - this will ASK THE USER for confirmation
-4. AFTER calling trie_propose_fix, WAIT for the user to respond - do NOT call any tools
-5. When the user says "yes" or "no", the system automatically handles spawning Claude Code - you should NOT call trie_propose_fix again
-6. Simply acknowledge that the fixes are being applied
+2. Extract: file path, goal description, and violation details for ALL files
+3. If multiple violations: Call trie_propose_fixes_batch ONCE with all fixes
+4. If single violation: Call trie_propose_fix once
+5. AFTER the tool call completes, the system will ask for user confirmation - do NOT add your own confirmation message
+6. When the user says "yes", "yes to all", or "no", the system handles spawning Claude Code automatically
 
 Examples:
 - User: "do we have emojis?" \u2192 Check nudges first. If none or unclear: Call trie_scan_for_goal_violations to scan the codebase.
 - User: "run a full scan for emojis" \u2192 Call trie_scan_for_goal_violations directly.
-- User: "fix the emoji violation" \u2192 Find emoji violation in nudges, call trie_propose_fix ONCE (will ask user to confirm), then STOP and wait
-- User responds "yes" after trie_propose_fix \u2192 Do NOT call trie_propose_fix again! Just say "Spawning Claude Code to fix the files..." The system handles it automatically.
+- User: "fix the emoji violations" \u2192 Find ALL emoji violations in nudges, call trie_propose_fixes_batch ONCE with all fixes, then STOP
+- User responds "yes to all" after proposal \u2192 Just say "Spawning Claude Code to fix all files..." The system handles it.
 - User: "search for TODO comments" \u2192 If there's a goal about TODOs, use trie_scan_for_goal_violations. Otherwise explain no such goal exists.
 
 Answer concisely. Reference specific files, decisions, and patterns when relevant.`;
@@ -5697,7 +5753,7 @@ ${contextBlock}`;
         tools: CHAT_TOOLS,
         executeTool,
         maxTokens: 4096,
-        maxToolRounds: 5
+        maxToolRounds: 8
       });
       if (result.success) {
         const action = {
@@ -6487,4 +6543,4 @@ export {
   handleCheckpointTool,
   InteractiveDashboard
 };
-//# sourceMappingURL=chunk-4GPN2QZ4.js.map
+//# sourceMappingURL=chunk-VHQBL2I7.js.map