ros/claude-task-master
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
91b9f11c036296556afefee0c31511b8a1ad3787
claude-task-master/CHANGELOG.md
github-actions[bot] 36fe838fd5 Version Packages
2025-06-20 16:10:52 +03:00

98 KiB
Raw Blame History

task-master-ai

0.17.1

Patch Changes

  • #789 8cde6c2 Thanks @Crunchyman-ralph! - Fix contextGatherer bug when adding a task Cannot read properties of undefined (reading 'forEach')

0.17.0

Minor Changes

  • #779 c0b3f43 Thanks @eyaltoledano! - Add comprehensive AI-powered research command with intelligent context gathering and interactive follow-ups.

    The new research command provides AI-powered research capabilities that automatically gather relevant project context to answer your questions. The command intelligently selects context from multiple sources and supports interactive follow-up questions in CLI mode.

    Key Features:

    • Intelligent Task Discovery: Automatically finds relevant tasks and subtasks using fuzzy search based on your query keywords, supplementing any explicitly provided task IDs
    • Multi-Source Context: Gathers context from tasks, files, project structure, and custom text to provide comprehensive answers
    • Interactive Follow-ups: CLI users can ask follow-up questions that build on the conversation history while allowing fresh context discovery for each question
    • Flexible Detail Levels: Choose from low (concise), medium (balanced), or high (comprehensive) response detail levels
    • Token Transparency: Displays detailed token breakdown showing context size, sources, and estimated costs
    • Enhanced Display: Syntax-highlighted code blocks and structured output with clear visual separation

    Usage Examples:

    # Basic research with auto-discovered context
task-master research "How should I implement user authentication?"

# Research with specific task context
task-master research "What's the best approach for this?" --id=15,23.2

# Research with file context and project tree
task-master research "How does the current auth system work?" --files=src/auth.js,config/auth.json --tree

# Research with custom context and low detail
task-master research "Quick implementation steps?" --context="Using JWT tokens" --detail=low

    Context Sources:

    • Tasks: Automatically discovers relevant tasks/subtasks via fuzzy search, plus any explicitly specified via --id
    • Files: Include specific files via --files for code-aware responses
    • Project Tree: Add --tree to include project structure overview
    • Custom Context: Provide additional context via --context for domain-specific information

    Interactive Features (CLI only):

    • Follow-up questions that maintain conversation history
    • Fresh fuzzy search for each follow-up to discover newly relevant tasks
    • Cumulative context building across the conversation
    • Clean visual separation between exchanges
    • Save to Tasks: Save entire research conversations (including follow-ups) directly to task or subtask details with timestamps
    • Clean Menu Interface: Streamlined inquirer-based menu for follow-up actions without redundant UI elements

    Save Functionality:

    The research command now supports saving complete conversation threads to tasks or subtasks:

    • Save research results and follow-up conversations to any task (e.g., "15") or subtask (e.g., "15.2")
    • Automatic timestamping and formatting of conversation history
    • Validation of task/subtask existence before saving
    • Appends to existing task details without overwriting content
    • Supports both CLI interactive mode and MCP programmatic access via --save-to flag

    Enhanced CLI Options:

    # Auto-save research results to a task
task-master research "Implementation approach?" --save-to=15

# Combine auto-save with context gathering
task-master research "How to optimize this?" --id=23 --save-to=23.1

    MCP Integration:

    • saveTo parameter for automatic saving to specified task/subtask ID
    • Structured response format with telemetry data
    • Silent operation mode for programmatic usage
    • Full feature parity with CLI except interactive follow-ups

    The research command integrates with the existing AI service layer and supports all configured AI providers. Both CLI and MCP interfaces provide comprehensive research capabilities with intelligent context gathering and flexible output options.

  • #779 c0b3f43 Thanks @eyaltoledano! - Enhance update-task with --append flag for timestamped task updates

    Adds the --append flag to update-task command, enabling it to behave like update-subtask with timestamped information appending. This provides more flexible task updating options:

    CLI Enhancement:

    • task-master update-task --id=5 --prompt="New info" - Full task update (existing behavior)
    • task-master update-task --id=5 --append --prompt="Progress update" - Append timestamped info to task details

    Full MCP Integration:

    • MCP tool update_task now supports append parameter
    • Seamless integration with Cursor and other MCP clients
    • Consistent behavior between CLI and MCP interfaces

    Instead of requiring separate subtask creation for progress tracking, you can now append timestamped information directly to parent tasks while preserving the option for comprehensive task updates.

  • #779 c0b3f43 Thanks @eyaltoledano! - Add --tag flag support to core commands for multi-context task management. Commands like parse-prd, analyze-complexity, and others now support targeting specific task lists, enabling rapid prototyping and parallel development workflows.

    Key features:

    • parse-prd --tag=feature-name: Parse PRDs into separate task contexts on the fly
    • analyze-complexity --tag=branch: Generate tag-specific complexity reports
    • All task operations can target specific contexts while preserving other lists
    • Non-existent tags are created automatically for seamless workflow

  • #779 c0b3f43 Thanks @eyaltoledano! - Introduces Tagged Lists: AI Multi-Context Task Management System

    This major feature release introduces Tagged Lists, a comprehensive system that transforms Taskmaster into a multi-context task management powerhouse. You can now organize tasks into completely isolated contexts, enabling parallel (agentic) development workflows, team collaboration, and project experimentation without conflicts.

    🏷️ Tagged Task Lists Architecture:

    The new tagged system fundamentally improves how tasks are organized:

    • Legacy Format: { "tasks": [...] }
    • New Tagged Format: { "master": { "tasks": [...], "metadata": {...} }, "feature-xyz": { "tasks": [...], "metadata": {...} } }
    • Automatic Migration: Existing projects will seamlessly migrate to tagged format with zero user intervention
    • State Management: New .taskmaster/state.json tracks current tag, last switched time, migration status and more.
    • Configuration Integration: Enhanced .taskmaster/config.json with tag-specific settings and defaults.

    By default, your existing task list will be migrated to the master tag.

    🚀 Complete Tag Management Suite:

    Core Tag Commands:

    • task-master tags [--show-metadata] - List all tags with task counts, completion stats, and metadata
    • task-master add-tag <name> [options] - Create new tag contexts with optional task copying
    • task-master delete-tag <name> [--yes] - Delete tags (and attached tasks) with double confirmation protection
    • task-master use-tag <name> - Switch contexts and immediately see next available task
    • task-master rename-tag <old> <new> - Rename tags with automatic current tag reference updates
    • task-master copy-tag <source> <target> [options] - Duplicate tag contexts for experimentation

    🤖 Full MCP Integration for Tag Management:

    Task Master's multi-context capabilities are now fully exposed through the MCP server, enabling powerful agentic workflows:

    • list_tags: List all available tag contexts.
    • add_tag: Programmatically create new tags.
    • delete_tag: Remove tag contexts.
    • use_tag: Switch the agent's active task context.
    • rename_tag: Rename existing tags.
    • copy_tag: Duplicate entire task contexts for experimentation.

    Tag Creation Options:

    • --copy-from-current - Copy tasks from currently active tag
    • --copy-from=<tag> - Copy tasks from specific tag
    • --from-branch - Creates a new tag using the active git branch name (for add-tag only)
    • --description="<text>" - Add custom tag descriptions
    • Empty tag creation for fresh contexts

    🎯 Universal --tag Flag Support:

    Every task operation now supports tag-specific execution:

    • task-master list --tag=feature-branch - View tasks in specific context
    • task-master add-task --tag=experiment --prompt="..." - Create tasks in specific tag
    • task-master parse-prd document.txt --tag=v2-redesign - Parse PRDs into dedicated contexts
    • task-master analyze-complexity --tag=performance-work - Generate tag-specific reports
    • task-master set-status --tag=hotfix --id=5 --status=done - Update tasks in specific contexts
    • task-master expand --tag=research --id=3 - Break down tasks within tag contexts

    This way you or your agent can store out of context tasks into the appropriate tags for later, allowing you to maintain a groomed and scoped master list. Focus on value, not chores.

    📊 Enhanced Workflow Features:

    Smart Context Switching:

    • use-tag command shows immediate next task after switching
    • Automatic tag creation when targeting non-existent tags
    • Current tag persistence across terminal sessions
    • Branch-tag mapping for future Git integration

    Intelligent File Management:

    • Tag-specific complexity reports: task-complexity-report_tagname.json
    • Master tag uses default filenames: task-complexity-report.json
    • Automatic file isolation prevents cross-tag contamination

    Advanced Confirmation Logic:

    • Commands only prompt when target tag has existing tasks
    • Empty tags allow immediate operations without confirmation
    • Smart append vs overwrite detection

    🔄 Seamless Migration & Compatibility:

    Zero-Disruption Migration:

    • Existing tasks.json files automatically migrate on first command
    • Master tag receives proper metadata (creation date, description)
    • Migration notice shown once with helpful explanation
    • All existing commands work identically to before

    State Management:

    • .taskmaster/state.json tracks current tag and migration status
    • Automatic state creation and maintenance
    • Branch-tag mapping foundation for Git integration
    • Migration notice tracking to avoid repeated notifications
    • Grounds for future context additions

    Backward Compatibility:

    • All existing workflows continue unchanged
    • Legacy commands work exactly as before
    • Gradual adoption - users can ignore tags entirely if desired
    • No breaking changes to existing tasks or file formats

    💡 Real-World Use Cases:

    Team Collaboration:

    • task-master add-tag alice --copy-from-current - Create teammate-specific contexts
    • task-master add-tag bob --copy-from=master - Onboard new team members
    • task-master use-tag alice - Switch to teammate's work context

    Feature Development:

    • task-master parse-prd feature-spec.txt --tag=user-auth - Dedicated feature planning
    • task-master add-tag experiment --copy-from=user-auth - Safe experimentation
    • task-master analyze-complexity --tag=user-auth - Feature-specific analysis

    Release Management:

    • task-master add-tag v2.0 --description="Next major release" - Version-specific planning
    • task-master copy-tag master v2.1 - Release branch preparation
    • task-master use-tag hotfix - Emergency fix context

    Project Phases:

    • task-master add-tag research --description="Discovery phase" - Research tasks
    • task-master add-tag implementation --copy-from=research - Development phase
    • task-master add-tag testing --copy-from=implementation - QA phase

    🛠️ Technical Implementation:

    Data Structure:

    • Tagged format with complete isolation between contexts
    • Rich metadata per tag (creation date, description, update tracking)
    • Automatic metadata enhancement for existing tags
    • Clean separation of tag data and internal state

    Performance Optimizations:

    • Dynamic task counting without stored counters
    • Efficient tag resolution and caching
    • Minimal file I/O with smart data loading
    • Responsive table layouts adapting to terminal width

    Error Handling:

    • Comprehensive validation for tag names (alphanumeric, hyphens, underscores)
    • Reserved name protection (master, main, default)
    • Graceful handling of missing tags and corrupted data
    • Detailed error messages with suggested corrections

    This release establishes the foundation for advanced multi-context workflows while maintaining the simplicity and power that makes Task Master effective for individual developers.

  • #779 c0b3f43 Thanks @eyaltoledano! - Research Save-to-File Feature & Critical MCP Tag Corruption Fix

    🔬 New Research Save-to-File Functionality:

    Added comprehensive save-to-file capability to the research command, enabling users to preserve research sessions for future reference and documentation.

    CLI Integration:

    • New --save-file flag for task-master research command
    • Consistent with existing --save and --save-to flags for intuitive usage
    • Interactive "Save to file" option in follow-up questions menu

    MCP Integration:

    • New saveToFile boolean parameter for the research MCP tool
    • Enables programmatic research saving for AI agents and integrated tools

    File Management:

    • Automatically creates .taskmaster/docs/research/ directory structure
    • Generates timestamped, slugified filenames (e.g., 2025-01-13_what-is-typescript.md)
    • Comprehensive Markdown format with metadata headers including query, timestamp, and context sources
    • Clean conversation history formatting without duplicate information

  • #779 c0b3f43 Thanks @eyaltoledano! - No longer automatically creates individual task files as they are not used by the applicatoin. You can still generate them anytime using the generate command.

  • #779 c0b3f43 Thanks @eyaltoledano! - Enhanced get-task/show command to support comma-separated task IDs for efficient batch operations

    New Features:

    • Multiple Task Retrieval: Pass comma-separated IDs to get/show multiple tasks at once (e.g., task-master show 1,3,5 or MCP get_task with id: "1,3,5")
    • Smart Display Logic: Single ID shows detailed view, multiple IDs show compact summary table with interactive options
    • Batch Action Menu: Interactive menu for multiple tasks with copy-paste ready commands for common operations (mark as done/in-progress, expand all, view dependencies, etc.)
    • MCP Array Response: MCP tool returns structured array of task objects for efficient AI agent context gathering

    Benefits:

    • Faster Context Gathering: AI agents can collect multiple tasks/subtasks in one call instead of iterating
    • Improved Workflow: Interactive batch operations reduce repetitive command execution
    • Better UX: Responsive layout adapts to terminal width, maintains consistency with existing UI patterns
    • API Efficiency: RESTful array responses in MCP format enable more sophisticated integrations

    This enhancement maintains full backward compatibility while significantly improving efficiency for both human users and AI agents working with multiple tasks.

  • #779 c0b3f43 Thanks @eyaltoledano! - Adds support for filtering tasks by multiple statuses at once using comma-separated statuses.

    Example: cancelled,deferred

  • #779 c0b3f43 Thanks @eyaltoledano! - Adds tag to CLI and MCP outputs/responses so you know which tag you are performing operations on.

Patch Changes

  • #779 5ec1f61 Thanks @eyaltoledano! - Fix Cursor deeplink installation by providing copy-paste instructions for GitHub compatibility

  • #779 c0b3f43 Thanks @eyaltoledano! - Fix critical bugs in task move functionality:

    • Fixed moving tasks to become subtasks of empty parents: When moving a task to become a subtask of a parent that had no existing subtasks (e.g., task 89 → task 98.1), the operation would fail with validation errors.
    • Fixed moving subtasks between parents: Subtasks can now be properly moved between different parent tasks, including to parents that previously had no subtasks.
    • Improved comma-separated batch moves: Multiple tasks can now be moved simultaneously using comma-separated IDs (e.g., "88,90" → "92,93") with proper error handling and atomic operations.

    These fixes enables proper task hierarchy reorganization for corner cases that were previously broken.

  • #779 d76bea4 Thanks @eyaltoledano! - Update o3 model price

  • #779 0849c0c Thanks @eyaltoledano! - Fixes issue with expand CLI command "Complexity report not found"

    • Closes #735
    • Closes #728

  • #779 c0b3f43 Thanks @eyaltoledano! - Fix issue with generate command which was creating tasks in the legacy tasks location.

    - No longer creates individual task files automatically. You can still use `generate` if you need to create our update your task files.

  • #779 c0b3f43 Thanks @eyaltoledano! - Improves dependency management when moving tasks by updating subtask dependencies that reference sibling subtasks by their old parent-based ID

  • Updated dependencies [c0b3f43, 5ec1f61, c0b3f43, c0b3f43, d76bea4, c0b3f43, 0849c0c, c0b3f43, c0b3f43, c0b3f43, c0b3f43, c0b3f43, c0b3f43, c0b3f43, c0b3f43]:

0.16.2

Patch Changes

  • #695 1ece6f1 Thanks @Crunchyman-ralph! - improve findTasks algorithm for resolving tasks path

  • #695 ee0be04 Thanks @Crunchyman-ralph! - Fix update tool on MCP giving No valid tasks found

  • #699 27edbd8 Thanks @eyaltoledano! - Enhanced add-task fuzzy search intelligence and improved user experience

    Smarter Task Discovery:

    • Remove hardcoded category system that always matched "Task management"
    • Eliminate arbitrary limits on fuzzy search results (5→25 high relevance, 3→10 medium relevance, 8→20 detailed tasks)
    • Improve semantic weighting in Fuse.js search (details=3, description=2, title=1.5) for better relevance
    • Generate context-driven task recommendations based on true semantic similarity

    Enhanced Terminal Experience:

    • Fix duplicate banner display issue that was "eating" terminal history (closes #553)
    • Remove console.clear() and redundant displayBanner() calls from UI functions
    • Preserve command history for better development workflow
    • Streamline banner display across all commands (list, next, show, set-status, clear-subtasks, dependency commands)

    Visual Improvements:

    • Replace emoji complexity indicators with clean filled circle characters (●) for professional appearance
    • Improve consistency and readability of task complexity display

    AI Provider Compatibility:

    • Change generateObject mode from 'tool' to 'auto' for better cross-provider compatibility
    • Add qwen3-235n-a22b:free model support (closes #687)
    • Add smart warnings for free OpenRouter models with limitations (rate limits, restricted context, no tool_use)

    Technical Improvements:

    • Enhanced context generation in add-task to rely on semantic similarity rather than rigid pattern matching
    • Improved dependency analysis and common pattern detection
    • Better handling of task relationships and relevance scoring
    • More intelligent task suggestion algorithms

    The add-task system now provides truly relevant task context based on semantic understanding rather than arbitrary categories and limits, while maintaining a cleaner and more professional terminal experience.

  • #655 edaa5fe Thanks @Crunchyman-ralph! - Fix double .taskmaster directory paths in file resolution utilities

    • Closes #636

  • #671 86ea6d1 Thanks @joedanz! - Add one-click MCP server installation for Cursor

  • #699 2e55757 Thanks @eyaltoledano! - Add sync-readme command for a task export to GitHub README

    Introduces a new sync-readme command that exports your task list to your project's README.md file.

    Features:

    • Flexible filtering: Supports --status filtering (e.g., pending, done) and --with-subtasks flag
    • Smart content management: Automatically replaces existing exports or appends to new READMEs
    • Metadata display: Shows export timestamp, subtask inclusion status, and filter settings

    Usage:

    • task-master sync-readme - Export tasks without subtasks
    • task-master sync-readme --with-subtasks - Include subtasks in export
    • task-master sync-readme --status=pending - Only export pending tasks
    • task-master sync-readme --status=done --with-subtasks - Export completed tasks with subtasks

    Perfect for showcasing project progress on GitHub. Experimental. Open to feedback.

0.16.2

Patch Changes

  • #695 1ece6f1 Thanks @Crunchyman-ralph! - improve findTasks algorithm for resolving tasks path

  • #695 ee0be04 Thanks @Crunchyman-ralph! - Fix update tool on MCP giving No valid tasks found

  • #699 27edbd8 Thanks @eyaltoledano! - Enhanced add-task fuzzy search intelligence and improved user experience

    Smarter Task Discovery:

    • Remove hardcoded category system that always matched "Task management"
    • Eliminate arbitrary limits on fuzzy search results (5→25 high relevance, 3→10 medium relevance, 8→20 detailed tasks)
    • Improve semantic weighting in Fuse.js search (details=3, description=2, title=1.5) for better relevance
    • Generate context-driven task recommendations based on true semantic similarity

    Enhanced Terminal Experience:

    • Fix duplicate banner display issue that was "eating" terminal history (closes #553)
    • Remove console.clear() and redundant displayBanner() calls from UI functions
    • Preserve command history for better development workflow
    • Streamline banner display across all commands (list, next, show, set-status, clear-subtasks, dependency commands)

    Visual Improvements:

    • Replace emoji complexity indicators with clean filled circle characters (●) for professional appearance
    • Improve consistency and readability of task complexity display

    AI Provider Compatibility:

    • Change generateObject mode from 'tool' to 'auto' for better cross-provider compatibility
    • Add qwen3-235n-a22b:free model support (closes #687)
    • Add smart warnings for free OpenRouter models with limitations (rate limits, restricted context, no tool_use)

    Technical Improvements:

    • Enhanced context generation in add-task to rely on semantic similarity rather than rigid pattern matching
    • Improved dependency analysis and common pattern detection
    • Better handling of task relationships and relevance scoring
    • More intelligent task suggestion algorithms

    The add-task system now provides truly relevant task context based on semantic understanding rather than arbitrary categories and limits, while maintaining a cleaner and more professional terminal experience.

  • #655 edaa5fe Thanks @Crunchyman-ralph! - Fix double .taskmaster directory paths in file resolution utilities

    • Closes #636

  • #671 86ea6d1 Thanks @joedanz! - Add one-click MCP server installation for Cursor

  • #699 2e55757 Thanks @eyaltoledano! - Add sync-readme command for a task export to GitHub README

    Introduces a new sync-readme command that exports your task list to your project's README.md file.

    Features:

    • Flexible filtering: Supports --status filtering (e.g., pending, done) and --with-subtasks flag
    • Smart content management: Automatically replaces existing exports or appends to new READMEs
    • Metadata display: Shows export timestamp, subtask inclusion status, and filter settings

    Usage:

    • task-master sync-readme - Export tasks without subtasks
    • task-master sync-readme --with-subtasks - Include subtasks in export
    • task-master sync-readme --status=pending - Only export pending tasks
    • task-master sync-readme --status=done --with-subtasks - Export completed tasks with subtasks

    Perfect for showcasing project progress on GitHub. Experimental. Open to feedback.

0.16.2-rc.0

Patch Changes

0.16.1

Patch Changes

0.16.0

Minor Changes

  • #607 6a8a68e Thanks @Crunchyman-ralph! - Add AWS bedrock support

  • #607 6a8a68e Thanks @Crunchyman-ralph! - # Add Google Vertex AI Provider Integration

    • Implemented VertexAIProvider class extending BaseAIProvider
    • Added authentication and configuration handling for Vertex AI
    • Updated configuration manager with Vertex-specific getters
    • Modified AI services unified system to integrate the provider
    • Added documentation for Vertex AI setup and configuration
    • Updated environment variable examples for Vertex AI support
    • Implemented specialized error handling for Vertex-specific issues

  • #607 6a8a68e Thanks @Crunchyman-ralph! - Add support for Azure

  • #612 669b744 Thanks @Crunchyman-ralph! - Increased minimum required node version to > 18 (was > 14)

  • #607 6a8a68e Thanks @Crunchyman-ralph! - Renamed baseUrl to baseURL

  • #604 80735f9 Thanks @Crunchyman-ralph! - Add TASK_MASTER_PROJECT_ROOT env variable supported in mcp.json and .env for project root resolution

    • Some users were having issues where the MCP wasn't able to detect the location of their project root, you can now set the TASK_MASTER_PROJECT_ROOT environment variable to the root of your project.

  • #619 3f64202 Thanks @Crunchyman-ralph! - Consolidate Task Master files into unified .taskmaster directory structure

    This release introduces a new consolidated directory structure that organizes all Task Master files under a single .taskmaster/ directory for better project organization and cleaner workspace management.

    New Directory Structure:

    • .taskmaster/tasks/ - Task files (previously tasks/)
    • .taskmaster/docs/ - Documentation including PRD files (previously scripts/)
    • .taskmaster/reports/ - Complexity analysis reports (previously scripts/)
    • .taskmaster/templates/ - Template files like example PRD
    • .taskmaster/config.json - Configuration (previously .taskmasterconfig)

    Migration & Backward Compatibility:

    • Existing projects continue to work with legacy file locations
    • New projects use the consolidated structure automatically
    • Run task-master migrate to move existing projects to the new structure
    • All CLI commands and MCP tools automatically detect and use appropriate file locations

    Benefits:

    • Cleaner project root with Task Master files organized in one location
    • Reduced file scatter across multiple directories
    • Improved project navigation and maintenance
    • Consistent file organization across all Task Master projects

    This change maintains full backward compatibility while providing a migration path to the improved structure.

Patch Changes

0.16.0-rc.0

Minor Changes

  • #607 6a8a68e Thanks @Crunchyman-ralph! - Add AWS bedrock support

  • #607 6a8a68e Thanks @Crunchyman-ralph! - # Add Google Vertex AI Provider Integration

    • Implemented VertexAIProvider class extending BaseAIProvider
    • Added authentication and configuration handling for Vertex AI
    • Updated configuration manager with Vertex-specific getters
    • Modified AI services unified system to integrate the provider
    • Added documentation for Vertex AI setup and configuration
    • Updated environment variable examples for Vertex AI support
    • Implemented specialized error handling for Vertex-specific issues

  • #607 6a8a68e Thanks @Crunchyman-ralph! - Add support for Azure

  • #612 669b744 Thanks @Crunchyman-ralph! - Increased minimum required node version to > 18 (was > 14)

  • #607 6a8a68e Thanks @Crunchyman-ralph! - Renamed baseUrl to baseURL

  • #604 80735f9 Thanks @Crunchyman-ralph! - Add TASK_MASTER_PROJECT_ROOT env variable supported in mcp.json and .env for project root resolution

    • Some users were having issues where the MCP wasn't able to detect the location of their project root, you can now set the TASK_MASTER_PROJECT_ROOT environment variable to the root of your project.

  • #619 3f64202 Thanks @Crunchyman-ralph! - Consolidate Task Master files into unified .taskmaster directory structure

    This release introduces a new consolidated directory structure that organizes all Task Master files under a single .taskmaster/ directory for better project organization and cleaner workspace management.

    New Directory Structure:

    • .taskmaster/tasks/ - Task files (previously tasks/)
    • .taskmaster/docs/ - Documentation including PRD files (previously scripts/)
    • .taskmaster/reports/ - Complexity analysis reports (previously scripts/)
    • .taskmaster/templates/ - Template files like example PRD
    • .taskmaster/config.json - Configuration (previously .taskmasterconfig)

    Migration & Backward Compatibility:

    • Existing projects continue to work with legacy file locations
    • New projects use the consolidated structure automatically
    • Run task-master migrate to move existing projects to the new structure
    • All CLI commands and MCP tools automatically detect and use appropriate file locations

    Benefits:

    • Cleaner project root with Task Master files organized in one location
    • Reduced file scatter across multiple directories
    • Improved project navigation and maintenance
    • Consistent file organization across all Task Master projects

    This change maintains full backward compatibility while providing a migration path to the improved structure.

Patch Changes

0.15.0

Minor Changes

  • #567 09add37 Thanks @eyaltoledano! - Added comprehensive Ollama model validation and interactive setup support

    • Interactive Setup Enhancement: Added "Custom Ollama model" option to task-master models --setup, matching the existing OpenRouter functionality
    • Live Model Validation: When setting Ollama models, Taskmaster now validates against the local Ollama instance by querying /api/tags endpoint
    • Configurable Endpoints: Uses the ollamaBaseUrl from .taskmasterconfig (with role-specific baseUrl overrides supported)
    • Robust Error Handling:
      • Detects when Ollama server is not running and provides clear error messages
      • Validates model existence and lists available alternatives when model not found
      • Graceful fallback behavior for connection issues
    • Full Platform Support: Both MCP server tools and CLI commands support the new validation
    • Improved User Experience: Clear feedback during model validation with informative success/error messages

  • #567 4c83526 Thanks @eyaltoledano! - Adds and updates supported AI models with costs:

    • Added new OpenRouter models: GPT-4.1 series, O3, Codex Mini, Llama 4 Maverick, Llama 4 Scout, Qwen3-235b
    • Added Mistral models: Devstral Small, Mistral Nemo
    • Updated Ollama models with latest variants: Devstral, Qwen3, Mistral-small3.1, Llama3.3
    • Updated Gemini model to latest 2.5 Flash preview version

  • #567 70f4054 Thanks @eyaltoledano! - Add --research flag to parse-prd command, enabling enhanced task generation from PRD files. When used, Taskmaster leverages the research model to:

    • Research current technologies and best practices relevant to the project
    • Identify technical challenges and security concerns not explicitly mentioned in the PRD
    • Include specific library recommendations with version numbers
    • Provide more detailed implementation guidance based on industry standards
    • Create more accurate dependency relationships between tasks

    This results in higher quality, more actionable tasks with minimal additional effort.

    NOTE That this is an experimental feature. Research models don't typically do great at structured output. You may find some failures when using research mode, so please share your feedback so we can improve this.

  • #567 5e9bc28 Thanks @eyaltoledano! - This change significantly enhances the add-task command's intelligence. When you add a new task, Taskmaster now automatically: - Analyzes your existing tasks to find those most relevant to your new task's description. - Provides the AI with detailed context from these relevant tasks.

    This results in newly created tasks being more accurately placed within your project's dependency structure, saving you time and any need to update tasks just for dependencies, all without significantly increasing AI costs. You'll get smarter, more connected tasks right from the start.

  • #567 34c769b Thanks @eyaltoledano! - Enhance analyze-complexity to support analyzing specific task IDs. - You can now analyze individual tasks or selected task groups by using the new --id option with comma-separated IDs, or --from and --to options to specify a range of tasks. - The feature intelligently merges analysis results with existing reports, allowing incremental analysis while preserving previous results.

  • #558 86d8f00 Thanks @ShreyPaharia! - Add next task to set task status response Status: DONE

  • #567 04af16d Thanks @eyaltoledano! - Add move command to enable moving tasks and subtasks within the task hierarchy. This new command supports moving standalone tasks to become subtasks, subtasks to become standalone tasks, and moving subtasks between different parents. The implementation handles circular dependencies, validation, and proper updating of parent-child relationships.

    Usage:

    • CLI command: task-master move --from=<id> --to=<id>
    • MCP tool: move_task with parameters:
      • from: ID of task/subtask to move (e.g., "5" or "5.2")
      • to: ID of destination (e.g., "7" or "7.3")
      • file (optional): Custom path to tasks.json

    Example scenarios:

    • Move task to become subtask: --from="5" --to="7"
    • Move subtask to standalone task: --from="5.2" --to="7"
    • Move subtask to different parent: --from="5.2" --to="7.3"
    • Reorder subtask within same parent: --from="5.2" --to="5.4"
    • Move multiple tasks at once: --from="10,11,12" --to="16,17,18"
    • Move task to new ID: --from="5" --to="25" (creates a new task with ID 25)

    Multiple Task Support: The command supports moving multiple tasks simultaneously by providing comma-separated lists for both --from and --to parameters. The number of source and destination IDs must match. This is particularly useful for resolving merge conflicts in task files when multiple team members have created tasks on different branches.

    Validation Features:

    • Allows moving tasks to new, non-existent IDs (automatically creates placeholders)
    • Prevents moving to existing task IDs that already contain content (to avoid overwriting)
    • Validates source tasks exist before attempting to move them
    • Ensures proper parent-child relationships are maintained

Patch Changes

  • #567 231e569 Thanks @eyaltoledano! - Adjusts default main model model to Claude Sonnet 4. Adjusts default fallback to Claude Sonney 3.7"

  • #567 b371808 Thanks @eyaltoledano! - Adds llms-install.md to the root to enable AI agents to programmatically install the Taskmaster MCP server. This is specifically being introduced for the Cline MCP marketplace and will be adjusted over time for other MCP clients as needed.

  • #567 a59dd03 Thanks @eyaltoledano! - Adds AGENTS.md to power Claude Code integration more natively based on Anthropic's best practice and Claude-specific MCP client behaviours. Also adds in advanced workflows that tie Taskmaster commands together into one Claude workflow."

  • #567 e0e1155 Thanks @eyaltoledano! - Fixes issue with force/append flag combinations for parse-prd.

  • #567 34df2c8 Thanks @eyaltoledano! - You can now add tasks to a newly initialized project without having to parse a prd. This will automatically create the missing tasks.json file and create the first task. Lets you vibe if you want to vibe."

  • #567 d2e6431 Thanks @eyaltoledano! - Fixes an issue where the research fallback would attempt to make API calls without checking for a valid API key first. This ensures proper error handling when the main task generation and first fallback both fail. Closes #421 #519.

0.15.0-rc.0

Minor Changes

  • #567 09add37 Thanks @eyaltoledano! - Added comprehensive Ollama model validation and interactive setup support

    • Interactive Setup Enhancement: Added "Custom Ollama model" option to task-master models --setup, matching the existing OpenRouter functionality
    • Live Model Validation: When setting Ollama models, Taskmaster now validates against the local Ollama instance by querying /api/tags endpoint
    • Configurable Endpoints: Uses the ollamaBaseUrl from .taskmasterconfig (with role-specific baseUrl overrides supported)
    • Robust Error Handling:
      • Detects when Ollama server is not running and provides clear error messages
      • Validates model existence and lists available alternatives when model not found
      • Graceful fallback behavior for connection issues
    • Full Platform Support: Both MCP server tools and CLI commands support the new validation
    • Improved User Experience: Clear feedback during model validation with informative success/error messages

  • #567 4c83526 Thanks @eyaltoledano! - Adds and updates supported AI models with costs:

    • Added new OpenRouter models: GPT-4.1 series, O3, Codex Mini, Llama 4 Maverick, Llama 4 Scout, Qwen3-235b
    • Added Mistral models: Devstral Small, Mistral Nemo
    • Updated Ollama models with latest variants: Devstral, Qwen3, Mistral-small3.1, Llama3.3
    • Updated Gemini model to latest 2.5 Flash preview version

  • #567 70f4054 Thanks @eyaltoledano! - Add --research flag to parse-prd command, enabling enhanced task generation from PRD files. When used, Taskmaster leverages the research model to:

    • Research current technologies and best practices relevant to the project
    • Identify technical challenges and security concerns not explicitly mentioned in the PRD
    • Include specific library recommendations with version numbers
    • Provide more detailed implementation guidance based on industry standards
    • Create more accurate dependency relationships between tasks

    This results in higher quality, more actionable tasks with minimal additional effort.

    NOTE That this is an experimental feature. Research models don't typically do great at structured output. You may find some failures when using research mode, so please share your feedback so we can improve this.

  • #567 5e9bc28 Thanks @eyaltoledano! - This change significantly enhances the add-task command's intelligence. When you add a new task, Taskmaster now automatically: - Analyzes your existing tasks to find those most relevant to your new task's description. - Provides the AI with detailed context from these relevant tasks.

    This results in newly created tasks being more accurately placed within your project's dependency structure, saving you time and any need to update tasks just for dependencies, all without significantly increasing AI costs. You'll get smarter, more connected tasks right from the start.

  • #567 34c769b Thanks @eyaltoledano! - Enhance analyze-complexity to support analyzing specific task IDs. - You can now analyze individual tasks or selected task groups by using the new --id option with comma-separated IDs, or --from and --to options to specify a range of tasks. - The feature intelligently merges analysis results with existing reports, allowing incremental analysis while preserving previous results.

  • #558 86d8f00 Thanks @ShreyPaharia! - Add next task to set task status response Status: DONE

  • #567 04af16d Thanks @eyaltoledano! - Add move command to enable moving tasks and subtasks within the task hierarchy. This new command supports moving standalone tasks to become subtasks, subtasks to become standalone tasks, and moving subtasks between different parents. The implementation handles circular dependencies, validation, and proper updating of parent-child relationships.

    Usage:

    • CLI command: task-master move --from=<id> --to=<id>
    • MCP tool: move_task with parameters:
      • from: ID of task/subtask to move (e.g., "5" or "5.2")
      • to: ID of destination (e.g., "7" or "7.3")
      • file (optional): Custom path to tasks.json

    Example scenarios:

    • Move task to become subtask: --from="5" --to="7"
    • Move subtask to standalone task: --from="5.2" --to="7"
    • Move subtask to different parent: --from="5.2" --to="7.3"
    • Reorder subtask within same parent: --from="5.2" --to="5.4"
    • Move multiple tasks at once: --from="10,11,12" --to="16,17,18"
    • Move task to new ID: --from="5" --to="25" (creates a new task with ID 25)

    Multiple Task Support: The command supports moving multiple tasks simultaneously by providing comma-separated lists for both --from and --to parameters. The number of source and destination IDs must match. This is particularly useful for resolving merge conflicts in task files when multiple team members have created tasks on different branches.

    Validation Features:

    • Allows moving tasks to new, non-existent IDs (automatically creates placeholders)
    • Prevents moving to existing task IDs that already contain content (to avoid overwriting)
    • Validates source tasks exist before attempting to move them
    • Ensures proper parent-child relationships are maintained

Patch Changes

  • #567 231e569 Thanks @eyaltoledano! - Adjusts default main model model to Claude Sonnet 4. Adjusts default fallback to Claude Sonney 3.7"

  • #567 b371808 Thanks @eyaltoledano! - Adds llms-install.md to the root to enable AI agents to programmatically install the Taskmaster MCP server. This is specifically being introduced for the Cline MCP marketplace and will be adjusted over time for other MCP clients as needed.

  • #567 a59dd03 Thanks @eyaltoledano! - Adds AGENTS.md to power Claude Code integration more natively based on Anthropic's best practice and Claude-specific MCP client behaviours. Also adds in advanced workflows that tie Taskmaster commands together into one Claude workflow."

  • #567 e0e1155 Thanks @eyaltoledano! - Fixes issue with force/append flag combinations for parse-prd.

  • #567 34df2c8 Thanks @eyaltoledano! - You can now add tasks to a newly initialized project without having to parse a prd. This will automatically create the missing tasks.json file and create the first task. Lets you vibe if you want to vibe."

  • #567 d2e6431 Thanks @eyaltoledano! - Fixes an issue where the research fallback would attempt to make API calls without checking for a valid API key first. This ensures proper error handling when the main task generation and first fallback both fail. Closes #421 #519.

0.14.0

Minor Changes

  • #521 ed17cb0 Thanks @Crunchyman-ralph! - .taskmasterconfig now supports a baseUrl field per model role (main, research, fallback), allowing endpoint overrides for any provider.

  • #536 f4a83ec Thanks @Crunchyman-ralph! - Add Ollama as a supported AI provider.

    • You can now add it by running task-master models --setup and selecting it.
    • Ollama is a local model provider, so no API key is required.
    • Ollama models are available at http://localhost:11434/api by default.
    • You can change the default URL by setting the OLLAMA_BASE_URL environment variable or by adding a baseUrl property to the ollama model role in .taskmasterconfig.
      • If you want to use a custom API key, you can set it in the OLLAMA_API_KEY environment variable.

  • #528 58b417a Thanks @Crunchyman-ralph! - Display task complexity scores in task lists, next task, and task details views.

Patch Changes

  • #402 01963af Thanks @Crunchyman-ralph! - Resolve all issues related to MCP

  • #478 4117f71 Thanks @joedanz! - Fix CLI --force flag for parse-prd command

    Previously, the --force flag was not respected when running parse-prd, causing the command to prompt for confirmation or fail even when --force was provided. This patch ensures that the flag is correctly passed and handled, allowing users to overwrite existing tasks.json files as intended.

    • Fixes #477

  • #511 17294ff Thanks @Crunchyman-ralph! - Task Master no longer tells you to update when you're already up to date

  • #442 2b3ae8b Thanks @eyaltoledano! - Adds costs information to AI commands using input/output tokens and model costs.

  • #402 01963af Thanks @Crunchyman-ralph! - Fix ERR_MODULE_NOT_FOUND when trying to run MCP Server

  • #402 01963af Thanks @Crunchyman-ralph! - Add src directory to exports

  • #523 da317f2 Thanks @Crunchyman-ralph! - Fix the error handling of task status settings

  • #527 a8dabf4 Thanks @Crunchyman-ralph! - Remove caching layer from MCP direct functions for task listing, next task, and complexity report

    • Fixes issues users where having where they were getting stale data

  • #417 a1f8d52 Thanks @ksylvan! - Fix for issue #409 LOG_LEVEL Pydantic validation error

  • #442 0288311 Thanks @eyaltoledano! - Small fixes - next command no longer incorrectly suggests that subtasks be broken down into subtasks in the CLI - fixes the append flag so it properly works in the CLI

  • #501 0a61184 Thanks @Crunchyman-ralph! - Fix initial .env.example to work out of the box

    • Closes #419

  • #435 a96215a Thanks @lebsral! - Fix default fallback model and maxTokens in Taskmaster initialization

  • #517 e96734a Thanks @Crunchyman-ralph! - Fix bug when updating tasks on the MCP server (#412)

  • #496 efce374 Thanks @joedanz! - Fix duplicate output on CLI help screen

    • Prevent the Task Master CLI from printing the help screen more than once when using -h or --help.
    • Removed redundant manual event handlers and guards for help output; now only the Commander .helpInformation override is used for custom help.
    • Simplified logic so that help is only shown once for both "no arguments" and help flag flows.
    • Ensures a clean, branded help experience with no repeated content.
    • Fixes #339

0.14.0-rc.1

Minor Changes

  • #536 f4a83ec Thanks @Crunchyman-ralph! - Add Ollama as a supported AI provider.

    • You can now add it by running task-master models --setup and selecting it.
    • Ollama is a local model provider, so no API key is required.
    • Ollama models are available at http://localhost:11434/api by default.
    • You can change the default URL by setting the OLLAMA_BASE_URL environment variable or by adding a baseUrl property to the ollama model role in .taskmasterconfig.
      • If you want to use a custom API key, you can set it in the OLLAMA_API_KEY environment variable.

Patch Changes

  • #442 2b3ae8b Thanks @eyaltoledano! - Adds costs information to AI commands using input/output tokens and model costs.

  • #442 0288311 Thanks @eyaltoledano! - Small fixes - next command no longer incorrectly suggests that subtasks be broken down into subtasks in the CLI - fixes the append flag so it properly works in the CLI

0.14.0-rc.0

Minor Changes

  • #521 ed17cb0 Thanks @Crunchyman-ralph! - .taskmasterconfig now supports a baseUrl field per model role (main, research, fallback), allowing endpoint overrides for any provider.

  • #528 58b417a Thanks @Crunchyman-ralph! - Display task complexity scores in task lists, next task, and task details views.

Patch Changes

  • #478 4117f71 Thanks @joedanz! - Fix CLI --force flag for parse-prd command

    Previously, the --force flag was not respected when running parse-prd, causing the command to prompt for confirmation or fail even when --force was provided. This patch ensures that the flag is correctly passed and handled, allowing users to overwrite existing tasks.json files as intended.

    • Fixes #477

  • #511 17294ff Thanks @Crunchyman-ralph! - Task Master no longer tells you to update when you're already up to date

  • #523 da317f2 Thanks @Crunchyman-ralph! - Fix the error handling of task status settings

  • #527 a8dabf4 Thanks @Crunchyman-ralph! - Remove caching layer from MCP direct functions for task listing, next task, and complexity report

    • Fixes issues users where having where they were getting stale data

  • #417 a1f8d52 Thanks @ksylvan! - Fix for issue #409 LOG_LEVEL Pydantic validation error

  • #501 0a61184 Thanks @Crunchyman-ralph! - Fix initial .env.example to work out of the box

    • Closes #419

  • #435 a96215a Thanks @lebsral! - Fix default fallback model and maxTokens in Taskmaster initialization

  • #517 e96734a Thanks @Crunchyman-ralph! - Fix bug when updating tasks on the MCP server (#412)

  • #496 efce374 Thanks @joedanz! - Fix duplicate output on CLI help screen

    • Prevent the Task Master CLI from printing the help screen more than once when using -h or --help.
    • Removed redundant manual event handlers and guards for help output; now only the Commander .helpInformation override is used for custom help.
    • Simplified logic so that help is only shown once for both "no arguments" and help flag flows.
    • Ensures a clean, branded help experience with no repeated content.
    • Fixes #339

0.13.1

Patch Changes

0.13.0

Minor Changes

  • #240 ef782ff Thanks @eyaltoledano! - feat(expand): Enhance expand and expand-all commands

    • Integrate task-complexity-report.json to automatically determine the number of subtasks and use tailored prompts for expansion based on prior analysis. You no longer need to try copy-pasting the recommended prompt. If it exists, it will use it for you. You can just run task-master update --id=[id of task] --research and it will use that prompt automatically. No extra prompt needed.
    • Change default behavior to append new subtasks to existing ones. Use the --force flag to clear existing subtasks before expanding. This is helpful if you need to add more subtasks to a task but you want to do it by the batch from a given prompt. Use force if you want to start fresh with a task's subtasks.

  • #240 87d97bb Thanks @eyaltoledano! - Adds support for the OpenRouter AI provider. Users can now configure models available through OpenRouter (requiring an OPENROUTER_API_KEY) via the task-master models command, granting access to a wide range of additional LLMs. - IMPORTANT FYI ABOUT OPENROUTER: Taskmaster relies on AI SDK, which itself relies on tool use. It looks like free models sometimes do not include tool use. For example, Gemini 2.5 pro (free) failed via OpenRouter (no tool use) but worked fine on the paid version of the model. Custom model support for Open Router is considered experimental and likely will not be further improved for some time.

  • #240 1ab836f Thanks @eyaltoledano! - Adds model management and new configuration file .taskmasterconfig which houses the models used for main, research and fallback. Adds models command and setter flags. Adds a --setup flag with an interactive setup. We should be calling this during init. Shows a table of active and available models when models is called without flags. Includes SWE scores and token costs, which are manually entered into the supported_models.json, the new place where models are defined for support. Config-manager.js is the core module responsible for managing the new config."

  • #240 c8722b0 Thanks @eyaltoledano! - Adds custom model ID support for Ollama and OpenRouter providers.

    • Adds the --ollama and --openrouter flags to task-master models --set-<role> command to set models for those providers outside of the support models list.
    • Updated task-master models --setup interactive mode with options to explicitly enter custom Ollama or OpenRouter model IDs.
    • Implemented live validation against OpenRouter API (/api/v1/models) when setting a custom OpenRouter model ID (via flag or setup).
    • Refined logic to prioritize explicit provider flags/choices over internal model list lookups in case of ID conflicts.
    • Added warnings when setting custom/unvalidated models.
    • We obviously don't recommend going with a custom, unproven model. If you do and find performance is good, please let us know so we can add it to the list of supported models.

  • #240 2517bc1 Thanks @eyaltoledano! - Integrate OpenAI as a new AI provider. - Enhance models command/tool to display API key status. - Implement model-specific maxTokens override based on supported-models.json to save you if you use an incorrect max token value.

  • #240 9a48278 Thanks @eyaltoledano! - Tweaks Perplexity AI calls for research mode to max out input tokens and get day-fresh information - Forces temp at 0.1 for highly deterministic output, no variations - Adds a system prompt to further improve the output - Correctly uses the maximum input tokens (8,719, used 8,700) for perplexity - Specificies to use a high degree of research across the web - Specifies to use information that is as fresh as today; this support stuff like capturing brand new announcements like new GPT models and being able to query for those in research. 🔥

Patch Changes

  • #240 842eaf7 Thanks @eyaltoledano! - - Add support for Google Gemini models via Vercel AI SDK integration.

  • #240 ed79d4f Thanks @eyaltoledano! - Add xAI provider and Grok models support

  • #378 ad89253 Thanks @eyaltoledano! - Better support for file paths on Windows, Linux & WSL.

    • Standardizes handling of different path formats (URI encoded, Windows, Linux, WSL).
    • Ensures tools receive a clean, absolute path suitable for the server OS.
    • Simplifies tool implementation by centralizing normalization logic.

  • #285 2acba94 Thanks @neno-is-ooo! - Add integration for Roo Code

  • #378 d63964a Thanks @eyaltoledano! - Improved update-subtask - Now it has context about the parent task details - It also has context about the subtask before it and the subtask after it (if they exist) - Not passing all subtasks to stay token efficient

  • #240 5f504fa Thanks @eyaltoledano! - Improve and adjust init command for robustness and updated dependencies.

    • Update Initialization Dependencies: Ensure newly initialized projects (task-master init) include all required AI SDK dependencies (@ai-sdk/*, ai, provider wrappers) in their package.json for out-of-the-box AI feature compatibility. Remove unnecessary dependencies (e.g., uuid) from the init template.
    • Silence npm install during init: Prevent npm install output from interfering with non-interactive/MCP initialization by suppressing its stdio in silent mode.
    • Improve Conditional Model Setup: Reliably skip interactive models --setup during non-interactive init runs (e.g., init -y or MCP) by checking isSilentMode() instead of passing flags.
    • Refactor init.js: Remove internal isInteractive flag logic.
    • Update init Instructions: Tweak the "Getting Started" text displayed after init.
    • Fix MCP Server Launch: Update .cursor/mcp.json template to use node ./mcp-server/server.js instead of npx task-master-mcp.
    • Update Default Model: Change the default main model in the .taskmasterconfig template.

  • #240 96aeeff Thanks @eyaltoledano! - Fixes an issue with add-task which did not use the manually defined properties and still needlessly hit the AI endpoint.

  • #240 5aea93d Thanks @eyaltoledano! - Fixes an issue that prevented remove-subtask with comma separated tasks/subtasks from being deleted (only the first ID was being deleted). Closes #140

  • #240 66ac9ab Thanks @eyaltoledano! - Improves next command to be subtask-aware - The logic for determining the "next task" (findNextTask function, used by task-master next and the next_task MCP tool) has been significantly improved. Previously, it only considered top-level tasks, making its recommendation less useful when a parent task containing subtasks was already marked 'in-progress'. - The updated logic now prioritizes finding the next available subtask within any 'in-progress' parent task, considering subtask dependencies and priority. - If no suitable subtask is found within active parent tasks, it falls back to recommending the next eligible top-level task based on the original criteria (status, dependencies, priority).

    This change makes the next command much more relevant and helpful during the implementation phase of complex tasks.

  • #240 ca7b045 Thanks @eyaltoledano! - Add --status flag to show command to filter displayed subtasks.

  • #328 5a2371b Thanks @knoxgraeme! - Fix --task to --num-tasks in ui + related tests - issue #324

  • #240 6cb213e Thanks @eyaltoledano! - Adds a 'models' CLI and MCP command to get the current model configuration, available models, and gives the ability to set main/research/fallback models." - In the CLI, task-master models shows the current models config. Using the --setup flag launches an interactive set up that allows you to easily select the models you want to use for each of the three roles. Use q during the interactive setup to cancel the setup. - In the MCP, responses are simplified in RESTful format (instead of the full CLI output). The agent can use the models tool with different arguments, including listAvailableModels to get available models. Run without arguments, it will return the current configuration. Arguments are available to set the model for each of the three roles. This allows you to manage Taskmaster AI providers and models directly from either the CLI or MCP or both. - Updated the CLI help menu when you run task-master to include missing commands and .taskmasterconfig information. - Adds --research flag to add-task so you can hit up Perplexity right from the add-task flow, rather than having to add a task and then update it.

0.12.1

Patch Changes

0.12.0

Minor Changes

  • #253 b2ccd60 Thanks @Crunchyman-ralph! - Add npx task-master-ai that runs mcp instead of using `task-master-mcp``

  • #267 c17d912 Thanks @Crunchyman-ralph! - Improve PRD parsing prompt with structured analysis and clearer task generation guidelines. We are testing a new prompt - please provide feedback on your experience.

Patch Changes

  • #243 454a1d9 Thanks @Crunchyman-ralph! - - Fixes shebang issue not allowing task-master to run on certain windows operating systems

    • Resolves #241 #211 #184 #193

  • #268 3e872f8 Thanks @Crunchyman-ralph! - Fix remove-task command to handle multiple comma-separated task IDs

  • #239 6599cb0 Thanks @eyaltoledano! - Updates the parameter descriptions for update, update-task and update-subtask to ensure the MCP server correctly reaches for the right update command based on what is being updated -- all tasks, one task, or a subtask.

  • #272 3aee9bc Thanks @Crunchyman-ralph! - Enhance the parsePRD to include --append flag. This flag allows users to append the parsed PRD to an existing file, making it easier to manage multiple PRD files without overwriting existing content.

  • #264 ff8e75c Thanks @joedanz! - Add quotes around numeric env vars in mcp.json (Windsurf, etc.)

  • #248 d99fa00 Thanks @Crunchyman-ralph! - - Fix task-master init polluting codebase with new packages inside package.json and modifying project README

    • Now only initializes with cursor rules, windsurf rules, mcp.json, scripts/example_prd.txt, .gitignore modifications, and README-task-master.md

  • #266 41b979c Thanks @Crunchyman-ralph! - Fixed a bug that prevented the task-master from running in a Linux container

  • #265 0eb16d5 Thanks @Crunchyman-ralph! - Remove the need for project name, description, and version. Since we no longer create a package.json for you

0.11.0

Minor Changes

  • #71 7141062 Thanks @eyaltoledano! - - Easier Ways to Use Taskmaster (CLI & MCP):
    • You can now use Taskmaster either by installing it as a standard command-line tool (task-master) or as an MCP server directly within integrated development tools like Cursor (using its built-in features). This makes Taskmaster accessible regardless of your preferred workflow.
    • Setting up a new project is simpler in integrated tools, thanks to the new initialize_project capability.
    • Complete MCP Implementation:
      • NOTE: Many MCP clients charge on a per tool basis. In that regard, the most cost-efficient way to use Taskmaster is through the CLI directly. Otherwise, the MCP offers the smoothest and most recommended user experience.
      • All MCP tools now follow a standardized output format that mimicks RESTful API responses. They are lean JSON responses that are context-efficient. This is a net improvement over the last version which sent the whole CLI output directly, which needlessly wasted tokens.
      • Added a remove-task command to permanently delete tasks you no longer need.
      • Many new MCP tools are available for managing tasks (updating details, adding/removing subtasks, generating task files, setting status, finding the next task, breaking down complex tasks, handling dependencies, analyzing complexity, etc.), usable both from the command line and integrated tools. (See the taskmaster.mdc reference guide and improved readme for a full list).
    • Better Task Tracking:
      • Added a "cancelled" status option for tasks, providing more ways to categorize work.
    • Smoother Experience in Integrated Tools:
      • Long-running operations (like breaking down tasks or analysis) now run in the background via an Async Operation Manager with progress updates, so you know what's happening without waiting and can check status later.
    • Improved Documentation:
      • Added a comprehensive reference guide (taskmaster.mdc) detailing all commands and tools with examples, usage tips, and troubleshooting info. This is mostly for use by the AI but can be useful for human users as well.
      • Updated the main README with clearer instructions and added a new tutorial/examples guide.
      • Added documentation listing supported integrated tools (like Cursor).
    • Increased Stability & Reliability:
      • Using Taskmaster within integrated tools (like Cursor) is now more stable and the recommended approach.
      • Added automated testing (CI) to catch issues earlier, leading to a more reliable tool.
      • Fixed release process issues to ensure users get the correct package versions when installing or updating via npm.
    • Better Command-Line Experience:
      • Fixed bugs in the expand-all command that could cause NaN errors or JSON formatting issues (especially when using --research).
      • Fixed issues with parameter validation in the analyze-complexity command (specifically related to the threshold parameter).
      • Made the add-task command more consistent by adding standard flags like --title, --description for manual task creation so you don't have to use --prompt and can quickly drop new ideas and stay in your flow.
      • Improved error messages for incorrect commands or flags, making them easier to understand.
      • Added confirmation warnings before permanently deleting tasks (remove-task) to prevent mistakes. There's a known bug for deleting multiple tasks with comma-separated values. It'll be fixed next release.
      • Renamed some background tool names used by integrated tools (e.g., list-tasks is now get_tasks) to be more intuitive if seen in logs or AI interactions.
      • Smoother project start: Improved the guidance provided to AI assistants immediately after setup (related to init and parse-prd steps). This ensures the AI doesn't go on a tangent deciding its own workflow, and follows the exact process outlined in the Taskmaster workflow.
    • Clearer Error Messages:
      • When generating subtasks fails, error messages are now clearer, including specific task IDs and potential suggestions.
      • AI fallback from Claude to Perplexity now also works the other way around. If Perplexity is down, will switch to Claude.
    • Simplified Setup & Configuration:
      • Made it clearer how to configure API keys depending on whether you're using the command-line tool (.env file) or an integrated tool (.cursor/mcp.json file).
      • Taskmaster is now better at automatically finding your project files, especially in integrated tools, reducing the need for manual path settings.
      • Fixed an issue that could prevent Taskmaster from working correctly immediately after initialization in integrated tools (related to how the MCP server was invoked). This should solve the issue most users were experiencing with the last release (0.10.x)
      • Updated setup templates with clearer examples for API keys.
      • **For advanced users setting up the MCP server manually, the command is now npx -y task-master-ai task-master-mcp.
    • Enhanced Performance & AI:
      • Updated underlying AI model settings:
        • Increased Context Window: Can now handle larger projects/tasks due to an increased Claude context window (64k -> 128k tokens).
        • Reduced AI randomness: More consistent and predictable AI outputs (temperature 0.4 -> 0.2).
        • Updated default AI models: Uses newer models like claude-3-7-sonnet-20250219 and Perplexity sonar-pro by default.
        • More granular breakdown: Increased the default number of subtasks generated by expand to 5 (from 4).
        • Consistent defaults: Set the default priority for new tasks consistently to "medium".
      • Improved performance when viewing task details in integrated tools by sending less redundant data.
    • Documentation Clarity:
      • Clarified in documentation that Markdown files (.md) can be used for Product Requirements Documents (parse_prd).
      • Improved the description for the numTasks option in parse_prd for better guidance.
    • Improved Visuals (CLI):
      • Enhanced the look and feel of progress bars and status updates in the command line.
      • Added a helpful color-coded progress bar to the task details view (show command) to visualize subtask completion.
      • Made progress bars show a breakdown of task statuses (e.g., how many are pending vs. done).
      • Made status counts clearer with text labels next to icons.
      • Prevented progress bars from messing up the display on smaller terminal windows.
      • Adjusted how progress is calculated for 'deferred' and 'cancelled' tasks in the progress bar, while still showing their distinct status visually.
    • Fixes for Integrated Tools:
      • Fixed how progress updates are sent to integrated tools, ensuring they display correctly.
      • Fixed internal issues that could cause errors or invalid JSON responses when using Taskmaster with integrated tools.

0.10.1

Patch Changes

0.10.0

Minor Changes

Patch Changes