@probelabs/probe 0.6.0-rc101 → 0.6.0-rc102

package/build/agent/ProbeAgent.js

@@ -384,7 +384,7 @@ Examples:
 </extract>
 
 <attempt_completion>
-<result>The configuration is loaded from src/config.js lines 15-25 which contains the database settings.</result>
+The configuration is loaded from src/config.js lines 15-25 which contains the database settings.
 </attempt_completion>
 
 # Special Case: Quick Completion
@@ -411,7 +411,7 @@ I need to find code related to error handling in the search module. The most app
 6. Wait for the tool execution result, which will be provided in the next message (within a <tool_result> block).
 7. Analyze the tool result and decide the next step. If more tool calls are needed, repeat steps 2-6.
 8. If the task is fully complete and all previous steps were successful, use the \`<attempt_completion>\` tool to provide the final answer. This is the ONLY way to finish the task.
-9. If you cannot proceed (e.g., missing information, invalid request), explain the issue clearly before using \`<attempt_completion>\` with an appropriate message in the \`<result>\` tag.
+9. If you cannot proceed (e.g., missing information, invalid request), use \`<attempt_completion>\` to explain the issue clearly with an appropriate message directly inside the tags.
 10. If your previous response was already correct and complete, you may use \`<attempt_complete>\` as a shorthand.
 
 Available Tools:

package/build/agent/index.js

@@ -2246,13 +2246,19 @@ For GitHub-compatible mermaid diagrams, avoid single quotes and parentheses in n
 
 **Rules:**
 - NO single quotes in any node labels: 'text' \u2192 "text" or text
-- NO parentheses in square brackets: [Text (detail)] \u2192 [Text - detail]
+- NO parentheses in square brackets: [Text (detail)] \u2192 [Text - detail]  
 - NO complex expressions in diamonds: {a && b} \u2192 {condition}
+- NO HTML tags in node labels: [<pre>code</pre>] \u2192 ["code block"] or [Code Block]
 - USE single quotes for styles and classes: classDef highlight fill:'#ff9999'
+- CRITICAL: When using quotes in node labels, place them INSIDE the brackets: ["quoted text"], NOT [quoted text"]
 
 **Examples:**
 - \u2705 [Load Config] ["Run command"] {Valid?}
+- \u2705 ["depends_on: [generate-items]"] (correct quote placement)
+- \u2705 ["Code Block"] (clean text instead of HTML)
 - \u274C [Load (config)] [Run 'command'] {isValid('x')}
+- \u274C [depends_on: [generate-items"] (incorrect quote placement - quote ends inside bracket)
+- \u274C [<pre>depends_on: [generate-items]</pre>] (HTML tags in node labels)
 
 **Diagram Type Selection:**
 
@@ -5140,7 +5146,7 @@ Examples:
 </extract>
 
 <attempt_completion>
-<result>The configuration is loaded from src/config.js lines 15-25 which contains the database settings.</result>
+The configuration is loaded from src/config.js lines 15-25 which contains the database settings.
 </attempt_completion>
 
 # Special Case: Quick Completion
@@ -5167,7 +5173,7 @@ I need to find code related to error handling in the search module. The most app
 6. Wait for the tool execution result, which will be provided in the next message (within a <tool_result> block).
 7. Analyze the tool result and decide the next step. If more tool calls are needed, repeat steps 2-6.
 8. If the task is fully complete and all previous steps were successful, use the \`<attempt_completion>\` tool to provide the final answer. This is the ONLY way to finish the task.
-9. If you cannot proceed (e.g., missing information, invalid request), explain the issue clearly before using \`<attempt_completion>\` with an appropriate message in the \`<result>\` tag.
+9. If you cannot proceed (e.g., missing information, invalid request), use \`<attempt_completion>\` to explain the issue clearly with an appropriate message directly inside the tags.
 10. If your previous response was already correct and complete, you may use \`<attempt_complete>\` as a shorthand.
 
 Available Tools:
@@ -6084,6 +6090,7 @@ import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js"
 import {
   CallToolRequestSchema,
   ErrorCode as ErrorCode2,
+  InitializeRequestSchema,
   ListToolsRequestSchema,
   McpError
 } from "@modelcontextprotocol/sdk/types.js";
@@ -6948,7 +6955,7 @@ var ProbeAgentMcpServer = class {
   constructor() {
     this.server = new Server(
       {
-        name: "@buger/probe-agent",
+        name: "@probelabs/probe agent",
         version: "1.0.0"
       },
       {
@@ -6965,6 +6972,18 @@ var ProbeAgentMcpServer = class {
     });
   }
   setupToolHandlers() {
+    this.server.setRequestHandler(InitializeRequestSchema, async (request) => {
+      return {
+        protocolVersion: "2024-11-05",
+        capabilities: {
+          tools: {}
+        },
+        serverInfo: {
+          name: "@probelabs/probe agent",
+          version: "1.0.0"
+        }
+      };
+    });
     this.server.setRequestHandler(ListToolsRequestSchema, async () => ({
       tools: [
         {
@@ -7386,7 +7405,12 @@ Please reformat your previous response to match this schema exactly. Only return
         }
       }
     }
-    console.log(result);
+    const resultMatch = result.match(/<result>([\s\S]*?)<\/result>/);
+    if (resultMatch) {
+      console.log(resultMatch[1].trim());
+    } else {
+      console.log(result);
+    }
     if (config.verbose) {
       const tokenUsage = agent.getTokenUsage();
       console.error(`

package/build/mcp/index.js

@@ -510,5 +510,5 @@ class ProbeServer {
         console.error('Probe MCP server running on stdio');
     }
 }
-const server = new ProbeServer(cliConfig.timeout, cliConfig.format);
+const server = new ProbeServer(cliConfig.timeout, cliConfig.format || 'outline-xml');
 server.run().catch(console.error);

package/build/mcp/index.ts

@@ -604,5 +604,5 @@ class ProbeServer {
   }
 }
 
-const server = new ProbeServer(cliConfig.timeout, cliConfig.format);
+const server = new ProbeServer(cliConfig.timeout, cliConfig.format || 'outline-xml');
 server.run().catch(console.error);

package/build/tools/system-message.js

@@ -73,13 +73,19 @@ For GitHub-compatible mermaid diagrams, avoid single quotes and parentheses in n
 
 **Rules:**
 - NO single quotes in any node labels: 'text' → "text" or text
-- NO parentheses in square brackets: [Text (detail)] → [Text - detail]
+- NO parentheses in square brackets: [Text (detail)] → [Text - detail]  
 - NO complex expressions in diamonds: {a && b} → {condition}
+- NO HTML tags in node labels: [<pre>code</pre>] → ["code block"] or [Code Block]
 - USE single quotes for styles and classes: classDef highlight fill:'#ff9999'
+- CRITICAL: When using quotes in node labels, place them INSIDE the brackets: ["quoted text"], NOT [quoted text"]
 
 **Examples:**
 - ✅ [Load Config] ["Run command"] {Valid?}
+- ✅ ["depends_on: [generate-items]"] (correct quote placement)
+- ✅ ["Code Block"] (clean text instead of HTML)
 - ❌ [Load (config)] [Run 'command'] {isValid('x')}
+- ❌ [depends_on: [generate-items"] (incorrect quote placement - quote ends inside bracket)
+- ❌ [<pre>depends_on: [generate-items]</pre>] (HTML tags in node labels)
 
 **Diagram Type Selection:**
 

package/cjs/agent/ProbeAgent.cjs

@@ -2268,13 +2268,19 @@ For GitHub-compatible mermaid diagrams, avoid single quotes and parentheses in n
 
 **Rules:**
 - NO single quotes in any node labels: 'text' \u2192 "text" or text
-- NO parentheses in square brackets: [Text (detail)] \u2192 [Text - detail]
+- NO parentheses in square brackets: [Text (detail)] \u2192 [Text - detail]  
 - NO complex expressions in diamonds: {a && b} \u2192 {condition}
+- NO HTML tags in node labels: [<pre>code</pre>] \u2192 ["code block"] or [Code Block]
 - USE single quotes for styles and classes: classDef highlight fill:'#ff9999'
+- CRITICAL: When using quotes in node labels, place them INSIDE the brackets: ["quoted text"], NOT [quoted text"]
 
 **Examples:**
 - \u2705 [Load Config] ["Run command"] {Valid?}
+- \u2705 ["depends_on: [generate-items]"] (correct quote placement)
+- \u2705 ["Code Block"] (clean text instead of HTML)
 - \u274C [Load (config)] [Run 'command'] {isValid('x')}
+- \u274C [depends_on: [generate-items"] (incorrect quote placement - quote ends inside bracket)
+- \u274C [<pre>depends_on: [generate-items]</pre>] (HTML tags in node labels)
 
 **Diagram Type Selection:**
 
@@ -4888,7 +4894,7 @@ Examples:
 </extract>
 
 <attempt_completion>
-<result>The configuration is loaded from src/config.js lines 15-25 which contains the database settings.</result>
+The configuration is loaded from src/config.js lines 15-25 which contains the database settings.
 </attempt_completion>
 
 # Special Case: Quick Completion
@@ -4915,7 +4921,7 @@ I need to find code related to error handling in the search module. The most app
 6. Wait for the tool execution result, which will be provided in the next message (within a <tool_result> block).
 7. Analyze the tool result and decide the next step. If more tool calls are needed, repeat steps 2-6.
 8. If the task is fully complete and all previous steps were successful, use the \`<attempt_completion>\` tool to provide the final answer. This is the ONLY way to finish the task.
-9. If you cannot proceed (e.g., missing information, invalid request), explain the issue clearly before using \`<attempt_completion>\` with an appropriate message in the \`<result>\` tag.
+9. If you cannot proceed (e.g., missing information, invalid request), use \`<attempt_completion>\` to explain the issue clearly with an appropriate message directly inside the tags.
 10. If your previous response was already correct and complete, you may use \`<attempt_complete>\` as a shorthand.
 
 Available Tools:

package/cjs/index.cjs

@@ -2040,13 +2040,19 @@ For GitHub-compatible mermaid diagrams, avoid single quotes and parentheses in n
 
 **Rules:**
 - NO single quotes in any node labels: 'text' \u2192 "text" or text
-- NO parentheses in square brackets: [Text (detail)] \u2192 [Text - detail]
+- NO parentheses in square brackets: [Text (detail)] \u2192 [Text - detail]  
 - NO complex expressions in diamonds: {a && b} \u2192 {condition}
+- NO HTML tags in node labels: [<pre>code</pre>] \u2192 ["code block"] or [Code Block]
 - USE single quotes for styles and classes: classDef highlight fill:'#ff9999'
+- CRITICAL: When using quotes in node labels, place them INSIDE the brackets: ["quoted text"], NOT [quoted text"]
 
 **Examples:**
 - \u2705 [Load Config] ["Run command"] {Valid?}
+- \u2705 ["depends_on: [generate-items]"] (correct quote placement)
+- \u2705 ["Code Block"] (clean text instead of HTML)
 - \u274C [Load (config)] [Run 'command'] {isValid('x')}
+- \u274C [depends_on: [generate-items"] (incorrect quote placement - quote ends inside bracket)
+- \u274C [<pre>depends_on: [generate-items]</pre>] (HTML tags in node labels)
 
 **Diagram Type Selection:**
 
@@ -4974,7 +4980,7 @@ Examples:
 </extract>
 
 <attempt_completion>
-<result>The configuration is loaded from src/config.js lines 15-25 which contains the database settings.</result>
+The configuration is loaded from src/config.js lines 15-25 which contains the database settings.
 </attempt_completion>
 
 # Special Case: Quick Completion
@@ -5001,7 +5007,7 @@ I need to find code related to error handling in the search module. The most app
 6. Wait for the tool execution result, which will be provided in the next message (within a <tool_result> block).
 7. Analyze the tool result and decide the next step. If more tool calls are needed, repeat steps 2-6.
 8. If the task is fully complete and all previous steps were successful, use the \`<attempt_completion>\` tool to provide the final answer. This is the ONLY way to finish the task.
-9. If you cannot proceed (e.g., missing information, invalid request), explain the issue clearly before using \`<attempt_completion>\` with an appropriate message in the \`<result>\` tag.
+9. If you cannot proceed (e.g., missing information, invalid request), use \`<attempt_completion>\` to explain the issue clearly with an appropriate message directly inside the tags.
 10. If your previous response was already correct and complete, you may use \`<attempt_complete>\` as a shorthand.
 
 Available Tools:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@probelabs/probe",
-  "version": "0.6.0-rc101",
+  "version": "0.6.0-rc102",
   "description": "Node.js wrapper for the probe code search tool",
   "main": "src/index.js",
   "module": "src/index.js",

package/src/agent/ProbeAgent.js

@@ -384,7 +384,7 @@ Examples:
 </extract>
 
 <attempt_completion>
-<result>The configuration is loaded from src/config.js lines 15-25 which contains the database settings.</result>
+The configuration is loaded from src/config.js lines 15-25 which contains the database settings.
 </attempt_completion>
 
 # Special Case: Quick Completion
@@ -411,7 +411,7 @@ I need to find code related to error handling in the search module. The most app
 6. Wait for the tool execution result, which will be provided in the next message (within a <tool_result> block).
 7. Analyze the tool result and decide the next step. If more tool calls are needed, repeat steps 2-6.
 8. If the task is fully complete and all previous steps were successful, use the \`<attempt_completion>\` tool to provide the final answer. This is the ONLY way to finish the task.
-9. If you cannot proceed (e.g., missing information, invalid request), explain the issue clearly before using \`<attempt_completion>\` with an appropriate message in the \`<result>\` tag.
+9. If you cannot proceed (e.g., missing information, invalid request), use \`<attempt_completion>\` to explain the issue clearly with an appropriate message directly inside the tags.
 10. If your previous response was already correct and complete, you may use \`<attempt_complete>\` as a shorthand.
 
 Available Tools:

package/src/agent/index.js

@@ -4,6 +4,7 @@ import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js'
 import {
   CallToolRequestSchema,
   ErrorCode,
+  InitializeRequestSchema,
   ListToolsRequestSchema,
   McpError,
 } from '@modelcontextprotocol/sdk/types.js';
@@ -255,7 +256,7 @@ class ProbeAgentMcpServer {
   constructor() {
     this.server = new Server(
       {
-        name: '@buger/probe-agent',
+        name: '@probelabs/probe agent',
         version: '1.0.0',
       },
       {
@@ -274,6 +275,20 @@ class ProbeAgentMcpServer {
   }
 
   setupToolHandlers() {
+    // Handle MCP initialize request
+    this.server.setRequestHandler(InitializeRequestSchema, async (request) => {
+      return {
+        protocolVersion: '2024-11-05',
+        capabilities: {
+          tools: {},
+        },
+        serverInfo: {
+          name: '@probelabs/probe agent',
+          version: '1.0.0',
+        },
+      };
+    });
+
     this.server.setRequestHandler(ListToolsRequestSchema, async () => ({
       tools: [
         {
@@ -763,8 +778,13 @@ async function main() {
       }
     }
 
-    // Output the result
-    console.log(result);
+    // Output the result (strip <result> tags if present for cleaner CLI output)
+    const resultMatch = result.match(/<result>([\s\S]*?)<\/result>/);
+    if (resultMatch) {
+      console.log(resultMatch[1].trim());
+    } else {
+      console.log(result);
+    }
 
     // Show token usage in verbose mode
     if (config.verbose) {
@@ -810,4 +830,4 @@ process.on('unhandledRejection', (reason, promise) => {
 main().catch((error) => {
   console.error('Fatal error:', error);
   process.exit(1);
-});
+});

package/src/mcp/index.ts

@@ -604,5 +604,5 @@ class ProbeServer {
   }
 }
 
-const server = new ProbeServer(cliConfig.timeout, cliConfig.format);
+const server = new ProbeServer(cliConfig.timeout, cliConfig.format || 'outline-xml');
 server.run().catch(console.error);

package/src/tools/system-message.js

@@ -73,13 +73,19 @@ For GitHub-compatible mermaid diagrams, avoid single quotes and parentheses in n
 
 **Rules:**
 - NO single quotes in any node labels: 'text' → "text" or text
-- NO parentheses in square brackets: [Text (detail)] → [Text - detail]
+- NO parentheses in square brackets: [Text (detail)] → [Text - detail]  
 - NO complex expressions in diamonds: {a && b} → {condition}
+- NO HTML tags in node labels: [<pre>code</pre>] → ["code block"] or [Code Block]
 - USE single quotes for styles and classes: classDef highlight fill:'#ff9999'
+- CRITICAL: When using quotes in node labels, place them INSIDE the brackets: ["quoted text"], NOT [quoted text"]
 
 **Examples:**
 - ✅ [Load Config] ["Run command"] {Valid?}
+- ✅ ["depends_on: [generate-items]"] (correct quote placement)
+- ✅ ["Code Block"] (clean text instead of HTML)
 - ❌ [Load (config)] [Run 'command'] {isValid('x')}
+- ❌ [depends_on: [generate-items"] (incorrect quote placement - quote ends inside bracket)
+- ❌ [<pre>depends_on: [generate-items]</pre>] (HTML tags in node labels)
 
 **Diagram Type Selection:**