Release v1.4.1

• CLI client installation is now better documented in the README
• autoApprove parameter is now better documented in the README
• autoApprove parameter is now true by default
• Tool now provides the approval command to the LLM so the LLM can provide it to the user

Package published to npm: 1.4.1

Release v1.4.0

• Simplify error handling throughout the application, properly separating MCP errors from tool execution errors per the MCP spec
• Switch to exclusively integration tests for better robustness against LLM agents breaking module integration
• Massive AI slop reduction

Package published to npm: 1.4.0

Release v1.3.4

• Use GEMINI_API_KEY instead of GOOGLE_API_KEY

Package published to npm: 1.3.4

Release v1.3.3

• Change GOOGLE_GENERATIVE_API_KEY to GOOGLE_API_KEY

Package published to npm: 1.3.3

Release v1.3.2

• Return full task details from read_task and get_next_task tools

Package published to npm: 1.3.2

Release v1.3.1

The MCP Server now exposes correct instructions on how to use the "attachments" parameter when calling the "generate_project_plan" tool

Package published to npm: 1.3.1

Release v1.3.0

• Refactor to correctly read file attachments in TaskManager when generating a project plan
• Correctly propagate informative error messages
• Greatly improve output formatting
• Change the name of the CLI entrypoint to 'taskqueue'

Package published to npm: 1.3.0

Release v1.2.0

• New tool and CLI command to generate plans with an LLM
• TaskManager refactor to reduce module length
• Commit cursor rules
• Fixed entrypoints in package.json

Package published to npm: 1.2.0

Release v1.1.2

• Remove redundant tool schemas
• Make direct use of TaskManager methods in src/client/cli.ts
• Improve README readability and document how to synchronize custom file path across CLI and server
• New file_path argument in the CLI adds another synchronization method

Package published to npm: 1.1.2

Release v1.1.1

Summary

Refactored tool execution in the Task Manager using the Command Pattern to improve maintainability, testability, and compliance with SOLID principles.

Key Changes

• Created a ToolExecutor interface defining a contract for all tool executors
• Implemented dedicated tool executor classes for each Task Manager operation
• Centralized error handling and response formatting
• Added consistent parameter validation across all tools
• Updated tool definitions with improved documentation

Benefits

• Better separation of concerns - each tool executor has a single responsibility
• Improved testability - tool executors are individually testable
• Enhanced maintainability - adding new tools requires less boilerplate
• Consistent error handling - standardized messages and validation
• Better developer experience - tool definitions now include references to their executors

Technical Details

• Implemented utility functions for common validation tasks
• Updated all tool executors to use standardized response formatting
• All tools now properly validate required parameters
• JSDoc documentation added to improve code comprehension

Package published to npm: 1.1.1