@wonderwhy-er/desktop-commander 0.2.16 → 0.2.17

package/README.md

@@ -427,7 +427,7 @@ The server provides a comprehensive set of tools organized into several categori
 | | `read_multiple_files` | Read multiple files simultaneously |
 | | `write_file` | Write file contents with options for rewrite or append mode (uses configurable line limits) |
 | | `create_directory` | Create a new directory or ensure it exists |
-| | `list_directory` | Get detailed listing of files and directories |
+| | `list_directory` | Get detailed recursive listing of files and directories (supports depth parameter, default depth=2) |
 | | `move_file` | Move or rename files and directories |
 | | `start_search` | Start streaming search for files by name or content patterns (unified ripgrep-based search) |
 | | `get_more_search_results` | Get paginated results from active search with offset support |
@@ -436,6 +436,7 @@ The server provides a comprehensive set of tools organized into several categori
 | | `get_file_info` | Retrieve detailed metadata about a file or directory |
 | **Text Editing** | `edit_block` | Apply targeted text replacements with enhanced prompting for smaller edits (includes character-level diff feedback) |
 | **Analytics** | `get_usage_stats` | Get usage statistics for your own insight |
+| | `get_recent_tool_calls` | Get recent tool call history with arguments and outputs for debugging and context recovery |
 | | `give_feedback_to_desktop_commander` | Open feedback form in browser to provide feedback to Desktop Commander Team |
 
 ### Quick Examples

package/dist/data/spec-kit-prompts.json

@@ -0,0 +1,123 @@
+{
+  "version": "1.0.0",
+  "description": "Spec-Kit prompts for specification-driven development workflows",
+  "prompts": [
+    {
+      "id": "spec_001",
+      "title": "Initialize Spec-Kit Project",
+      "description": "Set up a new project with spec-driven development workflow including templates, scripts, and AI agent integration.",
+      "prompt": "Let's initialize a new spec-driven development project! 🎯\n\n**Project Setup Process:**\n\n1. **Check Current Environment**: I'll verify if we're already in a spec-kit project (look for `.specify` folder)\n2. **Initialize New Project**: Set up project structure with `specify init <project-name>`\n3. **Configure AI Integration**: Choose your preferred AI agent (claude, copilot, gemini, cursor, etc.)\n4. **Explain Workflow**: Show you the available slash commands and methodology\n\n**What's the name of your new project?**\n\n*Example: `my-photo-app` or `user-auth-service`*\n\nOnce initialized, you'll have access to the complete spec-driven workflow:\n• `/constitution` - Define project principles\n• `/specify` - Create feature specifications\n• `/plan` - Generate technical plans\n• `/tasks` - Break down into actionable tasks\n• `/implement` - Execute implementation\n\nReady to get started?",
+      "categories": ["spec-kit"],
+      "secondaryTag": "Setup",
+      "votes": 0,
+      "gaClicks": 0,
+      "icon": "Rocket",
+      "author": "GitHub Spec-Kit",
+      "verified": true
+    },
+    {
+      "id": "spec_002",
+      "title": "Create Project Constitution",
+      "description": "Define project principles and governance that will guide all development decisions and ensure consistency across features.",
+      "prompt": "Let's establish your project constitution - the foundational principles that will guide all development! 📜\n\n**Constitution Creation Process:**\n\n1. **Analyze Current Context**: I'll check if you already have a constitution and understand your project\n2. **Define Core Principles**: Create non-negotiable rules for your development process\n3. **Set Governance**: Establish how principles are updated and enforced\n4. **Sync Dependencies**: Ensure all templates align with your new principles\n\n**What principles should guide your project?**\n\n*Examples:*\n• Code quality standards (testing requirements, review processes)\n• User experience consistency (accessibility-first, performance targets)\n• Technical constraints (preferred frameworks, deployment requirements)\n• Security requirements (authentication standards, data protection)\n\n**Tell me about your project's core values and constraints:**\n\nI'll create a comprehensive constitution that includes:\n• Principle definitions with clear rationale\n• Amendment procedures and versioning\n• Compliance review expectations\n• Template synchronization\n\nThis becomes the foundation for all future specifications and technical decisions!",
+      "categories": ["spec-kit"],
+      "secondaryTag": "Setup",
+      "votes": 0,
+      "gaClicks": 0,
+      "icon": "BookOpen",
+      "author": "GitHub Spec-Kit",
+      "verified": true
+    },
+    {
+      "id": "spec_003",
+      "title": "Create Feature Specification",
+      "description": "Generate a comprehensive feature specification from natural language description using spec-kit methodology and templates.",
+      "prompt": "Let's create a detailed feature specification using the spec-kit methodology! 📋\n\n**Specification Process:**\n\n1. **Create Feature Branch**: I'll run the create-new-feature script to set up a new branch and spec file\n2. **Generate Comprehensive Spec**: Use the spec-kit template to create:\n   • User scenarios and testing approaches\n   • Functional requirements (testable and unambiguous)\n   • Key entities and data models\n   • Success criteria and acceptance criteria\n3. **Mark Clarifications**: Highlight any areas that need more detail with [NEEDS CLARIFICATION] markers\n4. **Review Checklist**: Validate completeness and business alignment\n\n**What feature do you want to build?**\n\n*Be as detailed as possible about WHAT and WHY, avoid HOW:*\n\n*Examples:*\n• \"User authentication system with login, logout, and password reset\"\n• \"Photo album management with drag-and-drop organization\"\n• \"Real-time chat with message history and user presence\"\n• \"Task management with projects, assignments, and Kanban boards\"\n\n**Feature Description:**\n\nI'll focus on:\n✅ What users need and why\n✅ Business requirements and user scenarios\n✅ Testable functional requirements\n❌ Technical implementation details (saved for planning phase)\n\nReady to create your specification?",
+      "categories": ["spec-kit"],
+      "secondaryTag": "Specification",
+      "votes": 0,
+      "gaClicks": 0,
+      "icon": "FileText",
+      "author": "GitHub Spec-Kit",
+      "verified": true
+    },
+    {
+      "id": "spec_004",
+      "title": "Clarify Specification Requirements",
+      "description": "Run structured clarification workflow to resolve ambiguous requirements and ensure specification completeness before planning.",
+      "prompt": "Let's clarify any ambiguous areas in your specification before moving to technical planning! 🔍\n\n**Clarification Workflow:**\n\n1. **Analyze Current Spec**: I'll read your feature specification and identify areas marked with [NEEDS CLARIFICATION]\n2. **Structured Questioning**: Ask targeted questions about:\n   • User types and permissions\n   • Data retention and deletion policies\n   • Performance targets and scale requirements\n   • Error handling behaviors\n   • Integration requirements\n3. **Document Answers**: Record all clarifications in the specification\n4. **Validate Completeness**: Ensure all requirements are testable and unambiguous\n\n**Current clarification areas in your spec:**\n\nI'll systematically work through each unclear aspect:\n• Who are the users and what are their roles?\n• What are the data and storage requirements?\n• What are the performance and scale expectations?\n• How should errors and edge cases be handled?\n• What integrations or external dependencies exist?\n\n**Ready to clarify your specification?**\n\n*This step is crucial for reducing rework during planning and implementation phases.*\n\nOnce clarified, your specification will be ready for technical planning with `/plan`!",
+      "categories": ["spec-kit"],
+      "secondaryTag": "Specification",
+      "votes": 0,
+      "gaClicks": 0,
+      "icon": "HelpCircle",
+      "author": "GitHub Spec-Kit",
+      "verified": true
+    },
+    {
+      "id": "spec_005",
+      "title": "Generate Technical Implementation Plan",
+      "description": "Create detailed technical plan from specification including architecture, tech stack, data models, and implementation strategy.",
+      "prompt": "Let's create a comprehensive technical implementation plan for your feature! 🏗️\n\n**Planning Process:**\n\n1. **Analyze Specification**: I'll read your feature spec and understand all requirements\n2. **Check Constitution**: Ensure alignment with project principles and constraints\n3. **Generate Implementation Plan**: Create detailed technical plan including:\n   • Architecture and tech stack decisions\n   • Data models based on key entities\n   • API contracts and interfaces\n   • Research for technical decisions\n   • Quickstart validation scenarios\n4. **Validate Against Gates**: Check simplicity, anti-abstraction, and constitutional compliance\n\n**What's your preferred technology approach?**\n\n*Specify your tech stack and architectural preferences:*\n\n*Examples:*\n• \"React with TypeScript, Node.js backend, PostgreSQL database\"\n• \"Vanilla HTML/CSS/JavaScript, SQLite for local storage\"\n• \"Python FastAPI, Redis for caching, Docker deployment\"\n• \"Vue.js frontend, .NET Core API, SQL Server database\"\n\n**Technical Context:**\n\nI'll generate:\n📋 **Implementation Plan** - Architecture and approach\n🗄️ **Data Model** - Entities and relationships\n🔌 **API Contracts** - Endpoints and specifications\n🔬 **Research Notes** - Technical decisions and rationale\n⚡ **Quickstart Guide** - Key validation scenarios\n\nReady to create your technical plan?",
+      "categories": ["spec-kit"],
+      "secondaryTag": "Planning",
+      "votes": 0,
+      "gaClicks": 0,
+      "icon": "Blueprint",
+      "author": "GitHub Spec-Kit",
+      "verified": true
+    },
+    {
+      "id": "spec_006",
+      "title": "Generate Implementation Tasks",
+      "description": "Break down technical plan into actionable, dependency-ordered tasks ready for execution with parallel execution markers.",
+      "prompt": "Let's break down your implementation plan into actionable tasks! ✅\n\n**Task Generation Process:**\n\n1. **Analyze Design Artifacts**: I'll read your plan.md, data-model.md, contracts/, and other design documents\n2. **Generate Task Breakdown**: Create specific tasks organized by phases:\n   • **Setup Tasks**: Project init, dependencies, configuration\n   • **Test Tasks [P]**: Contract tests, integration scenarios (parallel)\n   • **Core Tasks**: Models, services, CLI commands, endpoints\n   • **Integration Tasks**: Database, middleware, logging\n   • **Polish Tasks [P]**: Unit tests, performance, docs (parallel)\n3. **Order Dependencies**: Ensure proper execution sequence (TDD approach)\n4. **Mark Parallelization**: Identify tasks that can run simultaneously with [P]\n\n**Task Generation Rules:**\n• Each contract → test task marked [P]\n• Each entity → model creation task marked [P]\n• Each endpoint → implementation task\n• Different files = parallel [P]\n• Same files = sequential\n• Tests before implementation (TDD)\n\n**Additional context for task generation:**\n\n*Any specific requirements or preferences for the implementation approach?*\n\nI'll create a `tasks.md` file with:\n📝 **Numbered Tasks** (T001, T002, etc.)\n📁 **File Paths** for each task\n🔗 **Dependencies** clearly marked\n⚡ **Parallel Groups** for efficient execution\n\nReady to generate your implementation tasks?",
+      "categories": ["spec-kit"],
+      "secondaryTag": "Planning",
+      "votes": 0,
+      "gaClicks": 0,
+      "icon": "CheckSquare",
+      "author": "GitHub Spec-Kit",
+      "verified": true
+    },
+    {
+      "id": "spec_007",
+      "title": "Execute Feature Implementation",
+      "description": "Execute all implementation tasks following the task breakdown with TDD approach, dependency management, and progress tracking.",
+      "prompt": "Let's implement your feature following the spec-driven task breakdown! 🚀\n\n**Implementation Process:**\n\n1. **Load Implementation Context**: I'll read all your design documents:\n   • tasks.md (execution plan)\n   • plan.md (architecture and tech stack)\n   • data-model.md (entities and relationships)\n   • contracts/ (API specifications)\n   • research.md (technical decisions)\n\n2. **Execute Phase-by-Phase**:\n   • **Setup**: Project structure, dependencies, configuration\n   • **Tests**: Contract tests and integration scenarios (TDD)\n   • **Core**: Models, services, CLI commands, endpoints\n   • **Integration**: Database, middleware, logging\n   • **Polish**: Unit tests, performance, documentation\n\n3. **Follow Execution Rules**:\n   • Respect task dependencies (sequential vs parallel)\n   • Tests before implementation (TDD approach)\n   • File-based coordination (same file = sequential)\n   • Mark completed tasks with [X]\n\n4. **Progress Tracking**: Report after each completed task with validation\n\n**Implementation preferences:**\n\n*Any specific notes for the implementation (deployment targets, testing frameworks, etc.)?*\n\nI'll execute tasks systematically:\n✅ **Validate Prerequisites** - All documents ready\n📋 **Phase-by-Phase Execution** - Setup → Tests → Core → Integration → Polish\n🔄 **Real-time Progress** - Track completion and handle errors\n🎯 **Final Validation** - Ensure specs match implementation\n\nReady to build your feature?",
+      "categories": ["spec-kit"],
+      "secondaryTag": "Implementation",
+      "votes": 0,
+      "gaClicks": 0,
+      "icon": "Play",
+      "author": "GitHub Spec-Kit",
+      "verified": true
+    },
+    {
+      "id": "spec_008",
+      "title": "Analyze Spec-Kit Project Status",
+      "description": "Comprehensive analysis of current spec-kit project state including features, phases, and recommended next steps.",
+      "prompt": "Let me analyze your spec-kit project and show you the current state! 📊\n\n**Project Analysis Process:**\n\n1. **Project Structure Review**: I'll examine your `.specify` directory and validate:\n   • Templates and scripts availability\n   • Project constitution and principles\n   • Current branch and feature context\n\n2. **Feature Inventory**: Scan the `specs/` directory to identify:\n   • All features and their completion status\n   • Current phase (specification, planning, tasks, implementation)\n   • Missing or incomplete artifacts\n\n3. **Health Check**: Verify project follows spec-kit best practices:\n   • All required templates present\n   • Script permissions and functionality\n   • Git branch structure and workflow\n\n4. **Progress Assessment**: For the current feature:\n   • What phase are you in?\n   • What files exist vs. what's missing?\n   • What's the logical next step?\n\n**Current Project Overview:**\n\nI'll provide:\n📋 **Feature Status Matrix** - All features and their phases\n🎯 **Current Focus** - Active feature and next steps\n⚙️ **Configuration Health** - Templates and scripts status\n📈 **Recommendations** - Suggested workflow continuations\n\n**Any specific areas you'd like me to focus on?**\n\n*Examples: \"Focus on feature completion status\" or \"Check for any configuration issues\"*\n\nLet me give you a complete project status report!",
+      "categories": ["spec-kit"],
+      "secondaryTag": "Analysis",
+      "votes": 0,
+      "gaClicks": 0,
+      "icon": "BarChart3",
+      "author": "GitHub Spec-Kit",
+      "verified": true
+    },
+    {
+      "id": "spec_009",
+      "title": "Validate Spec-Kit Workflow Compliance",
+      "description": "Check project adherence to spec-kit methodology and constitutional requirements with recommendations for improvements.",
+      "prompt": "Let's validate your project's compliance with spec-kit methodology and constitutional requirements! ✅\n\n**Compliance Validation Process:**\n\n1. **Constitutional Compliance**: I'll check if your features align with project constitution:\n   • Principle adherence in specifications\n   • Technical decisions follow governance\n   • Implementation respects constraints\n\n2. **Methodology Validation**: Verify proper spec-kit workflow:\n   • Specifications focus on WHAT/WHY (not HOW)\n   • Technical plans follow from specifications\n   • Tasks properly break down implementation\n   • Test-driven development approach\n\n3. **Quality Assessment**: Review specification and planning quality:\n   • Requirements are testable and unambiguous\n   • No [NEEDS CLARIFICATION] markers remain\n   • Success criteria are measurable\n   • Technical decisions have clear rationale\n\n4. **Process Adherence**: Check workflow execution:\n   • Proper phase progression (spec → plan → tasks → implement)\n   • Branch management and version control\n   • Documentation completeness\n\n**Compliance Report:**\n\nI'll generate:\n📋 **Constitutional Alignment** - Principle compliance score\n🔄 **Workflow Adherence** - Methodology following assessment\n📝 **Quality Metrics** - Specification and planning quality\n⚠️ **Issue Identification** - Areas needing attention\n🎯 **Recommendations** - Specific improvement actions\n\n**Any specific compliance areas you're concerned about?**\n\nReady for a complete compliance assessment?",
+      "categories": ["spec-kit"],
+      "secondaryTag": "Analysis",
+      "votes": 0,
+      "gaClicks": 0,
+      "icon": "Shield",
+      "author": "GitHub Spec-Kit",
+      "verified": true
+    }
+  ]
+}

package/dist/handlers/filesystem-handlers.js

@@ -166,10 +166,13 @@ export async function handleCreateDirectory(args) {
  */
 export async function handleListDirectory(args) {
     try {
+        const startTime = Date.now();
         const parsed = ListDirectoryArgsSchema.parse(args);
-        const entries = await listDirectory(parsed.path);
+        const entries = await listDirectory(parsed.path, parsed.depth);
+        const duration = Date.now() - startTime;
+        const resultText = entries.join('\n');
         return {
-            content: [{ type: "text", text: entries.join('\n') }],
+            content: [{ type: "text", text: resultText }],
         };
     }
     catch (error) {

package/dist/handlers/history-handlers.d.ts

@@ -0,0 +1,5 @@
+import { ServerResult } from '../types.js';
+/**
+ * Handle get_recent_tool_calls command
+ */
+export declare function handleGetRecentToolCalls(args: unknown): Promise<ServerResult>;

package/dist/handlers/history-handlers.js

@@ -0,0 +1,35 @@
+import { toolHistory } from '../utils/toolHistory.js';
+import { GetRecentToolCallsArgsSchema } from '../tools/schemas.js';
+/**
+ * Handle get_recent_tool_calls command
+ */
+export async function handleGetRecentToolCalls(args) {
+    try {
+        const parsed = GetRecentToolCallsArgsSchema.parse(args);
+        // Use formatted version with local timezone
+        const calls = toolHistory.getRecentCallsFormatted({
+            maxResults: parsed.maxResults,
+            toolName: parsed.toolName,
+            since: parsed.since
+        });
+        const stats = toolHistory.getStats();
+        // Format the response (excluding file path per user request)
+        const summary = `Tool Call History (${calls.length} results, ${stats.totalEntries} total in memory)`;
+        const historyJson = JSON.stringify(calls, null, 2);
+        return {
+            content: [{
+                    type: "text",
+                    text: `${summary}\n\n${historyJson}`
+                }]
+        };
+    }
+    catch (error) {
+        return {
+            content: [{
+                    type: "text",
+                    text: `Error getting tool history: ${error instanceof Error ? error.message : String(error)}`
+                }],
+            isError: true
+        };
+    }
+}

package/dist/handlers/index.d.ts

@@ -3,3 +3,4 @@ export * from './terminal-handlers.js';
 export * from './process-handlers.js';
 export * from './edit-search-handlers.js';
 export * from './search-handlers.js';
+export * from './history-handlers.js';

package/dist/handlers/index.js

@@ -4,3 +4,4 @@ export * from './terminal-handlers.js';
 export * from './process-handlers.js';
 export * from './edit-search-handlers.js';
 export * from './search-handlers.js';
+export * from './history-handlers.js';

package/dist/http-index.d.ts

@@ -0,0 +1,45 @@
+#!/usr/bin/env node
+/**
+ * HTTP Server Entry Point for Desktop Commander
+ *
+ * This file is used by Smithery CLI to create a Streamable HTTP server.
+ * For local stdio usage, see src/index.ts
+ *
+ * This is a thin wrapper that:
+ * 1. Applies configuration from Smithery
+ * 2. Returns the existing MCP server for HTTP transport
+ */
+interface ServerConfig {
+    config?: {
+        allowedDirectories?: string[];
+        blockedCommands?: string[];
+        defaultShell?: string;
+        fileReadLineLimit?: number;
+        fileWriteLineLimit?: number;
+        telemetryEnabled?: boolean;
+    };
+}
+export default function createServer({ config }?: ServerConfig): Promise<import("@modelcontextprotocol/sdk/server").Server<{
+    method: string;
+    params?: {
+        [x: string]: unknown;
+        _meta?: {
+            [x: string]: unknown;
+            progressToken?: string | number | undefined;
+        } | undefined;
+    } | undefined;
+}, {
+    method: string;
+    params?: {
+        [x: string]: unknown;
+        _meta?: {
+            [x: string]: unknown;
+        } | undefined;
+    } | undefined;
+}, {
+    [x: string]: unknown;
+    _meta?: {
+        [x: string]: unknown;
+    } | undefined;
+}>>;
+export {};

package/dist/http-index.js

@@ -0,0 +1,51 @@
+#!/usr/bin/env node
+/**
+ * HTTP Server Entry Point for Desktop Commander
+ *
+ * This file is used by Smithery CLI to create a Streamable HTTP server.
+ * For local stdio usage, see src/index.ts
+ *
+ * This is a thin wrapper that:
+ * 1. Applies configuration from Smithery
+ * 2. Returns the existing MCP server for HTTP transport
+ */
+import { server } from './server.js';
+import { configManager } from './config-manager.js';
+import { logToStderr } from './utils/logger.js';
+export default async function createServer({ config } = {}) {
+    logToStderr('info', '🌐 Starting Desktop Commander HTTP Server...');
+    // Apply configuration if provided
+    if (config) {
+        try {
+            logToStderr('info', 'Applying HTTP server configuration...');
+            if (config.allowedDirectories !== undefined) {
+                await configManager.setValue('allowedDirectories', config.allowedDirectories);
+            }
+            if (config.blockedCommands !== undefined) {
+                await configManager.setValue('blockedCommands', config.blockedCommands);
+            }
+            if (config.defaultShell !== undefined) {
+                await configManager.setValue('defaultShell', config.defaultShell);
+            }
+            if (config.fileReadLineLimit !== undefined) {
+                await configManager.setValue('fileReadLineLimit', config.fileReadLineLimit);
+            }
+            if (config.fileWriteLineLimit !== undefined) {
+                await configManager.setValue('fileWriteLineLimit', config.fileWriteLineLimit);
+            }
+            if (config.telemetryEnabled !== undefined) {
+                await configManager.setValue('telemetryEnabled', config.telemetryEnabled);
+            }
+            logToStderr('info', '✅ HTTP server configuration applied successfully');
+        }
+        catch (error) {
+            logToStderr('error', `Failed to apply configuration: ${error instanceof Error ? error.message : String(error)}`);
+        }
+    }
+    else {
+        logToStderr('info', 'No configuration provided, using defaults');
+    }
+    logToStderr('info', '✅ Desktop Commander HTTP Server ready');
+    // Return the existing server instance - it already has all tools registered
+    return server;
+}