docs: Update configuration.md (#782)

Version Packages

.changeset/bright-windows-sing.md

@@ -1,77 +0,0 @@
----
-"task-master-ai": minor
----
-
-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:**
-
-```bash
-# 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:**
-
-```bash
-# 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.

.changeset/chatty-rats-talk.md

@@ -1,5 +0,0 @@
----
-"task-master-ai": patch
----
-
-Fix Cursor deeplink installation by providing copy-paste instructions for GitHub compatibility

.changeset/cold-pears-poke.md

@@ -1,13 +0,0 @@
----
-'task-master-ai': patch
----
-
-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.

.changeset/curly-dragons-design.md

@@ -1,5 +0,0 @@
----
-"task-master-ai": patch
----
-
-improve findTasks algorithm for resolving tasks path

.changeset/eleven-news-check.md

@@ -1,5 +0,0 @@
----
-"task-master-ai": patch
----
-
-Fix update tool on MCP giving `No valid tasks found`

.changeset/fluffy-waves-allow.md

@@ -1,5 +0,0 @@
----
-"task-master-ai": patch
----
-
-Adds ability to automatically create/switch tags to match the current git branch. The configuration to enable the git workflow and then use the auto switching is in config.json."

.changeset/four-cups-enter.md

@@ -1,39 +0,0 @@
----
-"task-master-ai": patch
----
-
-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.

.changeset/free-pants-rescue.md

@@ -1,18 +0,0 @@
----
-"task-master-ai": minor
----
-
-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.

.changeset/large-wolves-strive.md

@@ -1,5 +0,0 @@
----
-"task-master-ai": patch
----
-
-Update o3 model price

.changeset/late-dryers-relax.md

@@ -1,11 +0,0 @@
----
-"task-master-ai": minor
----
-
-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

.changeset/nasty-chefs-add.md

@@ -1,8 +0,0 @@
----
-"task-master-ai": patch
----
-
-Fixes issue with expand CLI command "Complexity report not found"
-
-- Closes #735
-- Closes #728

.changeset/pink-houses-lay.md

@@ -1,7 +0,0 @@
----
-"task-master-ai": patch
----
-
-Fix double .taskmaster directory paths in file resolution utilities
-
-- Closes #636

.changeset/polite-areas-shave.md

@@ -1,5 +0,0 @@
----
-"task-master-ai": patch
----
-
-Add one-click MCP server installation for Cursor

.changeset/pre.json

@@ -1,11 +0,0 @@
-{
-  "mode": "exit",
-  "tag": "rc",
-  "initialVersions": {
-    "task-master-ai": "0.16.1"
-  },
-  "changesets": [
-    "pink-houses-lay",
-    "polite-areas-shave"
-  ]
-}

.changeset/quick-flies-sniff.md

@@ -1,5 +0,0 @@
----
-"task-master-ai": patch
----
-
-Fix issue with generate command which was creating tasks in the legacy tasks location.

.changeset/rotten-months-brake.md

@@ -0,0 +1,5 @@
+---
+"task-master-ai": patch
+---
+
+Fix contextGatherer bug when adding a task `Cannot read properties of undefined (reading 'forEach')`

.changeset/six-cups-see.md

@@ -1,136 +0,0 @@
----
-"task-master-ai": minor
----
-
-Introduces Tagged Lists: AI Multi-Context Task Management System
-
-This major release introduces Tagged Lists, a comprehensive system that transforms Task Master 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 changes how tasks are organized:
-- **Legacy Format**: `{ "tasks": [...] }` 
-- **New Tagged Format**: `{ "master": { "tasks": [...], "metadata": {...} }, "feature-xyz": { "tasks": [...], "metadata": {...} } }`
-- **Automatic Migration**: Existing projects seamlessly migrate to tagged format with zero user intervention
-- **State Management**: New `.taskmaster/state.json` tracks current tag, last switched time, and migration status
-- **Configuration Integration**: Enhanced `.taskmaster/config.json` with tag-specific settings and defaults
-
-**🚀 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 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 usin 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
-
-**📊 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.

.changeset/slick-webs-lead.md

@@ -1,24 +0,0 @@
----
-"task-master-ai": minor
----
-
-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

.changeset/slow-lies-make.md

@@ -1,5 +0,0 @@
----
-"task-master-ai": minor
----
-
-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.

.changeset/stale-bats-sin.md

@@ -1,19 +0,0 @@
----
-'task-master-ai': minor
----
-
-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.

.changeset/tiny-ads-decide.md

@@ -1,7 +0,0 @@
----
-"task-master-ai": minor
----
-
-Adds support for filtering tasks by multiple statuses at once using comma-separated statuses.
-
-Example: `cancelled,deferred`

.changeset/two-lies-start.md

@@ -1,5 +0,0 @@
----
-"task-master-ai": patch
----
-
-Improves dependency management when moving tasks by updating subtask dependencies that reference sibling subtasks by their old parent-based ID

.changeset/vast-shrimps-happen.md

@@ -1,22 +0,0 @@
----
-"task-master-ai": patch
----
-
-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.

.changeset/yellow-olives-admire.md

@@ -1,5 +0,0 @@
----
-"task-master-ai": minor
----
-
-Adds tag to CLI output so you know which tag you are performing operations on. Already supported in the MCP response.

.cursor/rules/dev_workflow.mdc

@@ -1,19 +1,199 @@
 ---
-description: Guide for using Task Master to manage task-driven development workflows
+description: Guide for using Taskmaster to manage task-driven development workflows
 globs: **/*
 alwaysApply: true
 ---
-# Task Master Development Workflow
 
-This guide outlines the typical process for using Task Master to manage software development projects.
+# Taskmaster Development Workflow
+
+This guide outlines the standard process for using Taskmaster to manage software development projects. It is written as a set of instructions for you, the AI agent.
+
+- **Your Default Stance**: For most projects, the user can work directly within the `master` task context. Your initial actions should operate on this default context unless a clear pattern for multi-context work emerges.
+- **Your Goal**: Your role is to elevate the user's workflow by intelligently introducing advanced features like **Tagged Task Lists** when you detect the appropriate context. Do not force tags on the user; suggest them as a helpful solution to a specific need.
+
+## The Basic Loop
+The fundamental development cycle you will facilitate is:
+1.  **`list`**: Show the user what needs to be done.
+2.  **`next`**: Help the user decide what to work on.
+3.  **`show <id>`**: Provide details for a specific task.
+4.  **`expand <id>`**: Break down a complex task into smaller, manageable subtasks.
+5.  **Implement**: The user writes the code and tests.
+6.  **`update-subtask`**: Log progress and findings on behalf of the user.
+7.  **`set-status`**: Mark tasks and subtasks as `done` as work is completed.
+8.  **Repeat**.
+
+All your standard command executions should operate on the user's current task context, which defaults to `master`.
+
+---
+
+## Standard Development Workflow Process
+
+### Simple Workflow (Default Starting Point)
+
+For new projects or when users are getting started, operate within the `master` tag context:
+
+-   Start new projects by running `initialize_project` tool / `task-master init` or `parse_prd` / `task-master parse-prd --input='<prd-file.txt>'` (see [`taskmaster.mdc`](mdc:.cursor/rules/taskmaster.mdc)) to generate initial tasks.json with tagged structure
+-   Begin coding sessions with `get_tasks` / `task-master list` (see [`taskmaster.mdc`](mdc:.cursor/rules/taskmaster.mdc)) to see current tasks, status, and IDs
+-   Determine the next task to work on using `next_task` / `task-master next` (see [`taskmaster.mdc`](mdc:.cursor/rules/taskmaster.mdc))
+-   Analyze task complexity with `analyze_project_complexity` / `task-master analyze-complexity --research` (see [`taskmaster.mdc`](mdc:.cursor/rules/taskmaster.mdc)) before breaking down tasks
+-   Review complexity report using `complexity_report` / `task-master complexity-report` (see [`taskmaster.mdc`](mdc:.cursor/rules/taskmaster.mdc))
+-   Select tasks based on dependencies (all marked 'done'), priority level, and ID order
+-   View specific task details using `get_task` / `task-master show <id>` (see [`taskmaster.mdc`](mdc:.cursor/rules/taskmaster.mdc)) to understand implementation requirements
+-   Break down complex tasks using `expand_task` / `task-master expand --id=<id> --force --research` (see [`taskmaster.mdc`](mdc:.cursor/rules/taskmaster.mdc)) with appropriate flags like `--force` (to replace existing subtasks) and `--research`
+-   Implement code following task details, dependencies, and project standards
+-   Mark completed tasks with `set_task_status` / `task-master set-status --id=<id> --status=done` (see [`taskmaster.mdc`](mdc:.cursor/rules/taskmaster.mdc))
+-   Update dependent tasks when implementation differs from original plan using `update` / `task-master update --from=<id> --prompt="..."` or `update_task` / `task-master update-task --id=<id> --prompt="..."` (see [`taskmaster.mdc`](mdc:.cursor/rules/taskmaster.mdc))
+
+---
+
+## Leveling Up: Agent-Led Multi-Context Workflows
+
+While the basic workflow is powerful, your primary opportunity to add value is by identifying when to introduce **Tagged Task Lists**. These patterns are your tools for creating a more organized and efficient development environment for the user, especially if you detect agentic or parallel development happening across the same session.
+
+**Critical Principle**: Most users should never see a difference in their experience. Only introduce advanced workflows when you detect clear indicators that the project has evolved beyond simple task management.
+
+### When to Introduce Tags: Your Decision Patterns
+
+Here are the patterns to look for. When you detect one, you should propose the corresponding workflow to the user.
+
+#### Pattern 1: Simple Git Feature Branching
+This is the most common and direct use case for tags.
+
+- **Trigger**: The user creates a new git branch (e.g., `git checkout -b feature/user-auth`).
+- **Your Action**: Propose creating a new tag that mirrors the branch name to isolate the feature's tasks from `master`.
+- **Your Suggested Prompt**: *"I see you've created a new branch named 'feature/user-auth'. To keep all related tasks neatly organized and separate from your main list, I can create a corresponding task tag for you. This helps prevent merge conflicts in your `tasks.json` file later. Shall I create the 'feature-user-auth' tag?"*
+- **Tool to Use**: `task-master add-tag --from-branch`
+
+#### Pattern 2: Team Collaboration
+- **Trigger**: The user mentions working with teammates (e.g., "My teammate Alice is handling the database schema," or "I need to review Bob's work on the API.").
+- **Your Action**: Suggest creating a separate tag for the user's work to prevent conflicts with shared master context.
+- **Your Suggested Prompt**: *"Since you're working with Alice, I can create a separate task context for your work to avoid conflicts. This way, Alice can continue working with the master list while you have your own isolated context. When you're ready to merge your work, we can coordinate the tasks back to master. Shall I create a tag for your current work?"*
+- **Tool to Use**: `task-master add-tag my-work --copy-from-current --description="My tasks while collaborating with Alice"`
+
+#### Pattern 3: Experiments or Risky Refactors
+- **Trigger**: The user wants to try something that might not be kept (e.g., "I want to experiment with switching our state management library," or "Let's refactor the old API module, but I want to keep the current tasks as a reference.").
+- **Your Action**: Propose creating a sandboxed tag for the experimental work.
+- **Your Suggested Prompt**: *"This sounds like a great experiment. To keep these new tasks separate from our main plan, I can create a temporary 'experiment-zustand' tag for this work. If we decide not to proceed, we can simply delete the tag without affecting the main task list. Sound good?"*
+- **Tool to Use**: `task-master add-tag experiment-zustand --description="Exploring Zustand migration"`
+
+#### Pattern 4: Large Feature Initiatives (PRD-Driven)
+This is a more structured approach for significant new features or epics.
+
+- **Trigger**: The user describes a large, multi-step feature that would benefit from a formal plan.
+- **Your Action**: Propose a comprehensive, PRD-driven workflow.
+- **Your Suggested Prompt**: *"This sounds like a significant new feature. To manage this effectively, I suggest we create a dedicated task context for it. Here's the plan: I'll create a new tag called 'feature-xyz', then we can draft a Product Requirements Document (PRD) together to scope the work. Once the PRD is ready, I'll automatically generate all the necessary tasks within that new tag. How does that sound?"*
+- **Your Implementation Flow**:
+    1.  **Create an empty tag**: `task-master add-tag feature-xyz --description "Tasks for the new XYZ feature"`. You can also start by creating a git branch if applicable, and then create the tag from that branch.
+    2.  **Collaborate & Create PRD**: Work with the user to create a detailed PRD file (e.g., `.taskmaster/docs/feature-xyz-prd.txt`).
+    3.  **Parse PRD into the new tag**: `task-master parse-prd .taskmaster/docs/feature-xyz-prd.txt --tag feature-xyz`
+    4.  **Prepare the new task list**: Follow up by suggesting `analyze-complexity` and `expand-all` for the newly created tasks within the `feature-xyz` tag.
+
+#### Pattern 5: Version-Based Development
+Tailor your approach based on the project maturity indicated by tag names.
+
+- **Prototype/MVP Tags** (`prototype`, `mvp`, `poc`, `v0.x`):
+  - **Your Approach**: Focus on speed and functionality over perfection
+  - **Task Generation**: Create tasks that emphasize "get it working" over "get it perfect"
+  - **Complexity Level**: Lower complexity, fewer subtasks, more direct implementation paths
+  - **Research Prompts**: Include context like "This is a prototype - prioritize speed and basic functionality over optimization"
+  - **Example Prompt Addition**: *"Since this is for the MVP, I'll focus on tasks that get core functionality working quickly rather than over-engineering."*
+
+- **Production/Mature Tags** (`v1.0+`, `production`, `stable`):
+  - **Your Approach**: Emphasize robustness, testing, and maintainability
+  - **Task Generation**: Include comprehensive error handling, testing, documentation, and optimization
+  - **Complexity Level**: Higher complexity, more detailed subtasks, thorough implementation paths
+  - **Research Prompts**: Include context like "This is for production - prioritize reliability, performance, and maintainability"
+  - **Example Prompt Addition**: *"Since this is for production, I'll ensure tasks include proper error handling, testing, and documentation."*
+
+### Advanced Workflow (Tag-Based & PRD-Driven)
+
+**When to Transition**: Recognize when the project has evolved (or has initiated a project which existing code) beyond simple task management. Look for these indicators:
+- User mentions teammates or collaboration needs
+- Project has grown to 15+ tasks with mixed priorities
+- User creates feature branches or mentions major initiatives
+- User initializes Taskmaster on an existing, complex codebase
+- User describes large features that would benefit from dedicated planning
+
+**Your Role in Transition**: Guide the user to a more sophisticated workflow that leverages tags for organization and PRDs for comprehensive planning.
+
+#### Master List Strategy (High-Value Focus)
+Once you transition to tag-based workflows, the `master` tag should ideally contain only:
+- **High-level deliverables** that provide significant business value
+- **Major milestones** and epic-level features
+- **Critical infrastructure** work that affects the entire project
+- **Release-blocking** items
+
+**What NOT to put in master**:
+- Detailed implementation subtasks (these go in feature-specific tags' parent tasks)
+- Refactoring work (create dedicated tags like `refactor-auth`)
+- Experimental features (use `experiment-*` tags)
+- Team member-specific tasks (use person-specific tags)
+
+#### PRD-Driven Feature Development
+
+**For New Major Features**:
+1. **Identify the Initiative**: When user describes a significant feature
+2. **Create Dedicated Tag**: `add_tag feature-[name] --description="[Feature description]"`
+3. **Collaborative PRD Creation**: Work with user to create comprehensive PRD in `.taskmaster/docs/feature-[name]-prd.txt`
+4. **Parse & Prepare**: 
+   - `parse_prd .taskmaster/docs/feature-[name]-prd.txt --tag=feature-[name]`
+   - `analyze_project_complexity --tag=feature-[name] --research`
+   - `expand_all --tag=feature-[name] --research`
+5. **Add Master Reference**: Create a high-level task in `master` that references the feature tag
+
+**For Existing Codebase Analysis**:
+When users initialize Taskmaster on existing projects:
+1. **Codebase Discovery**: Use your native tools for producing deep context about the code base. You may use `research` tool with `--tree` and `--files` to collect up to date information using the existing architecture as context.
+2. **Collaborative Assessment**: Work with user to identify improvement areas, technical debt, or new features
+3. **Strategic PRD Creation**: Co-author PRDs that include:
+   - Current state analysis (based on your codebase research)
+   - Proposed improvements or new features
+   - Implementation strategy considering existing code
+4. **Tag-Based Organization**: Parse PRDs into appropriate tags (`refactor-api`, `feature-dashboard`, `tech-debt`, etc.)
+5. **Master List Curation**: Keep only the most valuable initiatives in master
+
+The parse-prd's `--append` flag enables the user to parse multple PRDs within tags or across tags. PRDs should be focused and the number of tasks they are parsed into should be strategically chosen relative to the PRD's complexity and level of detail.
+
+### Workflow Transition Examples
+
+**Example 1: Simple → Team-Based**
+```
+User: "Alice is going to help with the API work"
+Your Response: "Great! To avoid conflicts, I'll create a separate task context for your work. Alice can continue with the master list while you work in your own context. When you're ready to merge, we can coordinate the tasks back together."
+Action: add_tag my-api-work --copy-from-current --description="My API tasks while collaborating with Alice"
+```
+
+**Example 2: Simple → PRD-Driven**
+```
+User: "I want to add a complete user dashboard with analytics, user management, and reporting"
+Your Response: "This sounds like a major feature that would benefit from detailed planning. Let me create a dedicated context for this work and we can draft a PRD together to ensure we capture all requirements."
+Actions: 
+1. add_tag feature-dashboard --description="User dashboard with analytics and management"
+2. Collaborate on PRD creation
+3. parse_prd dashboard-prd.txt --tag=feature-dashboard
+4. Add high-level "User Dashboard" task to master
+```
+
+**Example 3: Existing Project → Strategic Planning**
+```
+User: "I just initialized Taskmaster on my existing React app. It's getting messy and I want to improve it."
+Your Response: "Let me research your codebase to understand the current architecture, then we can create a strategic plan for improvements."
+Actions:
+1. research "Current React app architecture and improvement opportunities" --tree --files=src/
+2. Collaborate on improvement PRD based on findings
+3. Create tags for different improvement areas (refactor-components, improve-state-management, etc.)
+4. Keep only major improvement initiatives in master
+```
+
+---
 
 ## Primary Interaction: MCP Server vs. CLI
 
-Task Master offers two primary ways to interact:
+Taskmaster offers two primary ways to interact:
 
 1.  **MCP Server (Recommended for Integrated Tools)**:
     - For AI agents and integrated development environments (like Cursor), interacting via the **MCP server is the preferred method**.
-    - The MCP server exposes Task Master functionality through a set of tools (e.g., `get_tasks`, `add_subtask`).
+    - The MCP server exposes Taskmaster functionality through a set of tools (e.g., `get_tasks`, `add_subtask`).
     - This method offers better performance, structured data exchange, and richer error handling compared to CLI parsing.
     - Refer to [`mcp.mdc`](mdc:.cursor/rules/mcp.mdc) for details on the MCP architecture and available tools.
     - A comprehensive list and description of MCP tools and their corresponding CLI commands can be found in [`taskmaster.mdc`](mdc:.cursor/rules/taskmaster.mdc).
@@ -28,62 +208,15 @@ Task Master offers two primary ways to interact:
     - Refer to [`taskmaster.mdc`](mdc:.cursor/rules/taskmaster.mdc) for a detailed command reference.
     - **Tagged Task Lists**: CLI fully supports the new tagged system with seamless migration.
 
-## Tagged Task Lists System
+## How the Tag System Works (For Your Reference)
 
-Task Master now supports **tagged task lists** for multi-context task management:
+- **Data Structure**: Tasks are organized into separate contexts (tags) like "master", "feature-branch", or "v2.0".
+- **Silent Migration**: Existing projects automatically migrate to use a "master" tag with zero disruption.
+- **Context Isolation**: Tasks in different tags are completely separate. Changes in one tag do not affect any other tag.
+- **Manual Control**: The user is always in control. There is no automatic switching. You facilitate switching by using `use-tag <name>`.
+- **Full CLI & MCP Support**: All tag management commands are available through both the CLI and MCP tools for you to use. Refer to [`taskmaster.mdc`](mdc:.cursor/rules/taskmaster.mdc) for a full command list.
 
-- **Data Structure**: Tasks are organized into separate contexts (tags) like "master", "feature-branch", or "v2.0"
-- **Seamless Migration**: Existing projects automatically migrate to use a "master" tag with zero disruption
-- **Backward Compatibility**: All existing commands continue to work exactly as before
-- **Context Isolation**: Tasks in different tags are completely separate and isolated
-- **Silent Migration**: The first time you run any Task Master command, your existing tasks.json will be automatically migrated to the new tagged format
-- **Migration Notice**: You'll see a friendly FYI notice after migration explaining the new system
-
-**Migration Example**:
-```json
-// Before (legacy format)
-{
-  "tasks": [
-    { "id": 1, "title": "Setup API", ... }
-  ]
-}
-
-// After (tagged format - automatic)
-{
-  "master": {
-    "tasks": [
-      { "id": 1, "title": "Setup API", ... }
-    ]
-  }
-}
-```
-
-**Tag Management**: CLI commands for tag management (`add-tag`, `use-tag`, `list-tags`, `delete-tag`, `rename-tag`, `copy-tag`) are now available with manual git integration via `--from-branch` option.
-
-## Standard Development Workflow Process
-
--   Start new projects by running `initialize_project` tool / `task-master init` or `parse_prd` / `task-master parse-prd --input='<prd-file.txt>'` (see [`taskmaster.mdc`](mdc:.cursor/rules/taskmaster.mdc)) to generate initial tasks.json with tagged structure
--   Begin coding sessions with `get_tasks` / `task-master list` (see [`taskmaster.mdc`](mdc:.cursor/rules/taskmaster.mdc)) to see current tasks, status, and IDs
--   Determine the next task to work on using `next_task` / `task-master next` (see [`taskmaster.mdc`](mdc:.cursor/rules/taskmaster.mdc)).
--   Analyze task complexity with `analyze_project_complexity` / `task-master analyze-complexity --research` (see [`taskmaster.mdc`](mdc:.cursor/rules/taskmaster.mdc)) before breaking down tasks
--   Review complexity report using `complexity_report` / `task-master complexity-report` (see [`taskmaster.mdc`](mdc:.cursor/rules/taskmaster.mdc)).
--   Select tasks based on dependencies (all marked 'done'), priority level, and ID order
--   Clarify tasks by checking task files in tasks/ directory or asking for user input
--   View specific task details using `get_task` / `task-master show <id>` (see [`taskmaster.mdc`](mdc:.cursor/rules/taskmaster.mdc)) to understand implementation requirements
--   Break down complex tasks using `expand_task` / `task-master expand --id=<id> --force --research` (see [`taskmaster.mdc`](mdc:.cursor/rules/taskmaster.mdc)) with appropriate flags like `--force` (to replace existing subtasks) and `--research`.
--   Clear existing subtasks if needed using `clear_subtasks` / `task-master clear-subtasks --id=<id>` (see [`taskmaster.mdc`](mdc:.cursor/rules/taskmaster.mdc)) before regenerating
--   Implement code following task details, dependencies, and project standards
--   Verify tasks according to test strategies before marking as complete (See [`tests.mdc`](mdc:.cursor/rules/tests.mdc))
--   Mark completed tasks with `set_task_status` / `task-master set-status --id=<id> --status=done` (see [`taskmaster.mdc`](mdc:.cursor/rules/taskmaster.mdc))
--   Update dependent tasks when implementation differs from original plan using `update` / `task-master update --from=<id> --prompt="..."` or `update_task` / `task-master update-task --id=<id> --prompt="..."` (see [`taskmaster.mdc`](mdc:.cursor/rules/taskmaster.mdc))
--   Add new tasks discovered during implementation using `add_task` / `task-master add-task --prompt="..." --research` (see [`taskmaster.mdc`](mdc:.cursor/rules/taskmaster.mdc)).
--   Add new subtasks as needed using `add_subtask` / `task-master add-subtask --parent=<id> --title="..."` (see [`taskmaster.mdc`](mdc:.cursor/rules/taskmaster.mdc)).
--   Append notes or details to subtasks using `update_subtask` / `task-master update-subtask --id=<subtaskId> --prompt='Add implementation notes here...\nMore details...'` (see [`taskmaster.mdc`](mdc:.cursor/rules/taskmaster.mdc)).
--   Generate task files with `generate` / `task-master generate` (see [`taskmaster.mdc`](mdc:.cursor/rules/taskmaster.mdc)) after updating tasks.json
--   Maintain valid dependency structure with `add_dependency`/`remove_dependency` tools or `task-master add-dependency`/`remove-dependency` commands, `validate_dependencies` / `task-master validate-dependencies`, and `fix_dependencies` / `task-master fix-dependencies` (see [`taskmaster.mdc`](mdc:.cursor/rules/taskmaster.mdc)) when needed
--   Respect dependency chains and task priorities when selecting work
--   Report progress regularly using `get_tasks` / `task-master list`
--   Reorganize tasks as needed using `move_task` / `task-master move --from=<id> --to=<id>` (see [`taskmaster.mdc`](mdc:.cursor/rules/taskmaster.mdc)) to change task hierarchy or ordering
+---
 
 ## Task Complexity Analysis
 

.cursor/rules/taskmaster.mdc

@@ -77,6 +77,7 @@ This document provides a detailed reference for interacting with Taskmaster, cov
     *   `--set-fallback <model_id>`: `Set the fallback model.`
     *   `--ollama`: `Specify that the provided model ID is for Ollama (use with --set-*).`
     *   `--openrouter`: `Specify that the provided model ID is for OpenRouter (use with --set-*). Validates against OpenRouter API.`
+    *   `--bedrock`: `Specify that the provided model ID is for AWS Bedrock (use with --set-*).`
     *   `--setup`: `Run interactive setup to configure models, including custom Ollama/OpenRouter IDs.`
 *   **Usage (MCP):** Call without set flags to get current config. Use `setMain`, `setResearch`, or `setFallback` with a valid model ID to update the configuration. Use `listAvailableModels: true` to get a list of unassigned models. To set a custom model, provide the model ID and set `ollama: true` or `openrouter: true`.
 *   **Usage (CLI):** Run without flags to view current configuration and available models. Use set flags to update specific roles. Use `--setup` for guided configuration, including custom models. To set a custom model via flags, use `--set-<role>=<model_id>` along with either `--ollama` or `--openrouter`.
@@ -108,6 +109,7 @@ This document provides a detailed reference for interacting with Taskmaster, cov
 *   **Description:** `Ask Taskmaster to show the next available task you can work on, based on status and completed dependencies.`
 *   **Key Parameters/Options:**
     *   `file`: `Path to your Taskmaster 'tasks.json' file. Default relies on auto-detection.` (CLI: `-f, --file <file>`)
+    *   `tag`: `Specify which tag context to use. Defaults to the current active tag.` (CLI: `--tag <name>`)
 *   **Usage:** Identify what to work on next according to the plan.
 
 ### 5. Get Task Details (`get_task`)
@@ -136,6 +138,7 @@ This document provides a detailed reference for interacting with Taskmaster, cov
     *   `dependencies`: `Specify the IDs of any Taskmaster tasks that must be completed before this new one can start, e.g., '12,14'.` (CLI: `-d, --dependencies <ids>`)
     *   `priority`: `Set the priority for the new task: 'high', 'medium', or 'low'. Default is 'medium'.` (CLI: `--priority <priority>`)
     *   `research`: `Enable Taskmaster to use the research role for potentially more informed task creation.` (CLI: `-r, --research`)
+    *   `tag`: `Specify which tag context to add the task to. Defaults to the current active tag.` (CLI: `--tag <name>`)
     *   `file`: `Path to your Taskmaster 'tasks.json' file. Default relies on auto-detection.` (CLI: `-f, --file <file>`)
 *   **Usage:** Quickly add newly identified tasks during development.
 *   **Important:** This MCP tool makes AI calls and can take up to a minute to complete. Please inform users to hang tight while the operation is in progress.
@@ -154,6 +157,7 @@ This document provides a detailed reference for interacting with Taskmaster, cov
     *   `dependencies`: `Specify IDs of other tasks or subtasks, e.g., '15' or '16.1', that must be done before this new subtask.` (CLI: `--dependencies <ids>`)
     *   `status`: `Set the initial status for the new subtask. Default is 'pending'.` (CLI: `-s, --status <status>`)
     *   `skipGenerate`: `Prevent Taskmaster from automatically regenerating markdown task files after adding the subtask.` (CLI: `--skip-generate`)
+    *   `tag`: `Specify which tag context to operate on. Defaults to the current active tag.` (CLI: `--tag <name>`)
     *   `file`: `Path to your Taskmaster 'tasks.json' file. Default relies on auto-detection.` (CLI: `-f, --file <file>`)
 *   **Usage:** Break down tasks manually or reorganize existing tasks.
 
@@ -166,6 +170,7 @@ This document provides a detailed reference for interacting with Taskmaster, cov
     *   `from`: `Required. The ID of the first task Taskmaster should update. All tasks with this ID or higher that are not 'done' will be considered.` (CLI: `--from <id>`)
     *   `prompt`: `Required. Explain the change or new context for Taskmaster to apply to the tasks, e.g., "We are now using React Query instead of Redux Toolkit for data fetching".` (CLI: `-p, --prompt <text>`)
     *   `research`: `Enable Taskmaster to use the research role for more informed updates. Requires appropriate API key.` (CLI: `-r, --research`)
+    *   `tag`: `Specify which tag context to operate on. Defaults to the current active tag.` (CLI: `--tag <name>`)
     *   `file`: `Path to your Taskmaster 'tasks.json' file. Default relies on auto-detection.` (CLI: `-f, --file <file>`)
 *   **Usage:** Handle significant implementation changes or pivots that affect multiple future tasks. Example CLI: `task-master update --from='18' --prompt='Switching to React Query.\nNeed to refactor data fetching...'`
 *   **Important:** This MCP tool makes AI calls and can take up to a minute to complete. Please inform users to hang tight while the operation is in progress.
@@ -191,12 +196,13 @@ This document provides a detailed reference for interacting with Taskmaster, cov
 *   **CLI Command:** `task-master update-subtask [options]`
 *   **Description:** `Append timestamped notes or details to a specific Taskmaster subtask without overwriting existing content. Intended for iterative implementation logging.`
 *   **Key Parameters/Options:**
-    *   `id`: `Required. The ID of the Taskmaster task, e.g., '5', or subtask, e.g., '5.2', to permanently remove.` (CLI: `-i, --id <id>`)
-    *   `yes`: `Skip the confirmation prompt and immediately delete the task.` (CLI: `-y, --yes`)
-    *   `tag`: `Specify which tag context to remove the task from. Defaults to the current active tag.` (CLI: `--tag <name>`)
+    *   `id`: `Required. The ID of the Taskmaster subtask, e.g., '5.2', to update with new information.` (CLI: `-i, --id <id>`)
+    *   `prompt`: `Required. The information, findings, or progress notes to append to the subtask's details with a timestamp.` (CLI: `-p, --prompt <text>`)
+    *   `research`: `Enable Taskmaster to use the research role for more informed updates. Requires appropriate API key.` (CLI: `-r, --research`)
+    *   `tag`: `Specify which tag context the subtask belongs to. Defaults to the current active tag.` (CLI: `--tag <name>`)
     *   `file`: `Path to your Taskmaster 'tasks.json' file. Default relies on auto-detection.` (CLI: `-f, --file <file>`)
-*   **Usage:** Permanently delete tasks or subtasks that are no longer needed in the project.
-*   **Notes:** Use with caution as this operation cannot be undone. Consider using 'blocked', 'cancelled', or 'deferred' status instead if you just want to exclude a task from active planning but keep it for reference. The command automatically cleans up dependency references in other tasks.
+*   **Usage:** Log implementation progress, findings, and discoveries during subtask development. Each update is timestamped and appended to preserve the implementation journey.
+*   **Important:** This MCP tool makes AI calls and can take up to a minute to complete. Please inform users to hang tight while the operation is in progress.
 
 ### 11. Set Task Status (`set_task_status`)
 
@@ -206,6 +212,7 @@ This document provides a detailed reference for interacting with Taskmaster, cov
 *   **Key Parameters/Options:**
     *   `id`: `Required. The ID(s) of the Taskmaster task(s) or subtask(s), e.g., '15', '15.2', or '16,17.1', to update.` (CLI: `-i, --id <id>`)
     *   `status`: `Required. The new status to set, e.g., 'done', 'pending', 'in-progress', 'review', 'cancelled'.` (CLI: `-s, --status <status>`)
+    *   `tag`: `Specify which tag context to operate on. Defaults to the current active tag.` (CLI: `--tag <name>`)
     *   `file`: `Path to your Taskmaster 'tasks.json' file. Default relies on auto-detection.` (CLI: `-f, --file <file>`)
 *   **Usage:** Mark progress as tasks move through the development cycle.
 
@@ -217,6 +224,7 @@ This document provides a detailed reference for interacting with Taskmaster, cov
 *   **Key Parameters/Options:**
     *   `id`: `Required. The ID of the Taskmaster task, e.g., '5', or subtask, e.g., '5.2', to permanently remove.` (CLI: `-i, --id <id>`)
     *   `yes`: `Skip the confirmation prompt and immediately delete the task.` (CLI: `-y, --yes`)
+    *   `tag`: `Specify which tag context to operate on. Defaults to the current active tag.` (CLI: `--tag <name>`)
     *   `file`: `Path to your Taskmaster 'tasks.json' file. Default relies on auto-detection.` (CLI: `-f, --file <file>`)
 *   **Usage:** Permanently delete tasks or subtasks that are no longer needed in the project.
 *   **Notes:** Use with caution as this operation cannot be undone. Consider using 'blocked', 'cancelled', or 'deferred' status instead if you just want to exclude a task from active planning but keep it for reference. The command automatically cleans up dependency references in other tasks.
@@ -264,6 +272,7 @@ This document provides a detailed reference for interacting with Taskmaster, cov
 *   **Key Parameters/Options:**
     *   `id`: `The ID(s) of the Taskmaster parent task(s) whose subtasks you want to remove, e.g., '15' or '16,18'. Required unless using `all`.) (CLI: `-i, --id <ids>`)
     *   `all`: `Tell Taskmaster to remove subtasks from all parent tasks.` (CLI: `--all`)
+    *   `tag`: `Specify which tag context to operate on. Defaults to the current active tag.` (CLI: `--tag <name>`)
     *   `file`: `Path to your Taskmaster 'tasks.json' file. Default relies on auto-detection.` (CLI: `-f, --file <file>`)
 *   **Usage:** Used before regenerating subtasks with `expand_task` if the previous breakdown needs replacement.
 
@@ -276,6 +285,7 @@ This document provides a detailed reference for interacting with Taskmaster, cov
     *   `id`: `Required. The ID(s) of the Taskmaster subtask(s) to remove, e.g., '15.2' or '16.1,16.3'.` (CLI: `-i, --id <id>`)
     *   `convert`: `If used, Taskmaster will turn the subtask into a regular top-level task instead of deleting it.` (CLI: `-c, --convert`)
     *   `skipGenerate`: `Prevent Taskmaster from automatically regenerating markdown task files after removing the subtask.` (CLI: `--skip-generate`)
+    *   `tag`: `Specify which tag context to operate on. Defaults to the current active tag.` (CLI: `--tag <name>`)
     *   `file`: `Path to your Taskmaster 'tasks.json' file. Default relies on auto-detection.` (CLI: `-f, --file <file>`)
 *   **Usage:** Delete unnecessary subtasks or promote a subtask to a top-level task.
 
@@ -287,6 +297,7 @@ This document provides a detailed reference for interacting with Taskmaster, cov
 *   **Key Parameters/Options:**
     *   `from`: `Required. ID of the task/subtask to move (e.g., "5" or "5.2"). Can be comma-separated for multiple tasks.` (CLI: `--from <id>`)
     *   `to`: `Required. ID of the destination (e.g., "7" or "7.3"). Must match the number of source IDs if comma-separated.` (CLI: `--to <id>`)
+    *   `tag`: `Specify which tag context to operate on. Defaults to the current active tag.` (CLI: `--tag <name>`)
     *   `file`: `Path to your Taskmaster 'tasks.json' file. Default relies on auto-detection.` (CLI: `-f, --file <file>`)
 *   **Usage:** Reorganize tasks by moving them within the hierarchy. Supports various scenarios like:
     *   Moving a task to become a subtask
@@ -316,6 +327,7 @@ This document provides a detailed reference for interacting with Taskmaster, cov
 *   **Key Parameters/Options:**
     *   `id`: `Required. The ID of the Taskmaster task that will depend on another.` (CLI: `-i, --id <id>`)
     *   `dependsOn`: `Required. The ID of the Taskmaster task that must be completed first, the prerequisite.` (CLI: `-d, --depends-on <id>`)
+    *   `tag`: `Specify which tag context to operate on. Defaults to the current active tag.` (CLI: `--tag <name>`)
     *   `file`: `Path to your Taskmaster 'tasks.json' file. Default relies on auto-detection.` (CLI: `-f, --file <path>`)
 *   **Usage:** Establish the correct order of execution between tasks.
 
@@ -327,6 +339,7 @@ This document provides a detailed reference for interacting with Taskmaster, cov
 *   **Key Parameters/Options:**
     *   `id`: `Required. The ID of the Taskmaster task you want to remove a prerequisite from.` (CLI: `-i, --id <id>`)
     *   `dependsOn`: `Required. The ID of the Taskmaster task that should no longer be a prerequisite.` (CLI: `-d, --depends-on <id>`)
+    *   `tag`: `Specify which tag context to operate on. Defaults to the current active tag.` (CLI: `--tag <name>`)
     *   `file`: `Path to your Taskmaster 'tasks.json' file. Default relies on auto-detection.` (CLI: `-f, --file <file>`)
 *   **Usage:** Update task relationships when the order of execution changes.
 
@@ -336,6 +349,7 @@ This document provides a detailed reference for interacting with Taskmaster, cov
 *   **CLI Command:** `task-master validate-dependencies [options]`
 *   **Description:** `Check your Taskmaster tasks for dependency issues (like circular references or links to non-existent tasks) without making changes.`
 *   **Key Parameters/Options:**
+    *   `tag`: `Specify which tag context to validate. Defaults to the current active tag.` (CLI: `--tag <name>`)
     *   `file`: `Path to your Taskmaster 'tasks.json' file. Default relies on auto-detection.` (CLI: `-f, --file <file>`)
 *   **Usage:** Audit the integrity of your task dependencies.
 
@@ -373,6 +387,7 @@ This document provides a detailed reference for interacting with Taskmaster, cov
 *   **CLI Command:** `task-master complexity-report [options]`
 *   **Description:** `Display the task complexity analysis report in a readable format.`
 *   **Key Parameters/Options:**
+    *   `tag`: `Specify which tag context to show the report for. Defaults to the current active tag.` (CLI: `--tag <name>`)
     *   `file`: `Path to the complexity report (default: '.taskmaster/reports/task-complexity-report.json').` (CLI: `-f, --file <file>`)
 *   **Usage:** Review and understand the complexity analysis results after running analyze-complexity.
 
@@ -444,6 +459,7 @@ This new suite of commands allows you to manage different task contexts (tags).
 *   **CLI Command:** `task-master tags [options]`
 *   **Description:** `List all available tags with task counts, completion status, and other metadata.`
 *   **Key Parameters/Options:**
+    *   `file`: `Path to your Taskmaster 'tasks.json' file. Default relies on auto-detection.` (CLI: `-f, --file <file>`)
     *   `--show-metadata`: `Include detailed metadata in the output (e.g., creation date, description).` (CLI: `--show-metadata`)
 
 ### 27. Add Tag (`add_tag`)
@@ -457,6 +473,7 @@ This new suite of commands allows you to manage different task contexts (tags).
     *   `--copy-from-current`: `Copy tasks from the currently active tag to the new tag.` (CLI: `--copy-from-current`)
     *   `--copy-from <tag>`: `Copy tasks from a specific source tag to the new tag.` (CLI: `--copy-from <tag>`)
     *   `--description <text>`: `Provide an optional description for the new tag.` (CLI: `-d, --description <text>`)
+    *   `file`: `Path to your Taskmaster 'tasks.json' file. Default relies on auto-detection.` (CLI: `-f, --file <file>`)
 
 ### 28. Delete Tag (`delete_tag`)
 
@@ -466,6 +483,7 @@ This new suite of commands allows you to manage different task contexts (tags).
 *   **Key Parameters/Options:**
     *   `tagName`: `Name of the tag to delete.` (CLI: `<tagName>` positional)
     *   `--yes`: `Skip the confirmation prompt.` (CLI: `-y, --yes`)
+    *   `file`: `Path to your Taskmaster 'tasks.json' file. Default relies on auto-detection.` (CLI: `-f, --file <file>`)
 
 ### 29. Use Tag (`use_tag`)
 
@@ -474,6 +492,7 @@ This new suite of commands allows you to manage different task contexts (tags).
 *   **Description:** `Switch your active task context to a different tag.`
 *   **Key Parameters/Options:**
     *   `tagName`: `Name of the tag to switch to.` (CLI: `<tagName>` positional)
+    *   `file`: `Path to your Taskmaster 'tasks.json' file. Default relies on auto-detection.` (CLI: `-f, --file <file>`)
 
 ### 30. Rename Tag (`rename_tag`)
 
@@ -483,6 +502,7 @@ This new suite of commands allows you to manage different task contexts (tags).
 *   **Key Parameters/Options:**
     *   `oldName`: `The current name of the tag.` (CLI: `<oldName>` positional)
     *   `newName`: `The new name for the tag.` (CLI: `<newName>` positional)
+    *   `file`: `Path to your Taskmaster 'tasks.json' file. Default relies on auto-detection.` (CLI: `-f, --file <file>`)
 
 ### 31. Copy Tag (`copy_tag`)
 

.taskmaster/docs/research/2025-06-13_what-is-typescript.md

@@ -1,42 +0,0 @@
----
-title: Research Session
-query: "What is TypeScript?"
-date: 6/13/2025
-time: 3:07:41 PM
-timestamp: 2025-06-13T19:07:41.313Z
-exchanges: 2
----
-
-# Research Session
-
-**Query:** What is TypeScript?  
-**Date:** 6/13/2025 3:07:41 PM  
-**Exchanges:** 2
-
----
-
-## Initial Query
-
-**Question:** What is TypeScript?
-
-**Response:**
-
-TypeScript is a strongly typed, object-oriented programming language that builds on JavaScript by adding static typing and type annotations. It is a syntactic superset of JavaScript, meaning all JavaScript code is valid TypeScript, but TypeScript adds extra syntax to specify types, enabling compile-time type checking and better tooling support. This helps catch errors early before running the code and improves code quality, especially in large-scale applications. TypeScript code is transpiled to plain JavaScript, which can run anywhere JavaScript runs, such as browsers, Node.js, or Deno. It is developed and maintained by Microsoft as open-source software under the Apache 2.0 license[1][2][3][4][5].
-
----
-
-## Follow-up 1
-
-**Question:** And why is the sky blue?
-
-**Response:**
-
-- The sky appears blue because sunlight interacts with Earth's atmosphere, and the shorter wavelengths of light (blue and violet) are scattered in all directions by air molecules—a process called Rayleigh scattering[1][2][3][5].
-- Blue light is scattered more than red light because it has a shorter wavelength, making the sky look blue to our eyes during the day[2][3][5].
-- If Earth's atmosphere didn't scatter sunlight, the sky would appear dark, as it does on the Moon, which lacks an atmosphere[5].
-
-
----
-
-*Generated by Task Master Research Command*  
-*Timestamp: 2025-06-13T19:07:41.313Z*

.taskmaster/docs/research/2025-06-14_how-can-i-improve-the-scope-up-and-scope-down-comm.md

@@ -0,0 +1,128 @@
+---
+title: Research Session
+query: "how can i improve the scope-up and scope-down command"
+date: 6/14/2025
+time: 4:35:03 PM
+timestamp: 2025-06-14T20:35:03.231Z
+exchanges: 2
+---
+
+# Research Session
+
+## Initial Query
+
+**Question:** how can i improve the scope-up and scope-down command
+
+**Response:**
+
+## Improving the `scope-up` and `scope-down` Commands
+
+**Clarify Command Purpose and User Experience**
+
+- Ensure the commands have clear, intuitive behavior. For example, `scope-up` should consistently broaden the context or task view, while `scope-down` should reliably narrow it.
+- Provide immediate, user-friendly feedback after each command, indicating what changed (e.g., "Now viewing parent task and all subtasks" or "Focused on subtask: X").
+- Document the commands with examples in your `docs/command-reference.md` and `docs/examples.md` to help users understand their effects and use cases.
+
+**Enhance Context Awareness**
+
+- Make the commands context-sensitive: if the user is already at the top or bottom of the scope hierarchy, return a helpful message instead of failing silently.
+- Allow optional arguments to specify the exact level or target (e.g., `scope-up 2` to move up two levels, or `scope-down <subtask-id>` to jump directly to a subtask).
+
+**Robust Error Handling and Validation**
+
+- Implement checks to prevent invalid operations, such as attempting to scope up from the root or scope down when no subtasks exist.
+- Provide clear error messages and suggestions for next steps, improving user trust and reducing confusion[1][5].
+
+**Integrate with Task and Tag Systems**
+
+- Ensure `scope-up` and `scope-down` interact smoothly with your tagging and task hierarchy features. For example, scoping up from a subtask should show the parent task and its context, while scoping down should allow selection from available subtasks or related tags.
+- Consider supporting batch operations, such as scoping down into all subtasks and displaying them in a summarized view.
+
+**Improve Performance and Synchronization**
+
+- Optimize the underlying logic to minimize delays, especially in large task trees. Use asynchronous operations where possible to keep the UI responsive.
+- If the commands trigger data loading or context switching, ensure synchronization so that subsequent commands operate on the correct, updated context[2][4].
+
+**Testing and Stakeholder Feedback**
+
+- Add or expand unit and integration tests for these commands (see `tests/unit/commands.test.js` and `integration/cli/commands.test.js`) to cover edge cases and ensure reliability.
+- Gather feedback from users and stakeholders to identify pain points and desired enhancements, then iterate on the command design and implementation[1][5].
+
+**Example Improvements Table**
+
+| Area                | Current Issue                | Suggested Improvement                        |
+|---------------------|-----------------------------|----------------------------------------------|
+| User Feedback       | Minimal or unclear output    | Add explicit, contextual messages            |
+| Error Handling      | Silent failures              | Informative errors and recovery suggestions  |
+| Flexibility         | Only single-level movement   | Support multi-level and targeted navigation  |
+| Integration         | Limited context awareness    | Sync with tags, parent/child relationships   |
+| Performance         | Slow on large hierarchies    | Optimize data access and UI updates          |
+
+By focusing on these areas, you can make `scope-up` and `scope-down` more robust, user-friendly, and aligned with best practices in scope management and command design[1][5].
+
+---
+
+## Follow-up 1
+
+**Question:** how might i do this relative to the tag system?
+
+**Response:**
+
+## Integrating Scope-Up and Scope-Down with the Tag System
+
+**Conceptual Mapping**
+
+- In your project, *scope-up* and *scope-down* commands currently operate on the task hierarchy, broadening or narrowing the context by moving between parent and child tasks.
+- The tag system provides a parallel, orthogonal way to group and filter tasks—tags can represent categories, priorities, or any custom grouping, independent of strict parent/child relationships.
+
+**How to Make Scope Commands Tag-Aware**
+
+- **Scoping by Tag**: Allow users to "scope-down" into a tag, viewing only tasks associated with that tag. Conversely, "scope-up" could move from a specific tag context back to the broader task list or to a parent tag grouping if you support tag hierarchies.
+- **Tag-Scoped Views**: When a tag is active as the current scope, all navigation and operations (listing, editing, etc.) are limited to tasks with that tag. This is similar to how some systems let you set the "Tag Scope" to filter navigation and search to only tagged items[1][5].
+- **Combining Hierarchy and Tags**: Enable compound scoping, such as "all subtasks of Task X that also have Tag Y." This can be implemented by intersecting the results of hierarchical and tag-based queries.
+
+**Implementation Strategies**
+
+- **Scope Stack or Context Object**: Maintain a stack or context object that tracks both the current task scope and any active tag filters. Each scope change (up/down or tag in/out) updates this context.
+- **Commands**:
+  - `scope-down --tag <tag>`: Narrows the view to tasks with the specified tag.
+  - `scope-up --tag`: Removes the tag filter, broadening the view.
+  - `scope-down <subtask-id> --tag <tag>`: Narrows to a specific subtask *and* applies a tag filter.
+- **Tag Hierarchies (Optional)**: If your tag system supports parent/child tags or tag groups, allow "scope-up" to move from a specific tag to its parent tag or group, and "scope-down" to move into a child tag[4][5].
+
+**Example User Flows**
+
+- *Scoping Down by Tag*:  
+  User runs `scope-down --tag urgent` → Only tasks tagged "urgent" are shown.
+- *Combining Task and Tag*:  
+  User runs `scope-down <task-id> --tag frontend` → Only subtasks of `<task-id>` that are tagged "frontend" are shown.
+- *Scoping Up from Tag*:  
+  User runs `scope-up --tag` → Removes the tag filter, returning to the previous broader context.
+
+**Technical Considerations**
+
+- **Efficient Filtering**: Use indexed queries or in-memory filtering to efficiently combine tag and hierarchy filters, especially for large task sets.
+- **Feedback and UI**: Always display the current scope context (e.g., "Viewing tasks tagged 'urgent' under 'Feature X'") so users understand what they're seeing.
+- **Extensibility**: Design the scope system so new types of scopes (e.g., by status, assignee) can be added in the future, not just tags and hierarchy.
+
+**Relevant Precedents**
+
+- Tag-based file systems and management tools often implement "scopes" as dynamic groups defined by tag criteria, allowing users to build up complex views by combining tags and other filters[5].
+- Some systems allow scoping into tag management itself, where you can create, edit, or view tags and their associated objects, which could be mirrored in your CLI or UI[4].
+
+**Summary Table**
+
+| Command Example                  | Resulting Scope                                  |
+|----------------------------------|--------------------------------------------------|
+| `scope-down --tag bug`           | All tasks tagged "bug"                           |
+| `scope-down <task-id> --tag api` | Subtasks of `<task-id>` tagged "api"             |
+| `scope-up --tag`                 | Removes tag filter, returns to previous scope    |
+| `scope-down --tag frontend`      | All tasks tagged "frontend"                      |
+
+By integrating tag-based scoping, you make your scope commands more flexible and powerful, supporting both hierarchical and ad-hoc organizational strategies[1][5].
+
+
+---
+
+*Generated by Task Master Research Command*  
+*Timestamp: 2025-06-14T20:35:03.231Z*

.taskmaster/docs/research/2025-06-14_should-i-be-using-any-specific-libraries-for-this.md

@@ -0,0 +1,158 @@
+---
+title: Research Session
+query: "should i be using any specific libraries for this?"
+date: 6/14/2025
+time: 5:20:00 PM
+timestamp: 2025-06-14T21:20:00.561Z
+exchanges: 2
+---
+
+# Research Session
+
+## Initial Query
+
+**Question:** should i be using any specific libraries for this?
+
+**Response:**
+
+HELL YEAH PARTNER
+
+For implementing a GitHub Issue export feature with bidirectional linking in your project, you absolutely should use a dedicated library for interacting with the GitHub API. This will save you a ton of time, reduce boilerplate, and help you avoid common pitfalls with authentication, pagination, and error handling.
+
+## Recommended Library: PyGithub
+
+- **PyGithub** is the most widely used and well-documented Python library for accessing the GitHub REST API v3. It allows you to manage repositories, issues, user profiles, and more, all with a clean, object-oriented interface[1][2][3][5].
+- It supports all the operations you’ll need for your export feature, including creating issues, updating them, and managing references for bidirectional linking.
+
+### Key Features
+
+- **Authentication**: Easily authenticate with a personal access token.
+- **Issue Management**: Create, update, and link issues programmatically.
+- **Repository Access**: Fetch and manipulate repository data.
+- **User/Org Support**: Works for both user and organization repos.
+- **Pagination & Rate Limiting**: Handles these for you.
+
+### Example Usage
+
+```python
+from github import Github, Auth
+
+# Authenticate with a personal access token
+auth = Auth.Token("your_github_token")
+g = Github(auth=auth)
+
+# Get the repo
+repo = g.get_repo("owner/repo_name")
+
+# Create a new issue
+issue = repo.create_issue(
+    title="Exported from Task Master",
+    body="This issue was created by Task Master. [Task ID: 123]"
+)
+
+# Add a comment or update the issue to include a backlink
+issue.create_comment("Linked to Task Master task #123")
+```
+[3][5]
+
+## Why Not Use Raw Requests?
+
+- While you *can* use the `requests` library to call the GitHub API directly[4], PyGithub abstracts away authentication, error handling, and pagination, making your code much cleaner and less error-prone[2][5].
+
+## Integration Tips
+
+- Store your GitHub token securely (e.g., in environment variables).
+- Use PyGithub’s objects to fetch, create, and update issues.
+- For bidirectional linking, store the GitHub issue URL in your task data and the Task Master task ID in the GitHub issue body or as a label/comment.
+- PyGithub is actively maintained and widely used, so you’ll find plenty of support and documentation.
+
+## Installation
+
+```bash
+pip install PyGithub
+```
+[3]
+
+## Summary Table
+
+| Library   | Language | API Coverage | Ease of Use | Maintained | Docs/Support |
+|-----------|----------|--------------|-------------|------------|--------------|
+| PyGithub  | Python   | Full         | High        | Yes        | Excellent    |
+| requests  | Python   | Full (manual)| Medium      | Yes        | Good         |
+
+**Use PyGithub for all GitHub API interactions in your export/import features.** It’s the standard for Python projects and will make your implementation faster, safer, and more maintainable[1][2][3][5].
+
+---
+
+## Follow-up 1
+
+**Question:** we don't want to use py github because we have a node project
+
+**Response:**
+
+HELL YEAH PARTNER
+
+For a Node.js project, you should use a Node-native library to interact with the GitHub API instead of PyGithub, which is Python-only. The industry standard for Node.js is **Octokit**, the official GitHub SDK for JavaScript/TypeScript[1][2].
+
+## Why Use Octokit?
+
+- **Official & Complete**: Octokit is maintained by GitHub and covers all REST and GraphQL API endpoints, including issues, repositories, users, and more[1][2].
+- **Universal**: Works in Node.js, browsers, and Deno environments[2].
+- **Typed & Tested**: Comes with TypeScript declarations and 100% test coverage[2].
+- **Authentication**: Supports personal access tokens, GitHub Apps, OAuth, and more.
+- **Pagination & Error Handling**: Handles pagination and common error scenarios out of the box.
+- **Extendable**: Supports plugins and custom hooks for advanced use cases[2].
+
+## How to Use Octokit for GitHub Issue Export
+
+Install Octokit in your Node.js project:
+
+```bash
+npm install @octokit/rest
+```
+
+Basic usage for creating and linking issues:
+
+```js
+const { Octokit } = require("@octokit/rest");
+
+// Authenticate with a personal access token
+const octokit = new Octokit({ auth: process.env.GITHUB_TOKEN });
+
+// Create a new issue
+const { data: issue } = await octokit.issues.create({
+  owner: "owner",
+  repo: "repo_name",
+  title: "Exported from Task Master",
+  body: "This issue was created by Task Master. [Task ID: 123]"
+});
+
+// Add a comment for bidirectional linking
+await octokit.issues.createComment({
+  owner: "owner",
+  repo: "repo_name",
+  issue_number: issue.number,
+  body: "Linked to Task Master task #123"
+});
+```
+
+## Alternatives
+
+- **node-github**: An older library, less maintained than Octokit, but still functional for basic API access[5].
+- **Raw HTTP Requests**: You can use `node-fetch` or `axios` to call the GitHub API directly, but you’ll need to handle authentication, pagination, and error handling yourself[3]. Octokit abstracts all of this for you.
+
+## Summary Table
+
+| Library         | Language | API Coverage | Maintained | TypeScript | Docs/Support |
+|-----------------|----------|--------------|------------|------------|--------------|
+| Octokit         | Node.js  | Full         | Yes        | Yes        | Excellent    |
+| node-github     | Node.js  | Full         | No         | No         | Limited      |
+| Raw HTTP        | Node.js  | Full (manual)| N/A        | N/A        | N/A          |
+
+**Recommendation:** Use Octokit for all GitHub API interactions in your Node.js project. It’s the official, most robust, and best-supported option for your use case[1][2].
+
+
+---
+
+*Generated by Task Master Research Command*  
+*Timestamp: 2025-06-14T21:20:00.561Z*

.taskmaster/docs/research/2025-06-14_test-save-functionality.md

@@ -0,0 +1,76 @@
+---
+title: Research Session
+query: "test save functionality"
+date: 6/14/2025
+time: 5:50:23 PM
+timestamp: 2025-06-14T21:50:23.797Z
+exchanges: 1
+---
+
+# Research Session
+
+## Initial Query
+
+**Question:** test save functionality
+
+**Response:**
+
+## Testing Save Functionality in a Task Management System
+
+**Core Steps for Testing Save Functionality**
+
+- Create or update a task in the system using the CLI or UI.
+- Trigger the save operation (e.g., by issuing a command or clicking a save button).
+- Verify that the data is correctly written to the persistent storage (e.g., `tasks.json`).
+- Reload or re-query the data to ensure the saved changes persist and are accurately reflected.
+- Validate that all required fields and relationships (such as dependencies and subtasks) are preserved and correctly structured.
+
+**Key Test Scenarios**
+
+- **Basic Save:** Add a new task and confirm it appears in `tasks.json` with all fields populated.
+- **Update Save:** Modify an existing task (e.g., change status, description, or priority) and verify the changes are saved.
+- **Subtask and Dependency Preservation:** Update a parent task and ensure that completed subtasks and dependency links remain intact, especially after using commands like `updateTask`.
+- **Batch Operations:** Perform bulk updates or additions and confirm all affected tasks are saved correctly, with no data loss or corruption.
+- **Validation:** Attempt to save invalid data and ensure the system rejects it or provides meaningful error messages, confirming validation logic is enforced.
+
+**Recommended Practices**
+
+- Use automated tests to simulate save operations for various scenarios, including edge cases (e.g., circular dependencies, missing required fields).
+- After each save, reload the data and compare it to the expected state to ensure integrity.
+- Log all save operations and errors for traceability and debugging.
+- Regularly back up the `tasks.json` file to prevent data loss during testing and development.
+
+**Relevant Features from Industry Standards**
+
+- Task management systems typically provide robust save and update mechanisms, ensuring that all task attributes (including dependencies, subtasks, and comments) are consistently maintained[1][2][5].
+- Validation and error handling are critical to prevent corrupt or incomplete saves, especially when handling complex relationships or batch operations[1][5].
+- User feedback (such as success messages or error alerts) is important for confirming save actions and guiding users in case of issues[1][2].
+
+**Example Test Case**
+
+1. Create a task with subtasks and dependencies.
+2. Mark some subtasks as complete.
+3. Use the `updateTask` command to modify the parent task.
+4. Save and reload the data.
+5. Assert that:
+   - The parent task reflects the updates.
+   - Completed subtasks remain marked as complete.
+   - Dependencies are unchanged and valid.
+
+**Summary Table: Save Functionality Test Aspects**
+
+| Aspect                | What to Test                                      | Expected Outcome                        |
+|-----------------------|---------------------------------------------------|-----------------------------------------|
+| Basic Save            | Add/update task, save, reload                     | Data persists and matches expectations  |
+| Subtask Preservation  | Update parent, check subtask status               | Completed subtasks remain complete      |
+| Dependency Handling   | Save with dependencies, reload                    | Dependencies are intact and valid       |
+| Batch Operations      | Bulk save/update, reload                          | All changes persist, no data loss       |
+| Validation            | Save invalid data                                 | Error is raised, data not corrupted     |
+
+These steps and scenarios ensure that the save functionality is robust, reliable, and meets the requirements of a modern task management system[1][2][5].
+
+
+---
+
+*Generated by Task Master Research Command*  
+*Timestamp: 2025-06-14T21:50:23.797Z*

.taskmaster/docs/research/2025-06-14_test-the-fix-for-duplicate-saves-final-test.md

@@ -0,0 +1,81 @@
+---
+title: Research Session
+query: "test the fix for duplicate saves - final test"
+date: 6/14/2025
+time: 6:10:00 PM
+timestamp: 2025-06-14T22:10:00.394Z
+exchanges: 1
+---
+
+# Research Session
+
+## Initial Query
+
+**Question:** test the fix for duplicate saves - final test
+
+**Response:**
+
+## Steps to Test the Fix for Duplicate Saves
+
+**1. Prepare a Clean Test Environment**
+- Ensure the tasks.json file and any related data stores are in a known, clean state with no pre-existing duplicate entries.
+- Back up the current tasks.json in case rollback is needed.
+
+**2. Define Test Scenarios**
+- Attempt to save a new task with unique data.
+- Attempt to save a task with the same ID or unique identifier as an existing task (simulate a duplicate).
+- Attempt to save a task with the same title or content but a different ID (to test if the fix is based on ID or content).
+- Simultaneously trigger multiple save operations (if the system supports concurrency) to test race conditions.
+
+**3. Execute Manual and Automated Tests**
+- Use the application's UI or API to create and save tasks as per the scenarios above.
+- For each save operation, check the tasks.json file or the data store to verify:
+  - No duplicate entries are created.
+  - Existing tasks are not overwritten unless intended (e.g., for updates).
+  - The system returns appropriate error messages or warnings when a duplicate save is attempted.
+
+**4. Validate System Behavior**
+- Confirm that after all test operations, each task in tasks.json is unique according to the defined criteria (ID, title, or other unique fields).
+- If the system is designed to merge duplicates, verify that merging occurs as expected.
+- If the system is designed to reject duplicates, ensure that the rejection is clear and no duplicate is present.
+
+**5. Test Edge Cases**
+- Attempt to save tasks with minor variations (e.g., whitespace differences, case sensitivity) to ensure the duplicate detection logic is robust.
+- Test with large numbers of tasks to ensure performance and correctness at scale.
+
+**6. Review Logs and Error Handling**
+- Check application logs for any errors or warnings related to duplicate saves.
+- Ensure that error handling is user-friendly and provides actionable feedback.
+
+**7. Regression Testing**
+- Run the full suite of task operations (create, update, delete) to ensure the fix for duplicate saves does not introduce new issues elsewhere in the system.
+
+## Additional Best Practices
+
+- Communicate test results with the team to confirm the fix is effective and to prevent future regressions[1][2][5].
+- Consider implementing automated duplicate detection as part of the save operation to prevent future issues[2][3].
+- Document the test cases and results for future reference and audits.
+
+## Example Test Case Table
+
+| Test Scenario                        | Expected Result                | Actual Result | Pass/Fail |
+|--------------------------------------|-------------------------------|---------------|-----------|
+| Save unique task                     | Task saved                    |               |           |
+| Save duplicate task (same ID)        | Duplicate rejected/merged     |               |           |
+| Save duplicate task (same title)     | Duplicate rejected/merged     |               |           |
+| Simultaneous saves (race condition)  | Only one unique task present  |               |           |
+| Save with minor variations           | No false positives/negatives  |               |           |
+
+Fill in the "Actual Result" and "Pass/Fail" columns during testing.
+
+## Action Items
+
+- Complete all test scenarios above.
+- Document any issues found and retest after fixes.
+- Confirm with stakeholders before closing the issue.
+
+
+---
+
+*Generated by Task Master Research Command*  
+*Timestamp: 2025-06-14T22:10:00.394Z*

.taskmaster/docs/task-template-importing-prd.txt

@@ -0,0 +1,471 @@
+# Task Template Importing System - Product Requirements Document
+
+<context>
+# Overview  
+The Task Template Importing system enables seamless integration of external task templates into the Task Master CLI through automatic file discovery. This system allows users to drop task template files into the tasks directory and immediately access them as new tag contexts without manual import commands or configuration. The solution addresses the need for multi-project task management, team collaboration through shared templates, and clean separation between permanent tasks and temporary project contexts.
+
+# Core Features  
+## Silent Task Template Discovery
+- **What it does**: Automatically scans for `tasks_*.json` files in the tasks directory during tag operations
+- **Why it's important**: Eliminates friction in adding new task contexts and enables zero-configuration workflow
+- **How it works**: File pattern matching extracts tag names from filenames and validates against internal tag keys
+
+## External Tag Resolution System
+- **What it does**: Provides fallback mechanism to external files when tags are not found in main tasks.json
+- **Why it's important**: Maintains clean separation between core tasks and project-specific templates
+- **How it works**: Tag resolution logic checks external files as secondary source while preserving main file precedence
+
+## Read-Only External Tag Access
+- **What it does**: Allows viewing and switching to external tags while preventing modifications
+- **Why it's important**: Protects template integrity and prevents accidental changes to shared templates
+- **How it works**: All task modifications route to main tasks.json regardless of current tag context
+
+## Tag Precedence Management
+- **What it does**: Ensures main tasks.json tags override external files with same tag names
+- **Why it's important**: Prevents conflicts and maintains data integrity
+- **How it works**: Priority system where main file tags take precedence over external file tags
+
+# User Experience  
+## User Personas
+- **Solo Developer**: Manages multiple projects with different task contexts
+- **Team Lead**: Shares standardized task templates across team members
+- **Project Manager**: Organizes tasks by project phases or feature branches
+
+## Key User Flows
+### Template Addition Flow
+1. User receives or creates a `tasks_projectname.json` file
+2. User drops file into `.taskmaster/tasks/` directory
+3. Tag becomes immediately available via `task-master use-tag projectname`
+4. User can list, view, and switch to external tag without configuration
+
+### Template Usage Flow
+1. User runs `task-master tags` to see available tags including external ones
+2. External tags display with `(imported)` indicator
+3. User switches to external tag with `task-master use-tag projectname`
+4. User can view tasks but modifications are routed to main tasks.json
+
+## UI/UX Considerations
+- External tags clearly marked with `(imported)` suffix in listings
+- Visual indicators distinguish between main and external tags
+- Error messages guide users when external files are malformed
+- Read-only warnings when attempting to modify external tag contexts
+</context>
+
+<PRD>
+# Technical Architecture  
+## System Components
+1. **External File Discovery Engine**
+   - File pattern scanner for `tasks_*.json` files
+   - Tag name extraction from filenames using regex
+   - Dynamic tag registry combining main and external sources
+   - Error handling for malformed external files
+
+2. **Enhanced Tag Resolution System**
+   - Fallback mechanism to external files when tags not found in main tasks.json
+   - Precedence management ensuring main file tags override external files
+   - Read-only access enforcement for external tags
+   - Tag metadata preservation during discovery operations
+
+3. **Silent Discovery Integration**
+   - Automatic scanning during tag-related operations
+   - Seamless integration with existing tag management functions
+   - Zero-configuration workflow requiring no manual import commands
+   - Dynamic tag availability without restart requirements
+
+## Data Models
+
+### External Task File Structure
+```json
+{
+  "meta": {
+    "projectName": "External Project Name",
+    "version": "1.0.0",
+    "templateSource": "external",
+    "createdAt": "ISO-8601 timestamp"
+  },
+  "tags": {
+    "projectname": {
+      "meta": {
+        "name": "Project Name",
+        "description": "Project description",
+        "createdAt": "ISO-8601 timestamp"
+      },
+      "tasks": [
+        // Array of task objects
+      ]
+    },
+    "master": {
+      // This section is ignored to prevent conflicts
+    }
+  }
+}
+```
+
+### Enhanced Tag Registry Model
+```json
+{
+  "mainTags": [
+    {
+      "name": "master",
+      "source": "main",
+      "taskCount": 150,
+      "isActive": true
+    }
+  ],
+  "externalTags": [
+    {
+      "name": "projectname",
+      "source": "external",
+      "filename": "tasks_projectname.json",
+      "taskCount": 25,
+      "isReadOnly": true
+    }
+  ]
+}
+```
+
+## APIs and Integrations
+1. **File System Discovery API**
+   - Directory scanning with pattern matching
+   - JSON file validation and parsing
+   - Error handling for corrupted or malformed files
+   - File modification time tracking for cache invalidation
+
+2. **Enhanced Tag Management API**
+   - `scanForExternalTaskFiles(projectRoot)` - Discover external template files
+   - `getExternalTagsFromFiles(projectRoot)` - Extract tag names from external files
+   - `readExternalTagData(projectRoot, tagName)` - Read specific external tag data
+   - `getAvailableTags(projectRoot)` - Combined main and external tag listing
+
+3. **Tag Resolution Enhancement**
+   - Modified `readJSON()` with external file fallback
+   - Enhanced `tags()` function with external tag display
+   - Updated `useTag()` function supporting external tag switching
+   - Read-only enforcement for external tag operations
+
+## Infrastructure Requirements
+1. **File System Access**
+   - Read permissions for tasks directory
+   - JSON parsing capabilities
+   - Pattern matching and regex support
+   - Error handling for file system operations
+
+2. **Backward Compatibility**
+   - Existing tag operations continue unchanged
+   - Main tasks.json structure preserved
+   - No breaking changes to current workflows
+   - Graceful degradation when external files unavailable
+
+# Development Roadmap  
+## Phase 1: Core External File Discovery (Foundation)
+1. **External File Scanner Implementation**
+   - Create `scanForExternalTaskFiles()` function in utils.js
+   - Implement file pattern matching for `tasks_*.json` files
+   - Add error handling for file system access issues
+   - Test with various filename patterns and edge cases
+
+2. **Tag Name Extraction System**
+   - Implement `getExternalTagsFromFiles()` function
+   - Create regex pattern for extracting tag names from filenames
+   - Add validation to ensure tag names match internal tag key format
+   - Handle special characters and invalid filename patterns
+
+3. **External Tag Data Reader**
+   - Create `readExternalTagData()` function
+   - Implement JSON parsing with error handling
+   - Add validation for required tag structure
+   - Ignore 'master' key in external files to prevent conflicts
+
+## Phase 2: Tag Resolution Enhancement (Core Integration)
+1. **Enhanced Tag Registry**
+   - Implement `getAvailableTags()` function combining main and external sources
+   - Create tag metadata structure including source information
+   - Add deduplication logic prioritizing main tags over external
+   - Implement caching mechanism for performance optimization
+
+2. **Modified readJSON Function**
+   - Add external file fallback when tag not found in main tasks.json
+   - Maintain precedence rule: main tasks.json overrides external files
+   - Preserve existing error handling and validation patterns
+   - Ensure read-only access for external tags
+
+3. **Tag Listing Enhancement**
+   - Update `tags()` function to display external tags with `(imported)` indicator
+   - Show external tag metadata and task counts
+   - Maintain current tag highlighting and sorting functionality
+   - Add visual distinction between main and external tags
+
+## Phase 3: User Interface Integration (User Experience)
+1. **Tag Switching Enhancement**
+   - Update `useTag()` function to support external tag switching
+   - Add read-only warnings when switching to external tags
+   - Update state.json with external tag context information
+   - Maintain current tag switching behavior for main tags
+
+2. **Error Handling and User Feedback**
+   - Implement comprehensive error messages for malformed external files
+   - Add user guidance for proper external file structure
+   - Create warnings for read-only operations on external tags
+   - Ensure graceful degradation when external files are corrupted
+
+3. **Documentation and Help Integration**
+   - Update command help text to include external tag information
+   - Add examples of external file structure and usage
+   - Create troubleshooting guide for common external file issues
+   - Document file naming conventions and best practices
+
+## Phase 4: Advanced Features and Optimization (Enhancement)
+1. **Performance Optimization**
+   - Implement file modification time caching
+   - Add lazy loading for external tag data
+   - Optimize file scanning for directories with many files
+   - Create efficient tag resolution caching mechanism
+
+2. **Advanced External File Features**
+   - Support for nested external file directories
+   - Batch external file validation and reporting
+   - External file metadata display and management
+   - Integration with version control ignore patterns
+
+3. **Team Collaboration Features**
+   - Shared external file validation
+   - External file conflict detection and resolution
+   - Team template sharing guidelines and documentation
+   - Integration with git workflows for template management
+
+# Logical Dependency Chain
+## Foundation Layer (Must Be Built First)
+1. **External File Scanner** 
+   - Core requirement for all other functionality
+   - Provides the discovery mechanism for external template files
+   - Must handle file system access and pattern matching reliably
+
+2. **Tag Name Extraction**
+   - Depends on file scanner functionality
+   - Required for identifying available external tags
+   - Must validate tag names against internal format requirements
+
+3. **External Tag Data Reader**
+   - Depends on tag name extraction
+   - Provides access to external tag content
+   - Must handle JSON parsing and validation safely
+
+## Integration Layer (Builds on Foundation)
+4. **Enhanced Tag Registry**
+   - Depends on all foundation components
+   - Combines main and external tag sources
+   - Required for unified tag management across the system
+
+5. **Modified readJSON Function**
+   - Depends on enhanced tag registry
+   - Provides fallback mechanism for tag resolution
+   - Critical for maintaining backward compatibility
+
+6. **Tag Listing Enhancement**
+   - Depends on enhanced tag registry
+   - Provides user visibility into external tags
+   - Required for user discovery of available templates
+
+## User Experience Layer (Completes the Feature)
+7. **Tag Switching Enhancement**
+   - Depends on modified readJSON and tag listing
+   - Enables user interaction with external tags
+   - Must enforce read-only access properly
+
+8. **Error Handling and User Feedback**
+   - Can be developed in parallel with other UX components
+   - Enhances reliability and user experience
+   - Should be integrated throughout development process
+
+9. **Documentation and Help Integration**
+   - Should be developed alongside implementation
+   - Required for user adoption and proper usage
+   - Can be completed in parallel with advanced features
+
+## Optimization Layer (Performance and Advanced Features)
+10. **Performance Optimization**
+    - Can be developed after core functionality is stable
+    - Improves user experience with large numbers of external files
+    - Not blocking for initial release
+
+11. **Advanced External File Features**
+    - Can be developed independently after core features
+    - Enhances power user workflows
+    - Optional for initial release
+
+12. **Team Collaboration Features**
+    - Depends on stable core functionality
+    - Enhances team workflows and template sharing
+    - Can be prioritized based on user feedback
+
+# Risks and Mitigations  
+## Technical Challenges
+
+### File System Performance
+**Risk**: Scanning for external files on every tag operation could impact performance with large directories.
+**Mitigation**: 
+- Implement file modification time caching to avoid unnecessary rescans
+- Use lazy loading for external tag data - only read when accessed
+- Add configurable limits on number of external files to scan
+- Optimize file pattern matching with efficient regex patterns
+
+### External File Corruption
+**Risk**: Malformed or corrupted external JSON files could break tag operations.
+**Mitigation**:
+- Implement robust JSON parsing with comprehensive error handling
+- Add file validation before attempting to parse external files
+- Gracefully skip corrupted files and continue with valid ones
+- Provide clear error messages guiding users to fix malformed files
+
+### Tag Name Conflicts
+**Risk**: External files might contain tag names that conflict with main tasks.json tags.
+**Mitigation**:
+- Implement strict precedence rule: main tasks.json always overrides external files
+- Add warnings when external tags are ignored due to conflicts
+- Document naming conventions to avoid common conflicts
+- Provide validation tools to check for potential conflicts
+
+## MVP Definition
+
+### Core Feature Scope
+**Risk**: Including too many advanced features could delay the core functionality.
+**Mitigation**:
+- Define MVP as basic external file discovery + tag switching
+- Focus on the silent discovery mechanism as the primary value proposition
+- Defer advanced features like nested directories and batch operations
+- Ensure each phase delivers complete, usable functionality
+
+### User Experience Complexity
+**Risk**: The read-only nature of external tags might confuse users.
+**Mitigation**:
+- Provide clear visual indicators for external tags in all interfaces
+- Add explicit warnings when users attempt to modify external tag contexts
+- Document the read-only behavior and its rationale clearly
+- Consider future enhancement for external tag modification workflows
+
+### Backward Compatibility
+**Risk**: Changes to tag resolution logic might break existing workflows.
+**Mitigation**:
+- Maintain existing tag operations unchanged for main tasks.json
+- Add external file support as enhancement, not replacement
+- Test thoroughly with existing task structures and workflows
+- Provide migration path if any breaking changes are necessary
+
+## Resource Constraints
+
+### Development Complexity
+**Risk**: Integration with existing tag management system could be complex.
+**Mitigation**:
+- Phase implementation to minimize risk of breaking existing functionality
+- Create comprehensive test suite covering both main and external tag scenarios
+- Use feature flags to enable/disable external file support during development
+- Implement thorough error handling to prevent system failures
+
+### File System Dependencies
+**Risk**: Different operating systems might handle file operations differently.
+**Mitigation**:
+- Use Node.js built-in file system APIs for cross-platform compatibility
+- Test on multiple operating systems (Windows, macOS, Linux)
+- Handle file path separators and naming conventions properly
+- Add fallback mechanisms for file system access issues
+
+### User Adoption
+**Risk**: Users might not understand or adopt the external file template system.
+**Mitigation**:
+- Create clear documentation with practical examples
+- Provide sample external template files for common use cases
+- Integrate help and guidance directly into the CLI interface
+- Gather user feedback early and iterate on the user experience
+
+# Appendix  
+## External File Naming Convention
+
+### Filename Pattern
+- **Format**: `tasks_[tagname].json`
+- **Examples**: `tasks_feature-auth.json`, `tasks_v2-migration.json`, `tasks_project-alpha.json`
+- **Validation**: Tag name must match internal tag key format (alphanumeric, hyphens, underscores)
+
+### File Structure Requirements
+```json
+{
+  "meta": {
+    "projectName": "Required: Human-readable project name",
+    "version": "Optional: Template version",
+    "templateSource": "Optional: Source identifier",
+    "createdAt": "Optional: ISO-8601 timestamp"
+  },
+  "tags": {
+    "[tagname]": {
+      "meta": {
+        "name": "Required: Tag display name",
+        "description": "Optional: Tag description",
+        "createdAt": "Optional: ISO-8601 timestamp"
+      },
+      "tasks": [
+        // Required: Array of task objects following standard task structure
+      ]
+    }
+  }
+}
+```
+
+## Implementation Functions Specification
+
+### Core Discovery Functions
+```javascript
+// Scan tasks directory for external template files
+function scanForExternalTaskFiles(projectRoot) {
+  // Returns: Array of external file paths
+}
+
+// Extract tag names from external filenames
+function getExternalTagsFromFiles(projectRoot) {
+  // Returns: Array of external tag names
+}
+
+// Read specific external tag data
+function readExternalTagData(projectRoot, tagName) {
+  // Returns: Tag data object or null if not found
+}
+
+// Get combined main and external tags
+function getAvailableTags(projectRoot) {
+  // Returns: Combined tag registry with metadata
+}
+```
+
+### Integration Points
+```javascript
+// Enhanced readJSON with external fallback
+function readJSON(projectRoot, tag = null) {
+  // Modified to check external files when tag not found in main
+}
+
+// Enhanced tags listing with external indicators
+function tags(projectRoot, options = {}) {
+  // Modified to display external tags with (imported) suffix
+}
+
+// Enhanced tag switching with external support
+function useTag(projectRoot, tagName) {
+  // Modified to support switching to external tags (read-only)
+}
+```
+
+## Error Handling Specifications
+
+### File System Errors
+- **ENOENT**: External file not found - gracefully skip and continue
+- **EACCES**: Permission denied - warn user and continue with available files
+- **EISDIR**: Directory instead of file - skip and continue scanning
+
+### JSON Parsing Errors
+- **SyntaxError**: Malformed JSON - skip file and log warning with filename
+- **Missing required fields**: Skip file and provide specific error message
+- **Invalid tag structure**: Skip file and guide user to correct format
+
+### Tag Conflict Resolution
+- **Duplicate tag names**: Main tasks.json takes precedence, log warning
+- **Invalid tag names**: Skip external file and provide naming guidance
+- **Master key in external**: Ignore master key, process other tags normally
+</PRD> 

.taskmaster/state.json

@@ -1,8 +1,9 @@
 {
 	"currentTag": "master",
-	"lastSwitched": "2025-06-14T00:46:38.351Z",
+	"lastSwitched": "2025-06-14T20:37:15.456Z",
 	"branchTagMapping": {
-		"v017-adds": "v017-adds"
+		"v017-adds": "v017-adds",
+		"next": "next"
 	},
 	"migrationNoticeShown": true
 }

.taskmaster/tasks/task_001_test-tag.txt

@@ -0,0 +1,23 @@
+# Task ID: 1
+# Title: Implement TTS Flag for Taskmaster Commands
+# Status: pending
+# Dependencies: 16 (Not found)
+# Priority: medium
+# Description: Add text-to-speech functionality to taskmaster commands with configurable voice options and audio output settings.
+# Details:
+Implement TTS functionality including:
+- Add --tts flag to all relevant taskmaster commands (list, show, generate, etc.)
+- Integrate with system TTS engines (Windows SAPI, macOS say command, Linux espeak/festival)
+- Create TTS configuration options in the configuration management system
+- Add voice selection options (male/female, different languages if available)
+- Implement audio output settings (volume, speed, pitch)
+- Add TTS-specific error handling for cases where TTS is unavailable
+- Create fallback behavior when TTS fails (silent failure or text output)
+- Support for reading task titles, descriptions, and status updates aloud
+- Add option to read entire task lists or individual task details
+- Implement TTS for command confirmations and error messages
+- Create TTS output formatting to make spoken text more natural (removing markdown, formatting numbers/dates appropriately)
+- Add configuration option to enable/disable TTS globally
+
+# Test Strategy:
+Test TTS functionality across different operating systems (Windows, macOS, Linux). Verify that the --tts flag works with all major commands. Test voice configuration options and ensure audio output settings are properly applied. Test error handling when TTS services are unavailable. Verify that text formatting for speech is natural and understandable. Test with various task content types including special characters, code snippets, and long descriptions. Ensure TTS can be disabled and enabled through configuration.

.taskmaster/tasks/task_095.txt

@@ -1,149 +0,0 @@
-# Task ID: 95
-# Title: Implement .taskmaster Directory Structure
-# Status: done
-# Dependencies: 1, 3, 4, 17
-# Priority: high
-# Description: Consolidate all Task Master-managed files in user projects into a clean, centralized .taskmaster/ directory structure to improve organization and keep user project directories clean, based on GitHub issue #275.
-# Details:
-This task involves restructuring how Task Master organizes files within user projects to improve maintainability and keep project directories clean:
-
-1. Create a new `.taskmaster/` directory structure in user projects:
-   - Move task files from `tasks/` to `.taskmaster/tasks/`
-   - Move PRD files from `scripts/` to `.taskmaster/docs/`
-   - Move analysis reports to `.taskmaster/reports/`
-   - Move configuration from `.taskmasterconfig` to `.taskmaster/config.json`
-   - Create `.taskmaster/templates/` for user templates
-
-2. Update all Task Master code that creates/reads user files:
-   - Modify task file generation to use `.taskmaster/tasks/`
-   - Update PRD file handling to use `.taskmaster/docs/`
-   - Adjust report generation to save to `.taskmaster/reports/`
-   - Update configuration loading to look for `.taskmaster/config.json`
-   - Modify any path resolution logic in Task Master's codebase
-
-3. Ensure backward compatibility during migration:
-   - Implement path fallback logic that checks both old and new locations
-   - Add deprecation warnings when old paths are detected
-   - Create a migration command to help users transition to the new structure
-   - Preserve existing user data during migration
-
-4. Update the project initialization process:
-   - Modify the init command to create the new `.taskmaster/` directory structure
-   - Update default file creation to use new paths
-
-5. Benefits of the new structure:
-   - Keeps user project directories clean and organized
-   - Clearly separates Task Master files from user project files
-   - Makes it easier to add Task Master to .gitignore if desired
-   - Provides logical grouping of different file types
-
-6. Test thoroughly to ensure all functionality works with the new structure:
-   - Verify all Task Master commands work with the new paths
-   - Ensure backward compatibility functions correctly
-   - Test migration process preserves all user data
-
-7. Update documentation:
-   - Update README.md to reflect the new user file structure
-   - Add migration guide for existing users
-   - Document the benefits of the cleaner organization
-
-# Test Strategy:
-1. Unit Testing:
-   - Create unit tests for path resolution that verify both new and old paths work
-   - Test configuration loading with both `.taskmasterconfig` and `.taskmaster/config.json`
-   - Verify the migration command correctly moves files and preserves content
-   - Test file creation in all new subdirectories
-
-2. Integration Testing:
-   - Run all existing integration tests with the new directory structure
-   - Verify that all Task Master commands function correctly with new paths
-   - Test backward compatibility by running commands with old file structure
-
-3. Migration Testing:
-   - Test the migration process on sample projects with existing tasks and files
-   - Verify all tasks, PRDs, reports, and configurations are correctly moved
-   - Ensure no data loss occurs during migration
-   - Test migration with partial existing structures (e.g., only tasks/ exists)
-
-4. User Workflow Testing:
-   - Test complete workflows: init → create tasks → generate reports → update PRDs
-   - Verify all generated files go to correct locations in `.taskmaster/`
-   - Test that user project directories remain clean
-
-5. Manual Testing:
-   - Perform end-to-end testing with the new structure
-   - Create, update, and delete tasks using the new structure
-   - Generate reports and verify they're saved to `.taskmaster/reports/`
-
-6. Documentation Verification:
-   - Review all documentation to ensure it accurately reflects the new user file structure
-   - Verify the migration guide provides clear instructions
-
-7. Regression Testing:
-   - Run the full test suite to ensure no regressions were introduced
-   - Verify existing user projects continue to work during transition period
-
-# Subtasks:
-## 1. Create .taskmaster directory structure [done]
-### Dependencies: None
-### Description: Create the new .taskmaster directory and move existing files to their new locations
-### Details:
-Create a new .taskmaster/ directory in the project root. Move the tasks/ directory to .taskmaster/tasks/. Move the scripts/ directory to .taskmaster/scripts/. Move the .taskmasterconfig file to .taskmaster/config.json. Ensure proper file permissions are maintained during the move.
-<info added on 2025-05-29T15:03:56.912Z>
-Create the new .taskmaster/ directory structure in user projects with subdirectories for tasks/, docs/, reports/, and templates/. Move the existing .taskmasterconfig file to .taskmaster/config.json. Since this project is also a Task Master user, move this project's current user files (tasks.json, PRD files, etc.) to the new .taskmaster/ structure to test the implementation. This subtask focuses on user project directory structure, not Task Master source code relocation.
-</info added on 2025-05-29T15:03:56.912Z>
-
-## 2. Update Task Master code for new user file paths [done]
-### Dependencies: 95.1
-### Description: Modify all Task Master code that creates or reads user project files to use the new .taskmaster structure
-### Details:
-Update Task Master's file handling code to use the new paths: tasks in .taskmaster/tasks/, PRD files in .taskmaster/docs/, reports in .taskmaster/reports/, and config in .taskmaster/config.json. Modify path resolution logic throughout the Task Master codebase to reference the new user file locations.
-
-## 3. Update task file generation system [done]
-### Dependencies: 95.1
-### Description: Modify the task file generation system to use the new directory structure
-### Details:
-Update the task file generation system to create and read task files from .taskmaster/tasks/ instead of tasks/. Ensure all template paths are updated. Modify any path resolution logic specific to task file handling.
-
-## 4. Implement backward compatibility logic [done]
-### Dependencies: 95.2, 95.3
-### Description: Add fallback mechanisms to support both old and new file locations during transition
-### Details:
-Implement path fallback logic that checks both old and new locations when files aren't found. Add deprecation warnings when old paths are used, informing users about the new structure. Ensure error messages are clear about the transition.
-
-## 5. Create migration command for users [done]
-### Dependencies: 95.1, 95.4
-### Description: Develop a Task Master command to help users transition their existing projects to the new structure
-### Details:
-Create a 'taskmaster migrate' command that automatically moves user files from old locations to the new .taskmaster structure. Move tasks/ to .taskmaster/tasks/, scripts/prd.txt to .taskmaster/docs/, reports to .taskmaster/reports/, and .taskmasterconfig to .taskmaster/config.json. Include backup functionality and validation to ensure migration completed successfully.
-
-## 6. Update project initialization process [done]
-### Dependencies: 95.1
-### Description: Modify the init command to create the new directory structure for new projects
-### Details:
-Update the init command to create the .taskmaster directory and its subdirectories (tasks/, docs/, reports/, templates/). Modify default file creation to use the new paths. Ensure new projects are created with the correct structure from the start.
-
-## 7. Update PRD and report file handling [done]
-### Dependencies: 95.2, 95.6
-### Description: Modify PRD file creation and report generation to use the new directory structure
-### Details:
-Update PRD file handling to create and read files from .taskmaster/docs/ instead of scripts/. Modify report generation (like task-complexity-report.json) to save to .taskmaster/reports/. Ensure all file operations use the new paths consistently.
-
-## 8. Update documentation and create migration guide [done]
-### Dependencies: 95.5, 95.6, 95.7
-### Description: Update all documentation to reflect the new directory structure and provide migration guidance
-### Details:
-Update README.md and other documentation to reflect the new .taskmaster structure for user projects. Create a comprehensive migration guide explaining the benefits of the new structure and how to migrate existing projects. Include examples of the new directory layout and explain how it keeps user project directories clean.
-
-## 9. Add templates directory support [done]
-### Dependencies: 95.2, 95.6
-### Description: Implement support for user templates in the .taskmaster/templates/ directory
-### Details:
-Create functionality to support user-defined templates in .taskmaster/templates/. Allow users to store custom task templates, PRD templates, or other reusable files. Update Task Master commands to recognize and use templates from this directory when available.
-
-## 10. Verify clean user project directories [done]
-### Dependencies: 95.8, 95.9
-### Description: Ensure the new structure keeps user project root directories clean and organized
-### Details:
-Validate that after implementing the new structure, user project root directories only contain their actual project files plus the single .taskmaster/ directory. Verify that no Task Master files are created outside of .taskmaster/. Test that users can easily add .taskmaster/ to .gitignore if they choose to exclude Task Master files from version control.
-

.taskmaster/tasks/task_096.txt

@@ -1,37 +0,0 @@
-# Task ID: 96
-# Title: Create Export Command for On-Demand Task File and PDF Generation
-# Status: pending
-# Dependencies: 2, 4, 95
-# Priority: medium
-# Description: Develop an 'export' CLI command that generates task files and comprehensive PDF exports on-demand, replacing automatic file generation and providing users with flexible export options.
-# Details:
-Implement a new 'export' command in the CLI that supports two primary modes: (1) generating individual task files on-demand (superseding the current automatic generation system), and (2) producing a comprehensive PDF export. The PDF should include: a first page with the output of 'tm list --with-subtasks', followed by individual pages for each task (using 'tm show <task_id>') and each subtask (using 'tm show <subtask_id>'). Integrate PDF generation using a robust library (e.g., pdfkit, Puppeteer, or jsPDF) to ensure high-quality output and proper pagination. Refactor or disable any existing automatic file generation logic to avoid performance overhead. Ensure the command supports flexible output paths and options for exporting only files, only PDF, or both. Update documentation and help output to reflect the new export capabilities. Consider concurrency and error handling for large projects. Ensure the export process is efficient and does not block the main CLI thread unnecessarily.
-
-# Test Strategy:
-1. Run the 'export' command with various options and verify that task files are generated only on-demand, not automatically. 2. Generate a PDF export and confirm that the first page contains the correct 'tm list --with-subtasks' output, and that each subsequent page accurately reflects the output of 'tm show <task_id>' and 'tm show <subtask_id>' for all tasks and subtasks. 3. Test exporting in projects with large numbers of tasks and subtasks to ensure performance and correctness. 4. Attempt exports with invalid paths or missing data to verify robust error handling. 5. Confirm that no automatic file generation occurs during normal task operations. 6. Review CLI help output and documentation for accuracy regarding the new export functionality.
-
-# Subtasks:
-## 1. Remove Automatic Task File Generation from Task Operations [pending]
-### Dependencies: None
-### Description: Eliminate all calls to generateTaskFiles() from task operations such as add-task, remove-task, set-status, and similar commands to prevent unnecessary performance overhead.
-### Details:
-Audit the codebase for any automatic invocations of generateTaskFiles() and remove or refactor them to ensure task files are not generated automatically during task operations.
-
-## 2. Implement Export Command Infrastructure with On-Demand Task File Generation [pending]
-### Dependencies: 96.1
-### Description: Develop the CLI 'export' command infrastructure, enabling users to generate task files on-demand by invoking the preserved generateTaskFiles function only when requested.
-### Details:
-Create the export command with options for output paths and modes (files, PDF, or both). Ensure generateTaskFiles is only called within this command and not elsewhere.
-
-## 3. Implement Comprehensive PDF Export Functionality [pending]
-### Dependencies: 96.2
-### Description: Add PDF export capability to the export command, generating a structured PDF with a first page listing all tasks and subtasks, followed by individual pages for each task and subtask, using a robust PDF library.
-### Details:
-Integrate a PDF generation library (e.g., pdfkit, Puppeteer, or jsPDF). Ensure the PDF includes the output of 'tm list --with-subtasks' on the first page, and uses 'tm show <task_id>' and 'tm show <subtask_id>' for subsequent pages. Handle pagination, concurrency, and error handling for large projects.
-
-## 4. Update Documentation, Tests, and CLI Help for Export Workflow [pending]
-### Dependencies: 96.2, 96.3
-### Description: Revise all relevant documentation, automated tests, and CLI help output to reflect the new export-based workflow and available options.
-### Details:
-Update user guides, README files, and CLI help text. Add or modify tests to cover the new export command and its options. Ensure all documentation accurately describes the new workflow and usage.
-

CHANGELOG.md

@@ -1,5 +1,480 @@
 # task-master-ai
 
+## 0.17.0
+
+### Minor Changes
+
+- [#779](https://github.com/eyaltoledano/claude-task-master/pull/779) [`c0b3f43`](https://github.com/eyaltoledano/claude-task-master/commit/c0b3f432a60891550b00acb113dc877bd432995f) Thanks [@eyaltoledano](https://github.com/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:**
+
+  ```bash
+  # 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:**
+
+  ```bash
+  # 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](https://github.com/eyaltoledano/claude-task-master/pull/779) [`c0b3f43`](https://github.com/eyaltoledano/claude-task-master/commit/c0b3f432a60891550b00acb113dc877bd432995f) Thanks [@eyaltoledano](https://github.com/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](https://github.com/eyaltoledano/claude-task-master/pull/779) [`c0b3f43`](https://github.com/eyaltoledano/claude-task-master/commit/c0b3f432a60891550b00acb113dc877bd432995f) Thanks [@eyaltoledano](https://github.com/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](https://github.com/eyaltoledano/claude-task-master/pull/779) [`c0b3f43`](https://github.com/eyaltoledano/claude-task-master/commit/c0b3f432a60891550b00acb113dc877bd432995f) Thanks [@eyaltoledano](https://github.com/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](https://github.com/eyaltoledano/claude-task-master/pull/779) [`c0b3f43`](https://github.com/eyaltoledano/claude-task-master/commit/c0b3f432a60891550b00acb113dc877bd432995f) Thanks [@eyaltoledano](https://github.com/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](https://github.com/eyaltoledano/claude-task-master/pull/779) [`c0b3f43`](https://github.com/eyaltoledano/claude-task-master/commit/c0b3f432a60891550b00acb113dc877bd432995f) Thanks [@eyaltoledano](https://github.com/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](https://github.com/eyaltoledano/claude-task-master/pull/779) [`c0b3f43`](https://github.com/eyaltoledano/claude-task-master/commit/c0b3f432a60891550b00acb113dc877bd432995f) Thanks [@eyaltoledano](https://github.com/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](https://github.com/eyaltoledano/claude-task-master/pull/779) [`c0b3f43`](https://github.com/eyaltoledano/claude-task-master/commit/c0b3f432a60891550b00acb113dc877bd432995f) Thanks [@eyaltoledano](https://github.com/eyaltoledano)! - Adds support for filtering tasks by multiple statuses at once using comma-separated statuses.
+
+  Example: `cancelled,deferred`
+
+- [#779](https://github.com/eyaltoledano/claude-task-master/pull/779) [`c0b3f43`](https://github.com/eyaltoledano/claude-task-master/commit/c0b3f432a60891550b00acb113dc877bd432995f) Thanks [@eyaltoledano](https://github.com/eyaltoledano)! - Adds tag to CLI and MCP outputs/responses so you know which tag you are performing operations on.
+
+### Patch Changes
+
+- [#779](https://github.com/eyaltoledano/claude-task-master/pull/779) [`5ec1f61`](https://github.com/eyaltoledano/claude-task-master/commit/5ec1f61c13f468648b7fdc8fa112e95aec25f76d) Thanks [@eyaltoledano](https://github.com/eyaltoledano)! - Fix Cursor deeplink installation by providing copy-paste instructions for GitHub compatibility
+
+- [#779](https://github.com/eyaltoledano/claude-task-master/pull/779) [`c0b3f43`](https://github.com/eyaltoledano/claude-task-master/commit/c0b3f432a60891550b00acb113dc877bd432995f) Thanks [@eyaltoledano](https://github.com/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](https://github.com/eyaltoledano/claude-task-master/pull/779) [`d76bea4`](https://github.com/eyaltoledano/claude-task-master/commit/d76bea49b381c523183f39e33c2a4269371576ed) Thanks [@eyaltoledano](https://github.com/eyaltoledano)! - Update o3 model price
+
+- [#779](https://github.com/eyaltoledano/claude-task-master/pull/779) [`0849c0c`](https://github.com/eyaltoledano/claude-task-master/commit/0849c0c2cedb16ac44ba5cc2d109625a9b4efd67) Thanks [@eyaltoledano](https://github.com/eyaltoledano)! - Fixes issue with expand CLI command "Complexity report not found"
+
+  - Closes #735
+  - Closes #728
+
+- [#779](https://github.com/eyaltoledano/claude-task-master/pull/779) [`c0b3f43`](https://github.com/eyaltoledano/claude-task-master/commit/c0b3f432a60891550b00acb113dc877bd432995f) Thanks [@eyaltoledano](https://github.com/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](https://github.com/eyaltoledano/claude-task-master/pull/779) [`c0b3f43`](https://github.com/eyaltoledano/claude-task-master/commit/c0b3f432a60891550b00acb113dc877bd432995f) Thanks [@eyaltoledano](https://github.com/eyaltoledano)! - Improves dependency management when moving tasks by updating subtask dependencies that reference sibling subtasks by their old parent-based ID
+
+- Updated dependencies [[`c0b3f43`](https://github.com/eyaltoledano/claude-task-master/commit/c0b3f432a60891550b00acb113dc877bd432995f), [`5ec1f61`](https://github.com/eyaltoledano/claude-task-master/commit/5ec1f61c13f468648b7fdc8fa112e95aec25f76d), [`c0b3f43`](https://github.com/eyaltoledano/claude-task-master/commit/c0b3f432a60891550b00acb113dc877bd432995f), [`c0b3f43`](https://github.com/eyaltoledano/claude-task-master/commit/c0b3f432a60891550b00acb113dc877bd432995f), [`d76bea4`](https://github.com/eyaltoledano/claude-task-master/commit/d76bea49b381c523183f39e33c2a4269371576ed), [`c0b3f43`](https://github.com/eyaltoledano/claude-task-master/commit/c0b3f432a60891550b00acb113dc877bd432995f), [`0849c0c`](https://github.com/eyaltoledano/claude-task-master/commit/0849c0c2cedb16ac44ba5cc2d109625a9b4efd67), [`c0b3f43`](https://github.com/eyaltoledano/claude-task-master/commit/c0b3f432a60891550b00acb113dc877bd432995f), [`c0b3f43`](https://github.com/eyaltoledano/claude-task-master/commit/c0b3f432a60891550b00acb113dc877bd432995f), [`c0b3f43`](https://github.com/eyaltoledano/claude-task-master/commit/c0b3f432a60891550b00acb113dc877bd432995f), [`c0b3f43`](https://github.com/eyaltoledano/claude-task-master/commit/c0b3f432a60891550b00acb113dc877bd432995f), [`c0b3f43`](https://github.com/eyaltoledano/claude-task-master/commit/c0b3f432a60891550b00acb113dc877bd432995f), [`c0b3f43`](https://github.com/eyaltoledano/claude-task-master/commit/c0b3f432a60891550b00acb113dc877bd432995f), [`c0b3f43`](https://github.com/eyaltoledano/claude-task-master/commit/c0b3f432a60891550b00acb113dc877bd432995f), [`c0b3f43`](https://github.com/eyaltoledano/claude-task-master/commit/c0b3f432a60891550b00acb113dc877bd432995f)]:
+  - task-master-ai@0.17.0
+
+## 0.16.2
+
+### Patch Changes
+
+- [#695](https://github.com/eyaltoledano/claude-task-master/pull/695) [`1ece6f1`](https://github.com/eyaltoledano/claude-task-master/commit/1ece6f19048df6ae2a0b25cbfb84d2c0f430642c) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - improve findTasks algorithm for resolving tasks path
+
+- [#695](https://github.com/eyaltoledano/claude-task-master/pull/695) [`ee0be04`](https://github.com/eyaltoledano/claude-task-master/commit/ee0be04302cc602246de5cd296291db69bc8b300) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Fix update tool on MCP giving `No valid tasks found`
+
+- [#699](https://github.com/eyaltoledano/claude-task-master/pull/699) [`27edbd8`](https://github.com/eyaltoledano/claude-task-master/commit/27edbd8f3fe5e2ac200b80e7f27f4c0e74a074d6) Thanks [@eyaltoledano](https://github.com/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](https://github.com/eyaltoledano/claude-task-master/pull/655) [`edaa5fe`](https://github.com/eyaltoledano/claude-task-master/commit/edaa5fe0d56e0e4e7c4370670a7a388eebd922ac) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Fix double .taskmaster directory paths in file resolution utilities
+
+  - Closes #636
+
+- [#671](https://github.com/eyaltoledano/claude-task-master/pull/671) [`86ea6d1`](https://github.com/eyaltoledano/claude-task-master/commit/86ea6d1dbc03eeb39f524f565b50b7017b1d2c9c) Thanks [@joedanz](https://github.com/joedanz)! - Add one-click MCP server installation for Cursor
+
+- [#699](https://github.com/eyaltoledano/claude-task-master/pull/699) [`2e55757`](https://github.com/eyaltoledano/claude-task-master/commit/2e55757b2698ba20b78f09ec0286951297510b8e) Thanks [@eyaltoledano](https://github.com/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](https://github.com/eyaltoledano/claude-task-master/pull/695) [`1ece6f1`](https://github.com/eyaltoledano/claude-task-master/commit/1ece6f19048df6ae2a0b25cbfb84d2c0f430642c) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - improve findTasks algorithm for resolving tasks path
+
+- [#695](https://github.com/eyaltoledano/claude-task-master/pull/695) [`ee0be04`](https://github.com/eyaltoledano/claude-task-master/commit/ee0be04302cc602246de5cd296291db69bc8b300) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Fix update tool on MCP giving `No valid tasks found`
+
+- [#699](https://github.com/eyaltoledano/claude-task-master/pull/699) [`27edbd8`](https://github.com/eyaltoledano/claude-task-master/commit/27edbd8f3fe5e2ac200b80e7f27f4c0e74a074d6) Thanks [@eyaltoledano](https://github.com/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](https://github.com/eyaltoledano/claude-task-master/pull/655) [`edaa5fe`](https://github.com/eyaltoledano/claude-task-master/commit/edaa5fe0d56e0e4e7c4370670a7a388eebd922ac) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Fix double .taskmaster directory paths in file resolution utilities
+
+  - Closes #636
+
+- [#671](https://github.com/eyaltoledano/claude-task-master/pull/671) [`86ea6d1`](https://github.com/eyaltoledano/claude-task-master/commit/86ea6d1dbc03eeb39f524f565b50b7017b1d2c9c) Thanks [@joedanz](https://github.com/joedanz)! - Add one-click MCP server installation for Cursor
+
+- [#699](https://github.com/eyaltoledano/claude-task-master/pull/699) [`2e55757`](https://github.com/eyaltoledano/claude-task-master/commit/2e55757b2698ba20b78f09ec0286951297510b8e) Thanks [@eyaltoledano](https://github.com/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

docs/configuration.md

@@ -2,7 +2,6 @@
 
 Taskmaster uses two primary methods for configuration:
 
-1.  **`.taskmaster/config.json` File (Recommended - New Structure)**
 1.  **`.taskmaster/config.json` File (Recommended - New Structure)**
 
     - This JSON file stores most configuration settings, including AI model selections, parameters, logging levels, and project defaults.

docs/models.md

@@ -1,4 +1,4 @@
-# Available Models as of June 13, 2025
+# Available Models as of June 15, 2025
 
 ## Main Models
 

mcp-server/src/core/direct-functions/clear-subtasks.js

@@ -5,9 +5,11 @@
 import { clearSubtasks } from '../../../../scripts/modules/task-manager.js';
 import {
 	enableSilentMode,
-	disableSilentMode
+	disableSilentMode,
+	readJSON
 } from '../../../../scripts/modules/utils.js';
 import fs from 'fs';
+import path from 'path';
 
 /**
  * Clear subtasks from specified tasks
@@ -15,12 +17,13 @@ import fs from 'fs';
  * @param {string} args.tasksJsonPath - Explicit path to the tasks.json file.
  * @param {string} [args.id] - Task IDs (comma-separated) to clear subtasks from
  * @param {boolean} [args.all] - Clear subtasks from all tasks
+ * @param {string} [args.tag] - Tag context to operate on (defaults to current active tag)
  * @param {Object} log - Logger object
  * @returns {Promise<{success: boolean, data?: Object, error?: {code: string, message: string}}>}
  */
 export async function clearSubtasksDirect(args, log) {
 	// Destructure expected args
-	const { tasksJsonPath, id, all } = args;
+	const { tasksJsonPath, id, all, tag, projectRoot } = args;
 	try {
 		log.info(`Clearing subtasks with args: ${JSON.stringify(args)}`);
 
@@ -64,52 +67,70 @@ export async function clearSubtasksDirect(args, log) {
 
 		let taskIds;
 
+		// Use readJSON which handles silent migration and tag resolution
+		const data = readJSON(tasksPath, projectRoot, tag);
+
+		if (!data || !data.tasks) {
+			return {
+				success: false,
+				error: {
+					code: 'INPUT_VALIDATION_ERROR',
+					message: `No tasks found in tasks file: ${tasksPath}`
+				}
+			};
+		}
+
+		const currentTag = data.tag || 'master';
+		const tasks = data.tasks;
+
 		// If all is specified, get all task IDs
 		if (all) {
-			log.info('Clearing subtasks from all tasks');
-			const data = JSON.parse(fs.readFileSync(tasksPath, 'utf8'));
-			if (!data || !data.tasks || data.tasks.length === 0) {
+			log.info(`Clearing subtasks from all tasks in tag '${currentTag}'`);
+			if (tasks.length === 0) {
 				return {
 					success: false,
 					error: {
 						code: 'INPUT_VALIDATION_ERROR',
-						message: 'No valid tasks found in the tasks file'
+						message: `No tasks found in tag context '${currentTag}'`
 					}
 				};
 			}
-			taskIds = data.tasks.map((t) => t.id).join(',');
+			taskIds = tasks.map((t) => t.id).join(',');
 		} else {
 			// Use the provided task IDs
 			taskIds = id;
 		}
 
-		log.info(`Clearing subtasks from tasks: ${taskIds}`);
+		log.info(`Clearing subtasks from tasks: ${taskIds} in tag '${currentTag}'`);
 
 		// Enable silent mode to prevent console logs from interfering with JSON response
 		enableSilentMode();
 
 		// Call the core function
-		clearSubtasks(tasksPath, taskIds);
+		clearSubtasks(tasksPath, taskIds, { projectRoot, tag: currentTag });
 
 		// Restore normal logging
 		disableSilentMode();
 
 		// Read the updated data to provide a summary
-		const updatedData = JSON.parse(fs.readFileSync(tasksPath, 'utf8'));
+		const updatedData = readJSON(tasksPath, projectRoot, currentTag);
 		const taskIdArray = taskIds.split(',').map((id) => parseInt(id.trim(), 10));
 
 		// Build a summary of what was done
 		const clearedTasksCount = taskIdArray.length;
+		const updatedTasks = updatedData.tasks || [];
+
 		const taskSummary = taskIdArray.map((id) => {
-			const task = updatedData.tasks.find((t) => t.id === id);
+			const task = updatedTasks.find((t) => t.id === id);
 			return task ? { id, title: task.title } : { id, title: 'Task not found' };
 		});
 
 		return {
 			success: true,
 			data: {
-				message: `Successfully cleared subtasks from ${clearedTasksCount} task(s)`,
-				tasksCleared: taskSummary
+				message: `Successfully cleared subtasks from ${clearedTasksCount} task(s) in tag '${currentTag}'`,
+				tasksCleared: taskSummary,
+				tag: currentTag
 			}
 		};
 	} catch (error) {

mcp-server/src/core/direct-functions/move-task.js

@@ -71,7 +71,11 @@ export async function moveTaskDirect(args, log, context = {}) {
 			tasksPath,
 			args.sourceId,
 			args.destinationId,
-			generateFiles
+			generateFiles,
+			{
+				projectRoot: args.projectRoot,
+				tag: args.tag
+			}
 		);
 
 		// Restore console output

mcp-server/src/tools/clear-subtasks.js

@@ -35,7 +35,8 @@ export function registerClearSubtasksTool(server) {
 					),
 				projectRoot: z
 					.string()
-					.describe('The directory of the project. Must be an absolute path.')
+					.describe('The directory of the project. Must be an absolute path.'),
+				tag: z.string().optional().describe('Tag context to operate on')
 			})
 			.refine((data) => data.id || data.all, {
 				message: "Either 'id' or 'all' parameter must be provided",
@@ -64,7 +65,8 @@ export function registerClearSubtasksTool(server) {
 						tasksJsonPath: tasksJsonPath,
 						id: args.id,
 						all: args.all,
-						projectRoot: args.projectRoot
+						projectRoot: args.projectRoot,
+						tag: args.tag || 'master'
 					},
 					log,
 					{ session }

package-lock.json

@@ -1,12 +1,12 @@
 {
 	"name": "task-master-ai",
-	"version": "0.16.2-rc.0",
+	"version": "0.17.0",
 	"lockfileVersion": 3,
 	"requires": true,
 	"packages": {
 		"": {
 			"name": "task-master-ai",
-			"version": "0.16.2-rc.0",
+			"version": "0.17.0",
 			"license": "MIT WITH Commons-Clause",
 			"dependencies": {
 				"@ai-sdk/amazon-bedrock": "^2.2.9",
@@ -42,7 +42,6 @@
 				"ollama-ai-provider": "^1.2.0",
 				"openai": "^4.89.0",
 				"ora": "^8.2.0",
-				"task-master-ai": "0.16.2",
 				"uuid": "^11.1.0",
 				"zod": "^3.23.8"
 			},
@@ -11370,55 +11369,6 @@
 				"react": "^16.11.0 || ^17.0.0 || ^18.0.0 || ^19.0.0"
 			}
 		},
-		"node_modules/task-master-ai": {
-			"version": "0.16.2",
-			"resolved": "https://registry.npmjs.org/task-master-ai/-/task-master-ai-0.16.2.tgz",
-			"integrity": "sha512-7N2teGOMOmOEdmqEuggnVBpy7emZaRy32HbeKn1ZsVVxIb+PDNSRahhy/xlxrf6EVeGomW9HhG1moKk4ytMIVA==",
-			"license": "MIT WITH Commons-Clause",
-			"dependencies": {
-				"@ai-sdk/amazon-bedrock": "^2.2.9",
-				"@ai-sdk/anthropic": "^1.2.10",
-				"@ai-sdk/azure": "^1.3.17",
-				"@ai-sdk/google": "^1.2.13",
-				"@ai-sdk/google-vertex": "^2.2.23",
-				"@ai-sdk/mistral": "^1.2.7",
-				"@ai-sdk/openai": "^1.3.20",
-				"@ai-sdk/perplexity": "^1.1.7",
-				"@ai-sdk/xai": "^1.2.15",
-				"@anthropic-ai/sdk": "^0.39.0",
-				"@aws-sdk/credential-providers": "^3.817.0",
-				"@openrouter/ai-sdk-provider": "^0.4.5",
-				"ai": "^4.3.10",
-				"boxen": "^8.0.1",
-				"chalk": "^5.4.1",
-				"cli-table3": "^0.6.5",
-				"commander": "^11.1.0",
-				"cors": "^2.8.5",
-				"dotenv": "^16.3.1",
-				"express": "^4.21.2",
-				"fastmcp": "^2.2.2",
-				"figlet": "^1.8.0",
-				"fuse.js": "^7.1.0",
-				"gradient-string": "^3.0.0",
-				"helmet": "^8.1.0",
-				"inquirer": "^12.5.0",
-				"jsonwebtoken": "^9.0.2",
-				"lru-cache": "^10.2.0",
-				"ollama-ai-provider": "^1.2.0",
-				"openai": "^4.89.0",
-				"ora": "^8.2.0",
-				"uuid": "^11.1.0",
-				"zod": "^3.23.8"
-			},
-			"bin": {
-				"task-master": "bin/task-master.js",
-				"task-master-ai": "mcp-server/server.js",
-				"task-master-mcp": "mcp-server/server.js"
-			},
-			"engines": {
-				"node": ">=18.0.0"
-			}
-		},
 		"node_modules/term-size": {
 			"version": "2.2.1",
 			"resolved": "https://registry.npmjs.org/term-size/-/term-size-2.2.1.tgz",

package.json

@@ -1,6 +1,6 @@
 {
 	"name": "task-master-ai",
-	"version": "0.16.2-rc.0",
+	"version": "0.17.0",
 	"description": "A task management system for ambitious AI-driven development that doesn't overwhelm and confuse Cursor.",
 	"main": "index.js",
 	"type": "module",
@@ -72,7 +72,6 @@
 		"ollama-ai-provider": "^1.2.0",
 		"openai": "^4.89.0",
 		"ora": "^8.2.0",
-		"task-master-ai": "0.16.2",
 		"uuid": "^11.1.0",
 		"zod": "^3.23.8"
 	},

scripts/modules/commands.js

@@ -1614,7 +1614,7 @@ function registerCommands(programInstance) {
 		.command('research')
 		.description('Perform AI-powered research queries with project context')
 		.argument('[prompt]', 'Research prompt to investigate')
-		.option('--file <file>', 'Path to the tasks file', 'tasks/tasks.json')
+		.option('--file <file>', 'Path to the tasks file')
 		.option(
 			'-i, --id <ids>',
 			'Comma-separated task/subtask IDs to include as context (e.g., "15,16.2")'
@@ -1752,7 +1752,8 @@ function registerCommands(programInstance) {
 			const projectRoot = findProjectRoot() || '.';
 			const tag = options.tag || getCurrentTag(projectRoot) || 'master';
 			const tasksPath =
-				options.file || path.join(projectRoot, 'tasks', 'tasks.json');
+				options.file ||
+				path.join(projectRoot, '.taskmaster', 'tasks', 'tasks.json');
 
 			// Show current tag context
 			displayCurrentTagIndicator(tag);
@@ -1856,14 +1857,15 @@ function registerCommands(programInstance) {
 					researchOptions,
 					{
 						commandName: 'research',
-						outputType: 'cli'
+						outputType: 'cli',
+						tag: tag
 					},
 					'text',
 					validatedParams.allowFollowUp // Pass follow-up flag
 				);
 
-				// Auto-save to task/subtask if requested
-				if (validatedParams.saveToId) {
+				// Auto-save to task/subtask if requested and no interactive save occurred
+				if (validatedParams.saveToId && !result.interactiveSaveOccurred) {
 					try {
 						const isSubtask = validatedParams.saveToId.includes('.');
 
@@ -1892,7 +1894,8 @@ ${result.result}`;
 								{
 									commandName: 'research-save',
 									outputType: 'cli',
-									projectRoot: validatedParams.projectRoot
+									projectRoot: validatedParams.projectRoot,
+									tag: tag
 								},
 								'text'
 							);
@@ -1917,7 +1920,8 @@ ${result.result}`;
 								{
 									commandName: 'research-save',
 									outputType: 'cli',
-									projectRoot: validatedParams.projectRoot
+									projectRoot: validatedParams.projectRoot,
+									tag: tag
 								},
 								'text',
 								true // appendMode = true
@@ -3540,7 +3544,7 @@ Examples:
 
 				try {
 					// Read tasks data once to validate destination IDs
-					const tasksData = readJSON(tasksPath);
+					const tasksData = readJSON(tasksPath, projectRoot, tag);
 					if (!tasksData || !tasksData.tasks) {
 						console.error(
 							chalk.red(`Error: Invalid or missing tasks file at ${tasksPath}`)

scripts/modules/task-manager/add-task.js

@@ -558,14 +558,14 @@ async function addTask(
 		report('DEBUG: tasks.json written.', 'debug');
 
 		// Generate markdown task files
-		report('Generating task files...', 'info');
-		report('DEBUG: Calling generateTaskFiles...', 'debug');
-		// Pass mcpLog if available to generateTaskFiles
-		await generateTaskFiles(tasksPath, path.dirname(tasksPath), {
-			projectRoot,
-			tag: targetTag
-		});
-		report('DEBUG: generateTaskFiles finished.', 'debug');
+		// report('Generating task files...', 'info');
+		// report('DEBUG: Calling generateTaskFiles...', 'debug');
+		// // Pass mcpLog if available to generateTaskFiles
+		// await generateTaskFiles(tasksPath, path.dirname(tasksPath), {
+		// 	projectRoot,
+		// 	tag: targetTag
+		// });
+		// report('DEBUG: generateTaskFiles finished.', 'debug');
 
 		// Show success message - only for text output (CLI)
 		if (outputFormat === 'text') {

scripts/modules/task-manager/clear-subtasks.js

@@ -5,7 +5,6 @@ import Table from 'cli-table3';
 
 import { log, readJSON, writeJSON, truncate, isSilentMode } from '../utils.js';
 import { displayBanner } from '../ui.js';
-import generateTaskFiles from './generate-task-files.js';
 
 /**
  * Clear subtasks from specified tasks
@@ -99,10 +98,6 @@ function clearSubtasks(tasksPath, taskIds, context = {}) {
 			console.log(summaryTable.toString());
 		}
 
-		// Regenerate task files to reflect changes
-		log('info', 'Regenerating task files...');
-		generateTaskFiles(tasksPath, path.dirname(tasksPath), { projectRoot, tag });
-
 		// Success message
 		if (!isSilentMode()) {
 			console.log(

scripts/modules/task-manager/expand-task.js

@@ -669,7 +669,7 @@ async function expandTask(
 
 		data.tasks[taskIndex] = task; // Assign the modified task back
 		writeJSON(tasksPath, data);
-		await generateTaskFiles(tasksPath, path.dirname(tasksPath));
+		// await generateTaskFiles(tasksPath, path.dirname(tasksPath));
 
 		// Display AI Usage Summary for CLI
 		if (

scripts/modules/task-manager/move-task.js

@@ -120,7 +120,7 @@ async function moveTask(
 
 	// Always write the data object, never the _rawTaggedData directly
 	// The writeJSON function will filter out _rawTaggedData automatically
-	writeJSON(tasksPath, rawData);
+	writeJSON(tasksPath, rawData, options.projectRoot, currentTag);
 
 	if (generateFiles) {
 		await generateTaskFiles(tasksPath, path.dirname(tasksPath));

scripts/modules/task-manager/research.js

@@ -107,8 +107,13 @@ async function performResearch(
 		let autoDiscoveredIds = [];
 
 		try {
-			const tasksPath = path.join(projectRoot, 'tasks', 'tasks.json');
-			const tasksData = await readJSON(tasksPath);
+			const tasksPath = path.join(
+				projectRoot,
+				'.taskmaster',
+				'tasks',
+				'tasks.json'
+			);
+			const tasksData = await readJSON(tasksPath, projectRoot);
 
 			if (tasksData && tasksData.tasks && tasksData.tasks.length > 0) {
 				// Flatten tasks to include subtasks for fuzzy search
@@ -250,6 +255,9 @@ async function performResearch(
 		const tagInfo = aiResult.tagInfo;
 
 		// Format and display results
+		// Initialize interactive save tracking
+		let interactiveSaveInfo = { interactiveSaveOccurred: false };
+
 		if (outputFormat === 'text') {
 			displayResearchResults(
 				researchResult,
@@ -265,7 +273,7 @@ async function performResearch(
 
 			// Offer follow-up question option (only for initial CLI queries, not MCP)
 			if (allowFollowUp && !isMCP) {
-				await handleFollowUpQuestions(
+				interactiveSaveInfo = await handleFollowUpQuestions(
 					options,
 					context,
 					outputFormat,
@@ -308,7 +316,8 @@ async function performResearch(
 				detailLevel,
 				telemetryData,
 				tagInfo,
-				savedFilePath
+				savedFilePath,
+				interactiveSaveOccurred: false // MCP save-to-file doesn't count as interactive save
 			};
 		}
 
@@ -325,7 +334,9 @@ async function performResearch(
 			totalInputTokens,
 			detailLevel,
 			telemetryData,
-			tagInfo
+			tagInfo,
+			interactiveSaveOccurred:
+				interactiveSaveInfo?.interactiveSaveOccurred || false
 		};
 	} catch (error) {
 		logFn.error(`Research query failed: ${error.message}`);
@@ -643,6 +654,8 @@ async function handleFollowUpQuestions(
 	initialQuery,
 	initialResult
 ) {
+	let interactiveSaveOccurred = false;
+
 	try {
 		// Import required modules for saving
 		const { readJSON } = await import('../utils.js');
@@ -693,12 +706,15 @@ async function handleFollowUpQuestions(
 
 			if (action === 'save') {
 				// Handle save functionality
-				await handleSaveToTask(
+				const saveResult = await handleSaveToTask(
 					conversationHistory,
 					projectRoot,
 					context,
 					logFn
 				);
+				if (saveResult) {
+					interactiveSaveOccurred = true;
+				}
 				continue;
 			}
 
@@ -762,6 +778,8 @@ async function handleFollowUpQuestions(
 		// silently continue without follow-up functionality
 		logFn.debug(`Follow-up questions not available: ${error.message}`);
 	}
+
+	return { interactiveSaveOccurred };
 }
 
 /**
@@ -828,8 +846,10 @@ async function handleSaveToTask(
 			return;
 		}
 
-		// Validate ID exists
-		const data = readJSON(tasksPath, projectRoot);
+		// Validate ID exists - use tag from context
+		const { getCurrentTag } = await import('../utils.js');
+		const tag = context.tag || getCurrentTag(projectRoot) || 'master';
+		const data = readJSON(tasksPath, projectRoot, tag);
 		if (!data || !data.tasks) {
 			console.log(chalk.red('❌ No valid tasks found.'));
 			return;
@@ -863,7 +883,7 @@ async function handleSaveToTask(
 				trimmedTaskId,
 				conversationThread,
 				false, // useResearch = false for simple append
-				context,
+				{ ...context, tag },
 				'text'
 			);
 
@@ -890,7 +910,7 @@ async function handleSaveToTask(
 				taskIdNum,
 				conversationThread,
 				false, // useResearch = false for simple append
-				context,
+				{ ...context, tag },
 				'text',
 				true // appendMode = true
 			);
@@ -899,9 +919,12 @@ async function handleSaveToTask(
 				chalk.green(`✅ Research conversation saved to task ${trimmedTaskId}`)
 			);
 		}
+
+		return true; // Indicate successful save
 	} catch (error) {
 		console.log(chalk.red(`❌ Error saving conversation: ${error.message}`));
 		logFn.error(`Error saving conversation: ${error.message}`);
+		return false; // Indicate failed save
 	}
 }
 

scripts/modules/task-manager/update-subtask-by-id.js

@@ -17,7 +17,8 @@ import {
 	truncate,
 	isSilentMode,
 	findProjectRoot,
-	flattenTasksWithSubtasks
+	flattenTasksWithSubtasks,
+	getCurrentTag
 } from '../utils.js';
 import { generateTextService } from '../ai-services-unified.js';
 import { getDebugFlag } from '../config-manager.js';
@@ -46,7 +47,7 @@ async function updateSubtaskById(
 	context = {},
 	outputFormat = context.mcpLog ? 'json' : 'text'
 ) {
-	const { session, mcpLog, projectRoot: providedProjectRoot } = context;
+	const { session, mcpLog, projectRoot: providedProjectRoot, tag } = context;
 	const logFn = mcpLog || consoleLog;
 	const isMCP = !!mcpLog;
 
@@ -90,7 +91,10 @@ async function updateSubtaskById(
 			throw new Error('Could not determine project root directory');
 		}
 
-		const data = readJSON(tasksPath, projectRoot);
+		// Determine the tag to use
+		const currentTag = tag || getCurrentTag(projectRoot) || 'master';
+
+		const data = readJSON(tasksPath, projectRoot, currentTag);
 		if (!data || !data.tasks) {
 			throw new Error(
 				`No valid tasks found in ${tasksPath}. The file may be corrupted or have an invalid format.`
@@ -331,7 +335,7 @@ Output Requirements:
 		if (outputFormat === 'text' && getDebugFlag(session)) {
 			console.log('>>> DEBUG: About to call writeJSON with updated data...');
 		}
-		writeJSON(tasksPath, data, projectRoot);
+		writeJSON(tasksPath, data, projectRoot, currentTag);
 		if (outputFormat === 'text' && getDebugFlag(session)) {
 			console.log('>>> DEBUG: writeJSON call completed.');
 		}

scripts/modules/task-manager/update-task-by-id.js

@@ -12,7 +12,8 @@ import {
 	truncate,
 	isSilentMode,
 	flattenTasksWithSubtasks,
-	findProjectRoot
+	findProjectRoot,
+	getCurrentTag
 } from '../utils.js';
 
 import {
@@ -23,11 +24,7 @@ import {
 } from '../ui.js';
 
 import { generateTextService } from '../ai-services-unified.js';
-import {
-	getDebugFlag,
-	isApiKeySet // Keep this check
-} from '../config-manager.js';
-import generateTaskFiles from './generate-task-files.js';
+import { getDebugFlag, isApiKeySet } from '../config-manager.js';
 import { ContextGatherer } from '../utils/contextGatherer.js';
 import { FuzzyTaskSearch } from '../utils/fuzzyTaskSearch.js';
 
@@ -223,7 +220,7 @@ async function updateTaskById(
 	outputFormat = 'text',
 	appendMode = false
 ) {
-	const { session, mcpLog, projectRoot: providedProjectRoot } = context;
+	const { session, mcpLog, projectRoot: providedProjectRoot, tag } = context;
 	const logFn = mcpLog || consoleLog;
 	const isMCP = !!mcpLog;
 
@@ -268,8 +265,11 @@ async function updateTaskById(
 			throw new Error('Could not determine project root directory');
 		}
 
+		// Determine the tag to use
+		const currentTag = tag || getCurrentTag(projectRoot) || 'master';
+
 		// --- Task Loading and Status Check (Keep existing) ---
-		const data = readJSON(tasksPath, projectRoot);
+		const data = readJSON(tasksPath, projectRoot, currentTag);
 		if (!data || !data.tasks)
 			throw new Error(`No valid tasks found in ${tasksPath}.`);
 		const taskIndex = data.tasks.findIndex((task) => task.id === taskId);
@@ -510,7 +510,7 @@ The changes described in the prompt should be thoughtfully applied to make the t
 
 				// Write the updated task back to file
 				data.tasks[taskIndex] = taskToUpdate;
-				writeJSON(tasksPath, data);
+				writeJSON(tasksPath, data, projectRoot, currentTag);
 				report('success', `Successfully appended to task ${taskId}`);
 
 				// Display success message for CLI
@@ -624,7 +624,7 @@ The changes described in the prompt should be thoughtfully applied to make the t
 			// --- End Update Task Data ---
 
 			// --- Write File and Generate (Unchanged) ---
-			writeJSON(tasksPath, data);
+			writeJSON(tasksPath, data, projectRoot, currentTag);
 			report('success', `Successfully updated task ${taskId}`);
 			// await generateTaskFiles(tasksPath, path.dirname(tasksPath));
 			// --- End Write File ---

scripts/modules/utils/contextGatherer.js

@@ -123,7 +123,7 @@ export class ContextGatherer {
 
 		// Dependency Graph Analysis
 		if (dependencyTasks.length > 0) {
-			const dependencyResults = this._buildDependencyContext(dependencyTasks);
+			const dependencyResults = this._buildDependencyGraphs(dependencyTasks);
 			dependencyResults.allRelatedTaskIds.forEach((id) =>
 				finalTaskIds.add(String(id))
 			);

tests/unit/scripts/modules/task-manager/add-task.test.js

@@ -260,7 +260,6 @@ describe('addTask', () => {
 				})
 			})
 		);
-		expect(generateTaskFiles).toHaveBeenCalled();
 		expect(result).toEqual(
 			expect.objectContaining({
 				newTaskId: 4,

tests/unit/scripts/modules/task-manager/clear-subtasks.test.js

@@ -144,10 +144,6 @@ describe('clearSubtasks', () => {
 			undefined,
 			undefined
 		);
-		expect(generateTaskFiles).toHaveBeenCalledWith(tasksPath, 'tasks', {
-			projectRoot: undefined,
-			tag: undefined
-		});
 	});
 
 	test('should clear subtasks from multiple tasks when given comma-separated IDs', () => {
@@ -175,10 +171,6 @@ describe('clearSubtasks', () => {
 			undefined,
 			undefined
 		);
-		expect(generateTaskFiles).toHaveBeenCalledWith(tasksPath, 'tasks', {
-			projectRoot: undefined,
-			tag: undefined
-		});
 	});
 
 	test('should handle tasks with no subtasks', () => {
@@ -242,10 +234,6 @@ describe('clearSubtasks', () => {
 			undefined,
 			undefined
 		);
-		expect(generateTaskFiles).toHaveBeenCalledWith(tasksPath, 'tasks', {
-			projectRoot: undefined,
-			tag: undefined
-		});
 	});
 
 	test('should handle file read errors', () => {