chore: re-enter rc mode for a last pre-release

.changeset/README.md

@@ -58,9 +58,9 @@ Examples:
 ```md
 # Good
 
-Added new `--research` flag to the `expand` command that uses your configured research model
-to provide research-backed task expansions. Requires appropriate API key
-for your research model.
+Added new `--research` flag to the `expand` command that uses Perplexity AI
+to provide research-backed task expansions. Requires PERPLEXITY_API_KEY
+environment variable.
 
 # Not Good
 

.changeset/chore-fix-docs.md

@@ -1,5 +0,0 @@
----
-"task-master-ai": patch
----
-
-Improve `analyze-complexity` cli docs and `--research` flag documentation

.changeset/config.json

@@ -11,9 +11,6 @@
   "access": "public",
   "baseBranch": "main",
   "ignore": [
-    "docs",
-    "@tm/cli",
-    "@tm/core",
-    "@tm/build-config"
+    "docs"
   ]
 }

.changeset/fluffy-clocks-cross.md

@@ -0,0 +1,5 @@
+---
+"task-master-ai": patch
+---
+
+Fix module not found for new 0.27.0 release

.changeset/mcp-timeout-configuration.md

@@ -1,13 +0,0 @@
----
-"task-master-ai": minor
----
-
-Enhanced Roo Code profile with MCP timeout configuration for improved reliability during long-running AI operations. The Roo profile now automatically configures a 300-second timeout for MCP server operations, preventing timeouts during complex tasks like `parse-prd`, `expand-all`, `analyze-complexity`, and `research` operations. This change also replaces static MCP configuration files with programmatic generation for better maintainability.
-
-**What's New:**
-- 300-second timeout for MCP operations (up from default 60 seconds)
-- Programmatic MCP configuration generation (replaces static asset files)
-- Enhanced reliability for AI-powered operations
-- Consistent with other AI coding assistant profiles
-
-**Migration:** No user action required - existing Roo Code installations will automatically receive the enhanced MCP configuration on next initialization.

.changeset/petite-ideas-grab.md

@@ -1,5 +0,0 @@
----
-"task-master-ai": patch
----
-
-Fix Claude Code settings validation for pathToClaudeCodeExecutable

.changeset/pre.json

@@ -0,0 +1,12 @@
+{
+  "mode": "pre",
+  "tag": "rc",
+  "initialVersions": {
+    "task-master-ai": "0.27.0",
+    "docs": "0.0.3",
+    "extension": "0.25.1"
+  },
+  "changesets": [
+    "fluffy-clocks-cross"
+  ]
+}

.changeset/silly-pandas-find.md

@@ -1,5 +0,0 @@
----
-"task-master-ai": patch
----
-
-Fix sonar deep research model failing, should be called `sonar-deep-research`

.changeset/soft-dingos-grow.md

@@ -0,0 +1,5 @@
+---
+"task-master-ai": patch
+---
+
+One last testing final final

.claude/commands/tm/analyze-complexity/analyze-complexity.md

@@ -16,7 +16,7 @@ task-master analyze-complexity [--research] [--threshold=5]
 
 ## Analysis Parameters
 
-- `--research` → Use configured research model for deeper analysis
+- `--research` → Use research AI for deeper analysis
 - `--threshold=5` → Only flag tasks above complexity 5
 - Default: Analyze all pending tasks
 

.cursor/rules/dev_workflow.mdc

@@ -231,7 +231,7 @@ Taskmaster offers two primary ways to interact:
 
 -   Use `expand_task` / `task-master expand --id=<id>`. It automatically uses the complexity report if found, otherwise generates default number of subtasks.
 -   Use `--num=<number>` to specify an explicit number of subtasks, overriding defaults or complexity report recommendations.
--   Add `--research` flag to leverage your configured research model for research-backed expansion.
+-   Add `--research` flag to leverage Perplexity AI for research-backed expansion.
 -   Add `--force` flag to clear existing subtasks before generating new ones (default is to append).
 -   Use `--prompt="<context>"` to provide additional context when needed.
 -   Review and adjust generated subtasks as necessary.

.kiro/steering/dev_workflow.md

@@ -229,7 +229,7 @@ Taskmaster offers two primary ways to interact:
 
 -   Use `expand_task` / `task-master expand --id=<id>`. It automatically uses the complexity report if found, otherwise generates default number of subtasks.
 -   Use `--num=<number>` to specify an explicit number of subtasks, overriding defaults or complexity report recommendations.
--   Add `--research` flag to leverage your configured research model for research-backed expansion.
+-   Add `--research` flag to leverage Perplexity AI for research-backed expansion.
 -   Add `--force` flag to clear existing subtasks before generating new ones (default is to append).
 -   Use `--prompt="<context>"` to provide additional context when needed.
 -   Review and adjust generated subtasks as necessary.

.manypkg.json

@@ -0,0 +1,6 @@
+{
+	"$schema": "https://unpkg.com/@manypkg/get-packages@1.1.3/schema.json",
+	"defaultBranch": "main",
+	"ignoredRules": ["ROOT_HAS_DEPENDENCIES", "INTERNAL_MISMATCH"],
+	"ignoredPackages": ["@tm/core", "@tm/cli", "@tm/build-config"]
+}

.taskmaster/docs/README.md

@@ -12,7 +12,7 @@ In an AI-driven development process—particularly with tools like [Cursor](http
 4. **Generate** individual task files (e.g., `task_001.txt`) for easy reference or to feed into an AI coding workflow.
 5. **Set task status**—mark tasks as `done`, `pending`, or `deferred` based on progress.
 6. **Expand** tasks with subtasks—break down complex tasks into smaller, more manageable subtasks.
-7. **Research-backed subtask generation**—use your configured research model to generate more informed and contextually relevant subtasks.
+7. **Research-backed subtask generation**—use Perplexity AI to generate more informed and contextually relevant subtasks.
 8. **Clear subtasks**—remove subtasks from specified tasks to allow regeneration or restructuring.
 9. **Show task details**—display detailed information about a specific task and its subtasks.
 
@@ -29,7 +29,7 @@ The script can be configured through environment variables in a `.env` file at t
 - `MODEL`: Specify which Claude model to use (default: "claude-3-7-sonnet-20250219")
 - `MAX_TOKENS`: Maximum tokens for model responses (default: 4000)
 - `TEMPERATURE`: Temperature for model responses (default: 0.7)
-- `PERPLEXITY_API_KEY`: Your Perplexity API key for research-backed subtask generation (if using Perplexity as your research model)
+- `PERPLEXITY_API_KEY`: Your Perplexity API key for research-backed subtask generation
 - `PERPLEXITY_MODEL`: Specify which Perplexity model to use (default: "sonar-medium-online")
 - `DEBUG`: Enable debug logging (default: false)
 - `TASKMASTER_LOG_LEVEL`: Log level - debug, info, warn, error (default: info)
@@ -97,7 +97,7 @@ node scripts/dev.js update --from=4 --prompt="Refactor tasks from ID 4 onward to
 # Update all tasks (default from=1)
 node scripts/dev.js update --prompt="Add authentication to all relevant tasks"
 
-# With research-backed updates using your configured research model
+# With research-backed updates using Perplexity AI
 node scripts/dev.js update --from=4 --prompt="Integrate OAuth 2.0" --research
 
 # Specify a different tasks file
@@ -109,7 +109,7 @@ Notes:
 - The `--prompt` parameter is required and should explain the changes or new context
 - Only tasks that aren't marked as 'done' will be updated
 - Tasks with ID >= the specified --from value will be updated
-- The `--research` flag uses your configured research model for more informed updates when available
+- The `--research` flag uses Perplexity AI for more informed updates when available
 
 ## Updating a Single Task
 
@@ -119,7 +119,7 @@ The `update-task` command allows you to update a specific task instead of multip
 # Update a specific task with new information
 node scripts/dev.js update-task --id=4 --prompt="Use JWT for authentication"
 
-# With research-backed updates using your configured research model
+# With research-backed updates using Perplexity AI
 node scripts/dev.js update-task --id=4 --prompt="Use JWT for authentication" --research
 ```
 
@@ -178,10 +178,10 @@ node scripts/dev.js expand --all
 # Force regeneration of subtasks for all pending tasks
 node scripts/dev.js expand --all --force
 
-# Use your configured research model for research-backed subtask generation
+# Use Perplexity AI for research-backed subtask generation
 node scripts/dev.js expand --id=3 --research
 
-# Use your configured research model for research-backed generation on all pending tasks
+# Use Perplexity AI for research-backed generation on all pending tasks
 node scripts/dev.js expand --all --research
 ```
 
@@ -211,16 +211,17 @@ Notes:
 
 The script integrates with two AI services:
 
-1. **Main AI Model**: Used for parsing PRDs, generating tasks, and creating subtasks (typically Anthropic Claude).
-2. **Research Model**: Used for research-backed subtask generation when the `--research` flag is specified.
+1. **Anthropic Claude**: Used for parsing PRDs, generating tasks, and creating subtasks.
+2. **Perplexity AI**: Used for research-backed subtask generation when the `--research` flag is specified.
 
-The research integration provides enhanced research capabilities for generating more informed subtasks. You can configure different models for research (like Perplexity, which has access to current information) vs. main tasks. If the research model is unavailable or encounters an error, the script will automatically fall back to using your main model.
+The Perplexity integration uses the OpenAI client to connect to Perplexity's API, which provides enhanced research capabilities for generating more informed subtasks. If the Perplexity API is unavailable or encounters an error, the script will automatically fall back to using Anthropic's Claude.
 
-To use research-backed features:
+To use the Perplexity integration:
 
-1. Configure your research model using `task-master models --setup`
-2. Ensure you have the appropriate API key in your `.env` file (e.g., `PERPLEXITY_API_KEY` if using Perplexity)
-3. Use the `--research` flag with supported commands
+1. Obtain a Perplexity API key
+2. Add `PERPLEXITY_API_KEY` to your `.env` file
+3. Optionally specify `PERPLEXITY_MODEL` in your `.env` file (default: "sonar-medium-online")
+4. Use the `--research` flag with the `expand` command
 
 ## Logging
 
@@ -341,13 +342,13 @@ node scripts/dev.js analyze-complexity --model=claude-3-opus-20240229
 # Set a custom complexity threshold (1-10)
 node scripts/dev.js analyze-complexity --threshold=6
 
-# Use your configured research model for research-backed complexity analysis
+# Use Perplexity AI for research-backed complexity analysis
 node scripts/dev.js analyze-complexity --research
 ```
 
 Notes:
 
-- The command uses your main model to analyze each task's complexity (or your configured research model with --research flag)
+- The command uses Claude to analyze each task's complexity (or Perplexity with --research flag)
 - Tasks are scored on a scale of 1-10
 - Each task receives a recommended number of subtasks based on DEFAULT_SUBTASKS configuration
 - The default output path is `scripts/task-complexity-report.json`

CHANGELOG.md

@@ -1,5 +1,11 @@
 # task-master-ai
 
+## 0.27.1-rc.0
+
+### Patch Changes
+
+- [#1232](https://github.com/eyaltoledano/claude-task-master/pull/1232) [`f487736`](https://github.com/eyaltoledano/claude-task-master/commit/f487736670ef8c484059f676293777eabb249c9e) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Fix module not found for new 0.27.0 release
+
 ## 0.27.0
 
 ### Minor Changes

README-task-master.md

@@ -301,7 +301,7 @@ The agent will execute:
 task-master expand --all
 ```
 
-For research-backed subtask generation using your configured research model:
+For research-backed subtask generation using Perplexity AI:
 
 ```
 Please break down task 5 using research-backed generation.
@@ -450,7 +450,7 @@ task-master analyze-complexity --threshold=6
 # Use an alternative tasks file
 task-master analyze-complexity --file=custom-tasks.json
 
-# Use your configured research model for research-backed complexity analysis
+# Use Perplexity AI for research-backed complexity analysis
 task-master analyze-complexity --research
 ```
 

README.md

@@ -60,19 +60,6 @@ The following documentation is also available in the `docs` directory:
 
 > **Note:** After clicking the link, you'll still need to add your API keys to the configuration. The link installs the MCP server with placeholder keys that you'll need to replace with your actual API keys.
 
-#### Claude Code Quick Install
-
-For Claude Code users:
-
-```bash
-claude mcp add taskmaster-ai -- npx -y task-master-ai
-```
-
-Don't forget to add your API keys to the configuration:
-- in the root .env of your Project
-- in the "env" section of your mcp config for taskmaster-ai
-
-
 ## Requirements
 
 Taskmaster utilizes AI across several commands, and those require a separate API key. You can use a variety of models from different AI providers provided you add your API keys. For example, if you want to use Claude 3.7, you'll need an Anthropic API key.

apps/cli/package.json

@@ -1,6 +1,5 @@
 {
 	"name": "@tm/cli",
-	"version": "0.27.0",
 	"description": "Task Master CLI - Command line interface for task management",
 	"type": "module",
 	"private": true,
@@ -24,12 +23,12 @@
 	},
 	"dependencies": {
 		"@tm/core": "*",
-		"boxen": "^7.1.1",
+		"boxen": "^8.0.1",
 		"chalk": "5.6.2",
 		"cli-table3": "^0.6.5",
 		"commander": "^12.1.0",
-		"inquirer": "^9.2.10",
-		"ora": "^8.1.0"
+		"inquirer": "^12.5.0",
+		"ora": "^8.2.0"
 	},
 	"devDependencies": {
 		"@biomejs/biome": "^1.9.4",

apps/cli/src/index.ts

@@ -18,7 +18,8 @@ export * as ui from './utils/ui.js';
 export {
 	checkForUpdate,
 	performAutoUpdate,
-	displayUpgradeNotification
+	displayUpgradeNotification,
+	compareVersions
 } from './utils/auto-update.js';
 
 // Re-export commonly used types from tm-core

apps/cli/src/utils/auto-update.ts

@@ -7,7 +7,6 @@ import https from 'https';
 import chalk from 'chalk';
 import ora from 'ora';
 import boxen from 'boxen';
-import packageJson from '../../../../package.json' with { type: 'json' };
 
 export interface UpdateInfo {
 	currentVersion: string;
@@ -16,15 +15,18 @@ export interface UpdateInfo {
 }
 
 /**
- * Get current version from package.json
+ * Get current version from build-time injected environment variable
  */
 function getCurrentVersion(): string {
-	try {
-		return packageJson.version;
-	} catch (error) {
-		console.warn('Could not read package.json for version info');
-		return '0.0.0';
+	// Version is injected at build time via TM_PUBLIC_VERSION
+	const version = process.env.TM_PUBLIC_VERSION;
+	if (version && version !== 'unknown') {
+		return version;
 	}
+
+	// Fallback for development or if injection failed
+	console.warn('Could not read version from TM_PUBLIC_VERSION, using fallback');
+	return '0.0.0';
 }
 
 /**
@@ -33,7 +35,7 @@ function getCurrentVersion(): string {
  * @param v2 - Second version
  * @returns -1 if v1 < v2, 0 if v1 = v2, 1 if v1 > v2
  */
-function compareVersions(v1: string, v2: string): number {
+export function compareVersions(v1: string, v2: string): number {
 	const toParts = (v: string) => {
 		const [core, pre = ''] = v.split('-', 2);
 		const nums = core.split('.').map((n) => Number.parseInt(n, 10) || 0);

apps/docs/archive/ai-development-workflow.mdx

@@ -118,7 +118,7 @@ description: "Learn how Task Master and Cursor AI work together to streamline yo
     task-master expand --all
     ```
 
-    For research-backed subtask generation using configured research model:
+    For research-backed subtask generation using Perplexity AI:
 
     ```
     Please break down task 5 using research-backed generation.

apps/docs/archive/command-reference.mdx

@@ -61,7 +61,7 @@ description: "A comprehensive reference of all available Task Master commands"
     # Update a single task by ID with new information
     task-master update-task --id=<id> --prompt="<prompt>"
 
-    # Use research-backed updates with configured research model
+    # Use research-backed updates with Perplexity AI
     task-master update-task --id=<id> --prompt="<prompt>" --research
     ```
   </Accordion>
@@ -74,7 +74,7 @@ description: "A comprehensive reference of all available Task Master commands"
     # Example: Add details about API rate limiting to subtask 2 of task 5
     task-master update-subtask --id=5.2 --prompt="Add rate limiting of 100 requests per minute"
 
-    # Use research-backed updates with configured research model
+    # Use research-backed updates with Perplexity AI
     task-master update-subtask --id=<parentId.subtaskId> --prompt="<prompt>" --research
     ```
 
@@ -155,7 +155,7 @@ description: "A comprehensive reference of all available Task Master commands"
     # Use an alternative tasks file
     task-master analyze-complexity --file=custom-tasks.json
 
-    # Use configured research model for research-backed complexity analysis
+    # Use Perplexity AI for research-backed complexity analysis
     task-master analyze-complexity --research
     ```
   </Accordion>

apps/docs/capabilities/cli-root-commands.mdx

@@ -156,7 +156,7 @@ sidebarTitle: "CLI Commands"
     # Use an alternative tasks file
     task-master analyze-complexity --file=custom-tasks.json
 
-    # Use your configured research model for research-backed complexity analysis
+    # Use Perplexity AI for research-backed complexity analysis
     task-master analyze-complexity --research
     ```
   </Accordion>

apps/docs/getting-started/quick-start/installation.mdx

@@ -30,19 +30,6 @@ cursor://anysphere.cursor-deeplink/mcp/install?name=taskmaster-ai&config=eyJjb21
 ```
 
 > **Note:** After clicking the link, you'll still need to add your API keys to the configuration. The link installs the MCP server with placeholder keys that you'll need to replace with your actual API keys.
-
-### Claude Code Quick Install
-
-For Claude Code users:
-
-```bash
-claude mcp add taskmaster-ai -- npx -y task-master-ai
-```
-
-Don't forget to add your API keys to the configuration:
-- in the root .env of your Project
-- in the "env" section of your mcp config for taskmaster-ai
-
 </Accordion>
 ## Installation Options
 

apps/docs/getting-started/quick-start/tasks-quick.mdx

@@ -61,25 +61,9 @@ Task Master can provide a complexity report which can be helpful to read before
 Can you analyze the complexity of our tasks to help me understand which ones need to be broken down further?
 ```
 
-The agent will use the `analyze_project_complexity` MCP tool, or you can run it directly with the CLI command:
-```bash
-task-master analyze-complexity
-```
-
-For more comprehensive analysis using your configured research model, you can use:
-```bash
-task-master analyze-complexity --research
-```
-
-<Tip>
-The `--research` flag uses whatever research model you have configured in `.taskmaster/config.json` (configurable via `task-master models --setup`) for research-backed complexity analysis, providing more informed recommendations.
-</Tip>
-
 You can view the report in a friendly table using:
 ```
 Can you show me the complexity report in a more readable format?
 ```
 
-For more detailed CLI options, see the [Analyze Task Complexity](/docs/capabilities/cli-root-commands#analyze-task-complexity) section.
-
 <Check>Now you are ready to begin [executing tasks](/docs/getting-started/quick-start/execute-quick)</Check>

apps/extension/CHANGELOG.md

@@ -1,5 +1,12 @@
 # Change Log
 
+## 0.25.2-rc.0
+
+### Patch Changes
+
+- Updated dependencies [[`f487736`](https://github.com/eyaltoledano/claude-task-master/commit/f487736670ef8c484059f676293777eabb249c9e)]:
+  - task-master-ai@0.27.1-rc.0
+
 ## 0.25.0
 
 ### Minor Changes

apps/extension/package.json

@@ -3,7 +3,7 @@
 	"private": true,
 	"displayName": "TaskMaster",
 	"description": "A visual Kanban board interface for TaskMaster projects in VS Code",
-	"version": "0.25.0",
+	"version": "0.25.2-rc.0",
 	"publisher": "Hamster",
 	"icon": "assets/icon.png",
 	"engines": {
@@ -240,7 +240,7 @@
 		"check-types": "tsc --noEmit"
 	},
 	"dependencies": {
-		"task-master-ai": "*"
+		"task-master-ai": "0.27.1-rc.0"
 	},
 	"devDependencies": {
 		"@dnd-kit/core": "^6.3.1",
@@ -254,8 +254,9 @@
 		"@radix-ui/react-separator": "^1.1.7",
 		"@radix-ui/react-slot": "^1.2.3",
 		"@tailwindcss/postcss": "^4.1.11",
+		"@tanstack/react-query": "^5.83.0",
 		"@types/mocha": "^10.0.10",
-		"@types/node": "20.x",
+		"@types/node": "^22.10.5",
 		"@types/react": "19.1.8",
 		"@types/react-dom": "19.1.6",
 		"@types/vscode": "^1.101.0",
@@ -271,12 +272,11 @@
 		"lucide-react": "^0.525.0",
 		"npm-run-all": "^4.1.5",
 		"postcss": "8.5.6",
+		"react": "^19.0.0",
+		"react-dom": "^19.0.0",
 		"tailwind-merge": "^3.3.1",
 		"tailwindcss": "4.1.11",
-		"typescript": "^5.8.3",
-		"@tanstack/react-query": "^5.83.0",
-		"react": "^19.0.0",
-		"react-dom": "^19.0.0"
+		"typescript": "^5.7.3"
 	},
 	"overrides": {
 		"glob@<8": "^10.4.5",

assets/.windsurfrules

@@ -60,7 +60,7 @@ alwaysApply: true
 
   - For tasks with complexity analysis, use `node scripts/dev.js expand --id=<id>`
   - Otherwise use `node scripts/dev.js expand --id=<id> --subtasks=<number>`
-  - Add `--research` flag to leverage your configured research model for research-backed expansion
+  - Add `--research` flag to leverage Perplexity AI for research-backed expansion
   - Use `--prompt="<context>"` to provide additional context when needed
   - Review and adjust generated subtasks as necessary
   - Use `--all` flag to expand multiple pending tasks at once
@@ -160,7 +160,7 @@ alwaysApply: true
     - `--id=<id>`: ID of task to expand (required unless using --all)
     - `--all`: Expand all pending tasks, prioritized by complexity
     - `--num=<number>`: Number of subtasks to generate (default: from complexity report)
-    - `--research`: Use your configured research model for research-backed generation
+    - `--research`: Use Perplexity AI for research-backed generation
     - `--prompt="<text>"`: Additional context for subtask generation
     - `--force`: Regenerate subtasks even for tasks that already have them
   - Example: `task-master expand --id=3 --num=5 --research --prompt="Focus on security aspects"`
@@ -176,7 +176,7 @@ alwaysApply: true
     - `--model=<model>, -m`: Override LLM model to use
     - `--threshold=<number>, -t`: Minimum score for expansion recommendation (default: 5)
     - `--file=<path>, -f`: Use alternative tasks.json file
-    - `--research, -r`: Use your configured research model for research-backed analysis
+    - `--research, -r`: Use Perplexity AI for research-backed analysis
   - Example: `task-master analyze-complexity --research`
   - Notes: Report includes complexity scores, recommended subtasks, and tailored prompts.
 

assets/claude/commands/tm/analyze-complexity/analyze-complexity.md

@@ -16,7 +16,7 @@ task-master analyze-complexity [--research] [--threshold=5]
 
 ## Analysis Parameters
 
-- `--research` → Use configured research model for deeper analysis
+- `--research` → Use research AI for deeper analysis
 - `--threshold=5` → Only flag tasks above complexity 5
 - Default: Analyze all pending tasks
 

assets/rules/dev_workflow.mdc

@@ -231,7 +231,7 @@ Taskmaster offers two primary ways to interact:
 
 -   Use `expand_task` / `task-master expand --id=<id>`. It automatically uses the complexity report if found, otherwise generates default number of subtasks.
 -   Use `--num=<number>` to specify an explicit number of subtasks, overriding defaults or complexity report recommendations.
--   Add `--research` flag to leverage your configured research model for research-backed expansion.
+-   Add `--research` flag to leverage Perplexity AI for research-backed expansion.
 -   Add `--force` flag to clear existing subtasks before generating new ones (default is to append).
 -   Use `--prompt="<context>"` to provide additional context when needed.
 -   Review and adjust generated subtasks as necessary.