209 lines
6.8 KiB
JavaScript
Raw Normal View History

chore: Remove unused imports across modules Removes unused import statements identified after the major refactoring of the AI service layer and other components. This cleanup improves code clarity and removes unnecessary dependencies. Unused imports removed from: - **`mcp-server/src/core/direct-functions/analyze-task-complexity.js`:** - Removed `path` - **`mcp-server/src/core/direct-functions/complexity-report.js`:** - Removed `path` - **`mcp-server/src/core/direct-functions/expand-all-tasks.js`:** - Removed `path`, `fs` - **`mcp-server/src/core/direct-functions/generate-task-files.js`:** - Removed `path` - **`mcp-server/src/core/direct-functions/parse-prd.js`:** - Removed `os`, `findTasksJsonPath` - **`mcp-server/src/core/direct-functions/update-tasks.js`:** - Removed `isSilentMode` - **`mcp-server/src/tools/add-task.js`:** - Removed `createContentResponse`, `executeTaskMasterCommand` - **`mcp-server/src/tools/analyze.js`:** - Removed `getProjectRootFromSession` (as `projectRoot` is now required in args) - **`mcp-server/src/tools/expand-task.js`:** - Removed `path` - **`mcp-server/src/tools/initialize-project.js`:** - Removed `createContentResponse` - **`mcp-server/src/tools/parse-prd.js`:** - Removed `findPRDDocumentPath`, `resolveTasksOutputPath` (logic moved or handled by `resolveProjectPaths`) - **`mcp-server/src/tools/update.js`:** - Removed `getProjectRootFromSession` (as `projectRoot` is now required in args) - **`scripts/modules/commands.js`:** - Removed `exec`, `readline` - Removed AI config getters (`getMainModelId`, etc.) - Removed MCP helpers (`getMcpApiKeyStatus`) - **`scripts/modules/config-manager.js`:** - Removed `ZodError`, `readJSON`, `writeJSON` - **`scripts/modules/task-manager/analyze-task-complexity.js`:** - Removed AI config getters (`getMainModelId`, etc.) - **`scripts/modules/task-manager/expand-all-tasks.js`:** - Removed `fs`, `path`, `writeJSON` - **`scripts/modules/task-manager/models.js`:** - Removed `VALID_PROVIDERS` - **`scripts/modules/task-manager/update-subtask-by-id.js`:** - Removed AI config getters (`getMainModelId`, etc.) - **`scripts/modules/task-manager/update-tasks.js`:** - Removed AI config getters (`getMainModelId`, etc.) - **`scripts/modules/ui.js`:** - Removed `getDebugFlag` - **`scripts/modules/utils.js`:** - Removed `ZodError`
2025-04-25 15:11:55 -04:00
import { log, readJSON, isSilentMode } from '../utils.js';
feat(telemetry): Integrate telemetry for expand-all, aggregate results This commit implements AI usage telemetry for the `expand-all-tasks` command/tool and refactors its CLI output for clarity and consistency. Key Changes: 1. **Telemetry Integration for `expand-all-tasks` (Subtask 77.8):**\n - The `expandAllTasks` core logic (`scripts/modules/task-manager/expand-all-tasks.js`) now calls the `expandTask` function for each eligible task and collects the individual `telemetryData` returned.\n - A new helper function `_aggregateTelemetry` (in `utils.js`) is used to sum up token counts and costs from all individual expansions into a single `telemetryData` object for the entire `expand-all` operation.\n - The `expandAllTasksDirect` wrapper (`mcp-server/src/core/direct-functions/expand-all-tasks.js`) now receives and passes this aggregated `telemetryData` in the MCP response.\n - For CLI usage, `displayAiUsageSummary` is called once with the aggregated telemetry. 2. **Improved CLI Output for `expand-all`:**\n - The `expandAllTasks` core function now handles displaying a final "Expansion Summary" box (showing Attempted, Expanded, Skipped, Failed counts) directly after the aggregated telemetry summary.\n - This consolidates all summary output within the core function for better flow and removes redundant logging from the command action in `scripts/modules/commands.js`.\n - The summary box border is green for success and red if any expansions failed. 3. **Code Refinements:**\n - Ensured `chalk` and `boxen` are imported in `expand-all-tasks.js` for the new summary box.\n - Minor adjustments to logging messages for clarity.
2025-05-08 18:22:00 -04:00
import {
startLoadingIndicator,
stopLoadingIndicator,
displayAiUsageSummary
} from '../ui.js';
refactor(expand/all): Implement additive expansion and complexity report integration Refactors the `expandTask` and `expandAllTasks` features to complete subtask 61.38 and enhance functionality based on subtask 61.37's refactor. Key Changes: - **Additive Expansion (`expandTask`, `expandAllTasks`):** - Modified `expandTask` default behavior to append newly generated subtasks to any existing ones. - Added a `force` flag (passed down from CLI/MCP via `--force` option/parameter) to `expandTask` and `expandAllTasks`. When `force` is true, existing subtasks are cleared before generating new ones. - Updated relevant CLI command (`expand`), MCP tool (`expand_task`, `expand_all`), and direct function wrappers (`expandTaskDirect`, `expandAllTasksDirect`) to handle and pass the `force` flag. - **Complexity Report Integration (`expandTask`):** - `expandTask` now reads `scripts/task-complexity-report.json`. - If an analysis entry exists for the target task: - `recommendedSubtasks` is used to determine the number of subtasks to generate (unless `--num` is explicitly provided). - `expansionPrompt` is used as the primary prompt content for the AI. - `reasoning` is appended to any additional context provided. - If no report entry exists or the report is missing, it falls back to default subtask count (from config) and standard prompt generation. - **`expandAllTasks` Orchestration:** - Refactored `expandAllTasks` to primarily iterate through eligible tasks (pending/in-progress, considering `force` flag and existing subtasks) and call the updated `expandTask` function for each. - Removed redundant logic (like complexity reading or explicit subtask clearing) now handled within `expandTask`. - Ensures correct context (`session`, `mcpLog`) and flags (`useResearch`, `force`) are passed down. - **Configuration & Cleanup:** - Updated `.cursor/mcp.json` with new Perplexity/Anthropic API keys (old ones invalidated). - Completed refactoring of `expandTask` started in 61.37, confirming usage of `generateTextService` and appropriate prompts. - **Task Management:** - Marked subtask 61.37 as complete. - Updated `.changeset/cuddly-zebras-matter.md` to reflect user-facing changes. These changes finalize the refactoring of the task expansion features, making them more robust, configurable via complexity analysis, and aligned with the unified AI service architecture.
2025-04-25 02:57:08 -04:00
import expandTask from './expand-task.js';
import { getDebugFlag } from '../config-manager.js';
import { aggregateTelemetry } from '../utils.js';
feat(telemetry): Integrate telemetry for expand-all, aggregate results This commit implements AI usage telemetry for the `expand-all-tasks` command/tool and refactors its CLI output for clarity and consistency. Key Changes: 1. **Telemetry Integration for `expand-all-tasks` (Subtask 77.8):**\n - The `expandAllTasks` core logic (`scripts/modules/task-manager/expand-all-tasks.js`) now calls the `expandTask` function for each eligible task and collects the individual `telemetryData` returned.\n - A new helper function `_aggregateTelemetry` (in `utils.js`) is used to sum up token counts and costs from all individual expansions into a single `telemetryData` object for the entire `expand-all` operation.\n - The `expandAllTasksDirect` wrapper (`mcp-server/src/core/direct-functions/expand-all-tasks.js`) now receives and passes this aggregated `telemetryData` in the MCP response.\n - For CLI usage, `displayAiUsageSummary` is called once with the aggregated telemetry. 2. **Improved CLI Output for `expand-all`:**\n - The `expandAllTasks` core function now handles displaying a final "Expansion Summary" box (showing Attempted, Expanded, Skipped, Failed counts) directly after the aggregated telemetry summary.\n - This consolidates all summary output within the core function for better flow and removes redundant logging from the command action in `scripts/modules/commands.js`.\n - The summary box border is green for success and red if any expansions failed. 3. **Code Refinements:**\n - Ensured `chalk` and `boxen` are imported in `expand-all-tasks.js` for the new summary box.\n - Minor adjustments to logging messages for clarity.
2025-05-08 18:22:00 -04:00
import chalk from 'chalk';
import boxen from 'boxen';
/**
refactor(expand/all): Implement additive expansion and complexity report integration Refactors the `expandTask` and `expandAllTasks` features to complete subtask 61.38 and enhance functionality based on subtask 61.37's refactor. Key Changes: - **Additive Expansion (`expandTask`, `expandAllTasks`):** - Modified `expandTask` default behavior to append newly generated subtasks to any existing ones. - Added a `force` flag (passed down from CLI/MCP via `--force` option/parameter) to `expandTask` and `expandAllTasks`. When `force` is true, existing subtasks are cleared before generating new ones. - Updated relevant CLI command (`expand`), MCP tool (`expand_task`, `expand_all`), and direct function wrappers (`expandTaskDirect`, `expandAllTasksDirect`) to handle and pass the `force` flag. - **Complexity Report Integration (`expandTask`):** - `expandTask` now reads `scripts/task-complexity-report.json`. - If an analysis entry exists for the target task: - `recommendedSubtasks` is used to determine the number of subtasks to generate (unless `--num` is explicitly provided). - `expansionPrompt` is used as the primary prompt content for the AI. - `reasoning` is appended to any additional context provided. - If no report entry exists or the report is missing, it falls back to default subtask count (from config) and standard prompt generation. - **`expandAllTasks` Orchestration:** - Refactored `expandAllTasks` to primarily iterate through eligible tasks (pending/in-progress, considering `force` flag and existing subtasks) and call the updated `expandTask` function for each. - Removed redundant logic (like complexity reading or explicit subtask clearing) now handled within `expandTask`. - Ensures correct context (`session`, `mcpLog`) and flags (`useResearch`, `force`) are passed down. - **Configuration & Cleanup:** - Updated `.cursor/mcp.json` with new Perplexity/Anthropic API keys (old ones invalidated). - Completed refactoring of `expandTask` started in 61.37, confirming usage of `generateTextService` and appropriate prompts. - **Task Management:** - Marked subtask 61.37 as complete. - Updated `.changeset/cuddly-zebras-matter.md` to reflect user-facing changes. These changes finalize the refactoring of the task expansion features, making them more robust, configurable via complexity analysis, and aligned with the unified AI service architecture.
2025-04-25 02:57:08 -04:00
* Expand all eligible pending or in-progress tasks using the expandTask function.
* @param {string} tasksPath - Path to the tasks.json file
refactor(expand/all): Implement additive expansion and complexity report integration Refactors the `expandTask` and `expandAllTasks` features to complete subtask 61.38 and enhance functionality based on subtask 61.37's refactor. Key Changes: - **Additive Expansion (`expandTask`, `expandAllTasks`):** - Modified `expandTask` default behavior to append newly generated subtasks to any existing ones. - Added a `force` flag (passed down from CLI/MCP via `--force` option/parameter) to `expandTask` and `expandAllTasks`. When `force` is true, existing subtasks are cleared before generating new ones. - Updated relevant CLI command (`expand`), MCP tool (`expand_task`, `expand_all`), and direct function wrappers (`expandTaskDirect`, `expandAllTasksDirect`) to handle and pass the `force` flag. - **Complexity Report Integration (`expandTask`):** - `expandTask` now reads `scripts/task-complexity-report.json`. - If an analysis entry exists for the target task: - `recommendedSubtasks` is used to determine the number of subtasks to generate (unless `--num` is explicitly provided). - `expansionPrompt` is used as the primary prompt content for the AI. - `reasoning` is appended to any additional context provided. - If no report entry exists or the report is missing, it falls back to default subtask count (from config) and standard prompt generation. - **`expandAllTasks` Orchestration:** - Refactored `expandAllTasks` to primarily iterate through eligible tasks (pending/in-progress, considering `force` flag and existing subtasks) and call the updated `expandTask` function for each. - Removed redundant logic (like complexity reading or explicit subtask clearing) now handled within `expandTask`. - Ensures correct context (`session`, `mcpLog`) and flags (`useResearch`, `force`) are passed down. - **Configuration & Cleanup:** - Updated `.cursor/mcp.json` with new Perplexity/Anthropic API keys (old ones invalidated). - Completed refactoring of `expandTask` started in 61.37, confirming usage of `generateTextService` and appropriate prompts. - **Task Management:** - Marked subtask 61.37 as complete. - Updated `.changeset/cuddly-zebras-matter.md` to reflect user-facing changes. These changes finalize the refactoring of the task expansion features, making them more robust, configurable via complexity analysis, and aligned with the unified AI service architecture.
2025-04-25 02:57:08 -04:00
* @param {number} [numSubtasks] - Optional: Target number of subtasks per task.
* @param {boolean} [useResearch=false] - Whether to use the research AI role.
* @param {string} [additionalContext=''] - Optional additional context.
* @param {boolean} [force=false] - Force expansion even if tasks already have subtasks.
* @param {Object} context - Context object containing session and mcpLog.
* @param {Object} [context.session] - Session object from MCP.
* @param {Object} [context.mcpLog] - MCP logger object.
* @param {string} [outputFormat='text'] - Output format ('text' or 'json'). MCP calls should use 'json'.
feat(telemetry): Integrate telemetry for expand-all, aggregate results This commit implements AI usage telemetry for the `expand-all-tasks` command/tool and refactors its CLI output for clarity and consistency. Key Changes: 1. **Telemetry Integration for `expand-all-tasks` (Subtask 77.8):**\n - The `expandAllTasks` core logic (`scripts/modules/task-manager/expand-all-tasks.js`) now calls the `expandTask` function for each eligible task and collects the individual `telemetryData` returned.\n - A new helper function `_aggregateTelemetry` (in `utils.js`) is used to sum up token counts and costs from all individual expansions into a single `telemetryData` object for the entire `expand-all` operation.\n - The `expandAllTasksDirect` wrapper (`mcp-server/src/core/direct-functions/expand-all-tasks.js`) now receives and passes this aggregated `telemetryData` in the MCP response.\n - For CLI usage, `displayAiUsageSummary` is called once with the aggregated telemetry. 2. **Improved CLI Output for `expand-all`:**\n - The `expandAllTasks` core function now handles displaying a final "Expansion Summary" box (showing Attempted, Expanded, Skipped, Failed counts) directly after the aggregated telemetry summary.\n - This consolidates all summary output within the core function for better flow and removes redundant logging from the command action in `scripts/modules/commands.js`.\n - The summary box border is green for success and red if any expansions failed. 3. **Code Refinements:**\n - Ensured `chalk` and `boxen` are imported in `expand-all-tasks.js` for the new summary box.\n - Minor adjustments to logging messages for clarity.
2025-05-08 18:22:00 -04:00
* @returns {Promise<{success: boolean, expandedCount: number, failedCount: number, skippedCount: number, tasksToExpand: number, telemetryData: Array<Object>}>} - Result summary.
*/
async function expandAllTasks(
tasksPath,
refactor(expand/all): Implement additive expansion and complexity report integration Refactors the `expandTask` and `expandAllTasks` features to complete subtask 61.38 and enhance functionality based on subtask 61.37's refactor. Key Changes: - **Additive Expansion (`expandTask`, `expandAllTasks`):** - Modified `expandTask` default behavior to append newly generated subtasks to any existing ones. - Added a `force` flag (passed down from CLI/MCP via `--force` option/parameter) to `expandTask` and `expandAllTasks`. When `force` is true, existing subtasks are cleared before generating new ones. - Updated relevant CLI command (`expand`), MCP tool (`expand_task`, `expand_all`), and direct function wrappers (`expandTaskDirect`, `expandAllTasksDirect`) to handle and pass the `force` flag. - **Complexity Report Integration (`expandTask`):** - `expandTask` now reads `scripts/task-complexity-report.json`. - If an analysis entry exists for the target task: - `recommendedSubtasks` is used to determine the number of subtasks to generate (unless `--num` is explicitly provided). - `expansionPrompt` is used as the primary prompt content for the AI. - `reasoning` is appended to any additional context provided. - If no report entry exists or the report is missing, it falls back to default subtask count (from config) and standard prompt generation. - **`expandAllTasks` Orchestration:** - Refactored `expandAllTasks` to primarily iterate through eligible tasks (pending/in-progress, considering `force` flag and existing subtasks) and call the updated `expandTask` function for each. - Removed redundant logic (like complexity reading or explicit subtask clearing) now handled within `expandTask`. - Ensures correct context (`session`, `mcpLog`) and flags (`useResearch`, `force`) are passed down. - **Configuration & Cleanup:** - Updated `.cursor/mcp.json` with new Perplexity/Anthropic API keys (old ones invalidated). - Completed refactoring of `expandTask` started in 61.37, confirming usage of `generateTextService` and appropriate prompts. - **Task Management:** - Marked subtask 61.37 as complete. - Updated `.changeset/cuddly-zebras-matter.md` to reflect user-facing changes. These changes finalize the refactoring of the task expansion features, making them more robust, configurable via complexity analysis, and aligned with the unified AI service architecture.
2025-04-25 02:57:08 -04:00
numSubtasks, // Keep this signature, expandTask handles defaults
useResearch = false,
additionalContext = '',
refactor(expand/all): Implement additive expansion and complexity report integration Refactors the `expandTask` and `expandAllTasks` features to complete subtask 61.38 and enhance functionality based on subtask 61.37's refactor. Key Changes: - **Additive Expansion (`expandTask`, `expandAllTasks`):** - Modified `expandTask` default behavior to append newly generated subtasks to any existing ones. - Added a `force` flag (passed down from CLI/MCP via `--force` option/parameter) to `expandTask` and `expandAllTasks`. When `force` is true, existing subtasks are cleared before generating new ones. - Updated relevant CLI command (`expand`), MCP tool (`expand_task`, `expand_all`), and direct function wrappers (`expandTaskDirect`, `expandAllTasksDirect`) to handle and pass the `force` flag. - **Complexity Report Integration (`expandTask`):** - `expandTask` now reads `scripts/task-complexity-report.json`. - If an analysis entry exists for the target task: - `recommendedSubtasks` is used to determine the number of subtasks to generate (unless `--num` is explicitly provided). - `expansionPrompt` is used as the primary prompt content for the AI. - `reasoning` is appended to any additional context provided. - If no report entry exists or the report is missing, it falls back to default subtask count (from config) and standard prompt generation. - **`expandAllTasks` Orchestration:** - Refactored `expandAllTasks` to primarily iterate through eligible tasks (pending/in-progress, considering `force` flag and existing subtasks) and call the updated `expandTask` function for each. - Removed redundant logic (like complexity reading or explicit subtask clearing) now handled within `expandTask`. - Ensures correct context (`session`, `mcpLog`) and flags (`useResearch`, `force`) are passed down. - **Configuration & Cleanup:** - Updated `.cursor/mcp.json` with new Perplexity/Anthropic API keys (old ones invalidated). - Completed refactoring of `expandTask` started in 61.37, confirming usage of `generateTextService` and appropriate prompts. - **Task Management:** - Marked subtask 61.37 as complete. - Updated `.changeset/cuddly-zebras-matter.md` to reflect user-facing changes. These changes finalize the refactoring of the task expansion features, making them more robust, configurable via complexity analysis, and aligned with the unified AI service architecture.
2025-04-25 02:57:08 -04:00
force = false, // Keep force here for the filter logic
context = {},
outputFormat = 'text' // Assume text default for CLI
) {
refactor(expand/all): Implement additive expansion and complexity report integration Refactors the `expandTask` and `expandAllTasks` features to complete subtask 61.38 and enhance functionality based on subtask 61.37's refactor. Key Changes: - **Additive Expansion (`expandTask`, `expandAllTasks`):** - Modified `expandTask` default behavior to append newly generated subtasks to any existing ones. - Added a `force` flag (passed down from CLI/MCP via `--force` option/parameter) to `expandTask` and `expandAllTasks`. When `force` is true, existing subtasks are cleared before generating new ones. - Updated relevant CLI command (`expand`), MCP tool (`expand_task`, `expand_all`), and direct function wrappers (`expandTaskDirect`, `expandAllTasksDirect`) to handle and pass the `force` flag. - **Complexity Report Integration (`expandTask`):** - `expandTask` now reads `scripts/task-complexity-report.json`. - If an analysis entry exists for the target task: - `recommendedSubtasks` is used to determine the number of subtasks to generate (unless `--num` is explicitly provided). - `expansionPrompt` is used as the primary prompt content for the AI. - `reasoning` is appended to any additional context provided. - If no report entry exists or the report is missing, it falls back to default subtask count (from config) and standard prompt generation. - **`expandAllTasks` Orchestration:** - Refactored `expandAllTasks` to primarily iterate through eligible tasks (pending/in-progress, considering `force` flag and existing subtasks) and call the updated `expandTask` function for each. - Removed redundant logic (like complexity reading or explicit subtask clearing) now handled within `expandTask`. - Ensures correct context (`session`, `mcpLog`) and flags (`useResearch`, `force`) are passed down. - **Configuration & Cleanup:** - Updated `.cursor/mcp.json` with new Perplexity/Anthropic API keys (old ones invalidated). - Completed refactoring of `expandTask` started in 61.37, confirming usage of `generateTextService` and appropriate prompts. - **Task Management:** - Marked subtask 61.37 as complete. - Updated `.changeset/cuddly-zebras-matter.md` to reflect user-facing changes. These changes finalize the refactoring of the task expansion features, making them more robust, configurable via complexity analysis, and aligned with the unified AI service architecture.
2025-04-25 02:57:08 -04:00
const { session, mcpLog } = context;
const isMCPCall = !!mcpLog; // Determine if called from MCP
// Use mcpLog if available, otherwise use the default console log wrapper respecting silent mode
const logger =
mcpLog ||
(outputFormat === 'json'
? {
// Basic logger for JSON output mode
info: (msg) => {},
warn: (msg) => {},
error: (msg) => console.error(`ERROR: ${msg}`), // Still log errors
debug: (msg) => {}
}
: {
// CLI logger respecting silent mode
info: (msg) => !isSilentMode() && log('info', msg),
warn: (msg) => !isSilentMode() && log('warn', msg),
error: (msg) => !isSilentMode() && log('error', msg),
debug: (msg) =>
!isSilentMode() && getDebugFlag(session) && log('debug', msg)
});
refactor(expand/all): Implement additive expansion and complexity report integration Refactors the `expandTask` and `expandAllTasks` features to complete subtask 61.38 and enhance functionality based on subtask 61.37's refactor. Key Changes: - **Additive Expansion (`expandTask`, `expandAllTasks`):** - Modified `expandTask` default behavior to append newly generated subtasks to any existing ones. - Added a `force` flag (passed down from CLI/MCP via `--force` option/parameter) to `expandTask` and `expandAllTasks`. When `force` is true, existing subtasks are cleared before generating new ones. - Updated relevant CLI command (`expand`), MCP tool (`expand_task`, `expand_all`), and direct function wrappers (`expandTaskDirect`, `expandAllTasksDirect`) to handle and pass the `force` flag. - **Complexity Report Integration (`expandTask`):** - `expandTask` now reads `scripts/task-complexity-report.json`. - If an analysis entry exists for the target task: - `recommendedSubtasks` is used to determine the number of subtasks to generate (unless `--num` is explicitly provided). - `expansionPrompt` is used as the primary prompt content for the AI. - `reasoning` is appended to any additional context provided. - If no report entry exists or the report is missing, it falls back to default subtask count (from config) and standard prompt generation. - **`expandAllTasks` Orchestration:** - Refactored `expandAllTasks` to primarily iterate through eligible tasks (pending/in-progress, considering `force` flag and existing subtasks) and call the updated `expandTask` function for each. - Removed redundant logic (like complexity reading or explicit subtask clearing) now handled within `expandTask`. - Ensures correct context (`session`, `mcpLog`) and flags (`useResearch`, `force`) are passed down. - **Configuration & Cleanup:** - Updated `.cursor/mcp.json` with new Perplexity/Anthropic API keys (old ones invalidated). - Completed refactoring of `expandTask` started in 61.37, confirming usage of `generateTextService` and appropriate prompts. - **Task Management:** - Marked subtask 61.37 as complete. - Updated `.changeset/cuddly-zebras-matter.md` to reflect user-facing changes. These changes finalize the refactoring of the task expansion features, making them more robust, configurable via complexity analysis, and aligned with the unified AI service architecture.
2025-04-25 02:57:08 -04:00
let loadingIndicator = null;
let expandedCount = 0;
let failedCount = 0;
feat(telemetry): Integrate telemetry for expand-all, aggregate results This commit implements AI usage telemetry for the `expand-all-tasks` command/tool and refactors its CLI output for clarity and consistency. Key Changes: 1. **Telemetry Integration for `expand-all-tasks` (Subtask 77.8):**\n - The `expandAllTasks` core logic (`scripts/modules/task-manager/expand-all-tasks.js`) now calls the `expandTask` function for each eligible task and collects the individual `telemetryData` returned.\n - A new helper function `_aggregateTelemetry` (in `utils.js`) is used to sum up token counts and costs from all individual expansions into a single `telemetryData` object for the entire `expand-all` operation.\n - The `expandAllTasksDirect` wrapper (`mcp-server/src/core/direct-functions/expand-all-tasks.js`) now receives and passes this aggregated `telemetryData` in the MCP response.\n - For CLI usage, `displayAiUsageSummary` is called once with the aggregated telemetry. 2. **Improved CLI Output for `expand-all`:**\n - The `expandAllTasks` core function now handles displaying a final "Expansion Summary" box (showing Attempted, Expanded, Skipped, Failed counts) directly after the aggregated telemetry summary.\n - This consolidates all summary output within the core function for better flow and removes redundant logging from the command action in `scripts/modules/commands.js`.\n - The summary box border is green for success and red if any expansions failed. 3. **Code Refinements:**\n - Ensured `chalk` and `boxen` are imported in `expand-all-tasks.js` for the new summary box.\n - Minor adjustments to logging messages for clarity.
2025-05-08 18:22:00 -04:00
let tasksToExpandCount = 0;
const allTelemetryData = []; // Still collect individual data first
refactor(expand/all): Implement additive expansion and complexity report integration Refactors the `expandTask` and `expandAllTasks` features to complete subtask 61.38 and enhance functionality based on subtask 61.37's refactor. Key Changes: - **Additive Expansion (`expandTask`, `expandAllTasks`):** - Modified `expandTask` default behavior to append newly generated subtasks to any existing ones. - Added a `force` flag (passed down from CLI/MCP via `--force` option/parameter) to `expandTask` and `expandAllTasks`. When `force` is true, existing subtasks are cleared before generating new ones. - Updated relevant CLI command (`expand`), MCP tool (`expand_task`, `expand_all`), and direct function wrappers (`expandTaskDirect`, `expandAllTasksDirect`) to handle and pass the `force` flag. - **Complexity Report Integration (`expandTask`):** - `expandTask` now reads `scripts/task-complexity-report.json`. - If an analysis entry exists for the target task: - `recommendedSubtasks` is used to determine the number of subtasks to generate (unless `--num` is explicitly provided). - `expansionPrompt` is used as the primary prompt content for the AI. - `reasoning` is appended to any additional context provided. - If no report entry exists or the report is missing, it falls back to default subtask count (from config) and standard prompt generation. - **`expandAllTasks` Orchestration:** - Refactored `expandAllTasks` to primarily iterate through eligible tasks (pending/in-progress, considering `force` flag and existing subtasks) and call the updated `expandTask` function for each. - Removed redundant logic (like complexity reading or explicit subtask clearing) now handled within `expandTask`. - Ensures correct context (`session`, `mcpLog`) and flags (`useResearch`, `force`) are passed down. - **Configuration & Cleanup:** - Updated `.cursor/mcp.json` with new Perplexity/Anthropic API keys (old ones invalidated). - Completed refactoring of `expandTask` started in 61.37, confirming usage of `generateTextService` and appropriate prompts. - **Task Management:** - Marked subtask 61.37 as complete. - Updated `.changeset/cuddly-zebras-matter.md` to reflect user-facing changes. These changes finalize the refactoring of the task expansion features, making them more robust, configurable via complexity analysis, and aligned with the unified AI service architecture.
2025-04-25 02:57:08 -04:00
if (!isMCPCall && outputFormat === 'text') {
loadingIndicator = startLoadingIndicator(
'Analyzing tasks for expansion...'
);
}
try {
refactor(expand/all): Implement additive expansion and complexity report integration Refactors the `expandTask` and `expandAllTasks` features to complete subtask 61.38 and enhance functionality based on subtask 61.37's refactor. Key Changes: - **Additive Expansion (`expandTask`, `expandAllTasks`):** - Modified `expandTask` default behavior to append newly generated subtasks to any existing ones. - Added a `force` flag (passed down from CLI/MCP via `--force` option/parameter) to `expandTask` and `expandAllTasks`. When `force` is true, existing subtasks are cleared before generating new ones. - Updated relevant CLI command (`expand`), MCP tool (`expand_task`, `expand_all`), and direct function wrappers (`expandTaskDirect`, `expandAllTasksDirect`) to handle and pass the `force` flag. - **Complexity Report Integration (`expandTask`):** - `expandTask` now reads `scripts/task-complexity-report.json`. - If an analysis entry exists for the target task: - `recommendedSubtasks` is used to determine the number of subtasks to generate (unless `--num` is explicitly provided). - `expansionPrompt` is used as the primary prompt content for the AI. - `reasoning` is appended to any additional context provided. - If no report entry exists or the report is missing, it falls back to default subtask count (from config) and standard prompt generation. - **`expandAllTasks` Orchestration:** - Refactored `expandAllTasks` to primarily iterate through eligible tasks (pending/in-progress, considering `force` flag and existing subtasks) and call the updated `expandTask` function for each. - Removed redundant logic (like complexity reading or explicit subtask clearing) now handled within `expandTask`. - Ensures correct context (`session`, `mcpLog`) and flags (`useResearch`, `force`) are passed down. - **Configuration & Cleanup:** - Updated `.cursor/mcp.json` with new Perplexity/Anthropic API keys (old ones invalidated). - Completed refactoring of `expandTask` started in 61.37, confirming usage of `generateTextService` and appropriate prompts. - **Task Management:** - Marked subtask 61.37 as complete. - Updated `.changeset/cuddly-zebras-matter.md` to reflect user-facing changes. These changes finalize the refactoring of the task expansion features, making them more robust, configurable via complexity analysis, and aligned with the unified AI service architecture.
2025-04-25 02:57:08 -04:00
logger.info(`Reading tasks from ${tasksPath}`);
const data = readJSON(tasksPath);
if (!data || !data.tasks) {
refactor(expand/all): Implement additive expansion and complexity report integration Refactors the `expandTask` and `expandAllTasks` features to complete subtask 61.38 and enhance functionality based on subtask 61.37's refactor. Key Changes: - **Additive Expansion (`expandTask`, `expandAllTasks`):** - Modified `expandTask` default behavior to append newly generated subtasks to any existing ones. - Added a `force` flag (passed down from CLI/MCP via `--force` option/parameter) to `expandTask` and `expandAllTasks`. When `force` is true, existing subtasks are cleared before generating new ones. - Updated relevant CLI command (`expand`), MCP tool (`expand_task`, `expand_all`), and direct function wrappers (`expandTaskDirect`, `expandAllTasksDirect`) to handle and pass the `force` flag. - **Complexity Report Integration (`expandTask`):** - `expandTask` now reads `scripts/task-complexity-report.json`. - If an analysis entry exists for the target task: - `recommendedSubtasks` is used to determine the number of subtasks to generate (unless `--num` is explicitly provided). - `expansionPrompt` is used as the primary prompt content for the AI. - `reasoning` is appended to any additional context provided. - If no report entry exists or the report is missing, it falls back to default subtask count (from config) and standard prompt generation. - **`expandAllTasks` Orchestration:** - Refactored `expandAllTasks` to primarily iterate through eligible tasks (pending/in-progress, considering `force` flag and existing subtasks) and call the updated `expandTask` function for each. - Removed redundant logic (like complexity reading or explicit subtask clearing) now handled within `expandTask`. - Ensures correct context (`session`, `mcpLog`) and flags (`useResearch`, `force`) are passed down. - **Configuration & Cleanup:** - Updated `.cursor/mcp.json` with new Perplexity/Anthropic API keys (old ones invalidated). - Completed refactoring of `expandTask` started in 61.37, confirming usage of `generateTextService` and appropriate prompts. - **Task Management:** - Marked subtask 61.37 as complete. - Updated `.changeset/cuddly-zebras-matter.md` to reflect user-facing changes. These changes finalize the refactoring of the task expansion features, making them more robust, configurable via complexity analysis, and aligned with the unified AI service architecture.
2025-04-25 02:57:08 -04:00
throw new Error(`Invalid tasks data in ${tasksPath}`);
}
refactor(expand/all): Implement additive expansion and complexity report integration Refactors the `expandTask` and `expandAllTasks` features to complete subtask 61.38 and enhance functionality based on subtask 61.37's refactor. Key Changes: - **Additive Expansion (`expandTask`, `expandAllTasks`):** - Modified `expandTask` default behavior to append newly generated subtasks to any existing ones. - Added a `force` flag (passed down from CLI/MCP via `--force` option/parameter) to `expandTask` and `expandAllTasks`. When `force` is true, existing subtasks are cleared before generating new ones. - Updated relevant CLI command (`expand`), MCP tool (`expand_task`, `expand_all`), and direct function wrappers (`expandTaskDirect`, `expandAllTasksDirect`) to handle and pass the `force` flag. - **Complexity Report Integration (`expandTask`):** - `expandTask` now reads `scripts/task-complexity-report.json`. - If an analysis entry exists for the target task: - `recommendedSubtasks` is used to determine the number of subtasks to generate (unless `--num` is explicitly provided). - `expansionPrompt` is used as the primary prompt content for the AI. - `reasoning` is appended to any additional context provided. - If no report entry exists or the report is missing, it falls back to default subtask count (from config) and standard prompt generation. - **`expandAllTasks` Orchestration:** - Refactored `expandAllTasks` to primarily iterate through eligible tasks (pending/in-progress, considering `force` flag and existing subtasks) and call the updated `expandTask` function for each. - Removed redundant logic (like complexity reading or explicit subtask clearing) now handled within `expandTask`. - Ensures correct context (`session`, `mcpLog`) and flags (`useResearch`, `force`) are passed down. - **Configuration & Cleanup:** - Updated `.cursor/mcp.json` with new Perplexity/Anthropic API keys (old ones invalidated). - Completed refactoring of `expandTask` started in 61.37, confirming usage of `generateTextService` and appropriate prompts. - **Task Management:** - Marked subtask 61.37 as complete. - Updated `.changeset/cuddly-zebras-matter.md` to reflect user-facing changes. These changes finalize the refactoring of the task expansion features, making them more robust, configurable via complexity analysis, and aligned with the unified AI service architecture.
2025-04-25 02:57:08 -04:00
// --- Restore Original Filtering Logic ---
const tasksToExpand = data.tasks.filter(
(task) =>
(task.status === 'pending' || task.status === 'in-progress') && // Include 'in-progress'
(!task.subtasks || task.subtasks.length === 0 || force) // Check subtasks/force here
);
refactor(expand/all): Implement additive expansion and complexity report integration Refactors the `expandTask` and `expandAllTasks` features to complete subtask 61.38 and enhance functionality based on subtask 61.37's refactor. Key Changes: - **Additive Expansion (`expandTask`, `expandAllTasks`):** - Modified `expandTask` default behavior to append newly generated subtasks to any existing ones. - Added a `force` flag (passed down from CLI/MCP via `--force` option/parameter) to `expandTask` and `expandAllTasks`. When `force` is true, existing subtasks are cleared before generating new ones. - Updated relevant CLI command (`expand`), MCP tool (`expand_task`, `expand_all`), and direct function wrappers (`expandTaskDirect`, `expandAllTasksDirect`) to handle and pass the `force` flag. - **Complexity Report Integration (`expandTask`):** - `expandTask` now reads `scripts/task-complexity-report.json`. - If an analysis entry exists for the target task: - `recommendedSubtasks` is used to determine the number of subtasks to generate (unless `--num` is explicitly provided). - `expansionPrompt` is used as the primary prompt content for the AI. - `reasoning` is appended to any additional context provided. - If no report entry exists or the report is missing, it falls back to default subtask count (from config) and standard prompt generation. - **`expandAllTasks` Orchestration:** - Refactored `expandAllTasks` to primarily iterate through eligible tasks (pending/in-progress, considering `force` flag and existing subtasks) and call the updated `expandTask` function for each. - Removed redundant logic (like complexity reading or explicit subtask clearing) now handled within `expandTask`. - Ensures correct context (`session`, `mcpLog`) and flags (`useResearch`, `force`) are passed down. - **Configuration & Cleanup:** - Updated `.cursor/mcp.json` with new Perplexity/Anthropic API keys (old ones invalidated). - Completed refactoring of `expandTask` started in 61.37, confirming usage of `generateTextService` and appropriate prompts. - **Task Management:** - Marked subtask 61.37 as complete. - Updated `.changeset/cuddly-zebras-matter.md` to reflect user-facing changes. These changes finalize the refactoring of the task expansion features, making them more robust, configurable via complexity analysis, and aligned with the unified AI service architecture.
2025-04-25 02:57:08 -04:00
tasksToExpandCount = tasksToExpand.length; // Get the count from the filtered array
logger.info(`Found ${tasksToExpandCount} tasks eligible for expansion.`);
// --- End Restored Filtering Logic ---
refactor(expand/all): Implement additive expansion and complexity report integration Refactors the `expandTask` and `expandAllTasks` features to complete subtask 61.38 and enhance functionality based on subtask 61.37's refactor. Key Changes: - **Additive Expansion (`expandTask`, `expandAllTasks`):** - Modified `expandTask` default behavior to append newly generated subtasks to any existing ones. - Added a `force` flag (passed down from CLI/MCP via `--force` option/parameter) to `expandTask` and `expandAllTasks`. When `force` is true, existing subtasks are cleared before generating new ones. - Updated relevant CLI command (`expand`), MCP tool (`expand_task`, `expand_all`), and direct function wrappers (`expandTaskDirect`, `expandAllTasksDirect`) to handle and pass the `force` flag. - **Complexity Report Integration (`expandTask`):** - `expandTask` now reads `scripts/task-complexity-report.json`. - If an analysis entry exists for the target task: - `recommendedSubtasks` is used to determine the number of subtasks to generate (unless `--num` is explicitly provided). - `expansionPrompt` is used as the primary prompt content for the AI. - `reasoning` is appended to any additional context provided. - If no report entry exists or the report is missing, it falls back to default subtask count (from config) and standard prompt generation. - **`expandAllTasks` Orchestration:** - Refactored `expandAllTasks` to primarily iterate through eligible tasks (pending/in-progress, considering `force` flag and existing subtasks) and call the updated `expandTask` function for each. - Removed redundant logic (like complexity reading or explicit subtask clearing) now handled within `expandTask`. - Ensures correct context (`session`, `mcpLog`) and flags (`useResearch`, `force`) are passed down. - **Configuration & Cleanup:** - Updated `.cursor/mcp.json` with new Perplexity/Anthropic API keys (old ones invalidated). - Completed refactoring of `expandTask` started in 61.37, confirming usage of `generateTextService` and appropriate prompts. - **Task Management:** - Marked subtask 61.37 as complete. - Updated `.changeset/cuddly-zebras-matter.md` to reflect user-facing changes. These changes finalize the refactoring of the task expansion features, making them more robust, configurable via complexity analysis, and aligned with the unified AI service architecture.
2025-04-25 02:57:08 -04:00
if (loadingIndicator) {
stopLoadingIndicator(loadingIndicator, 'Analysis complete.');
}
refactor(expand/all): Implement additive expansion and complexity report integration Refactors the `expandTask` and `expandAllTasks` features to complete subtask 61.38 and enhance functionality based on subtask 61.37's refactor. Key Changes: - **Additive Expansion (`expandTask`, `expandAllTasks`):** - Modified `expandTask` default behavior to append newly generated subtasks to any existing ones. - Added a `force` flag (passed down from CLI/MCP via `--force` option/parameter) to `expandTask` and `expandAllTasks`. When `force` is true, existing subtasks are cleared before generating new ones. - Updated relevant CLI command (`expand`), MCP tool (`expand_task`, `expand_all`), and direct function wrappers (`expandTaskDirect`, `expandAllTasksDirect`) to handle and pass the `force` flag. - **Complexity Report Integration (`expandTask`):** - `expandTask` now reads `scripts/task-complexity-report.json`. - If an analysis entry exists for the target task: - `recommendedSubtasks` is used to determine the number of subtasks to generate (unless `--num` is explicitly provided). - `expansionPrompt` is used as the primary prompt content for the AI. - `reasoning` is appended to any additional context provided. - If no report entry exists or the report is missing, it falls back to default subtask count (from config) and standard prompt generation. - **`expandAllTasks` Orchestration:** - Refactored `expandAllTasks` to primarily iterate through eligible tasks (pending/in-progress, considering `force` flag and existing subtasks) and call the updated `expandTask` function for each. - Removed redundant logic (like complexity reading or explicit subtask clearing) now handled within `expandTask`. - Ensures correct context (`session`, `mcpLog`) and flags (`useResearch`, `force`) are passed down. - **Configuration & Cleanup:** - Updated `.cursor/mcp.json` with new Perplexity/Anthropic API keys (old ones invalidated). - Completed refactoring of `expandTask` started in 61.37, confirming usage of `generateTextService` and appropriate prompts. - **Task Management:** - Marked subtask 61.37 as complete. - Updated `.changeset/cuddly-zebras-matter.md` to reflect user-facing changes. These changes finalize the refactoring of the task expansion features, making them more robust, configurable via complexity analysis, and aligned with the unified AI service architecture.
2025-04-25 02:57:08 -04:00
if (tasksToExpandCount === 0) {
logger.info('No tasks eligible for expansion.');
// --- Fix: Restore success: true and add message ---
return {
success: true, // Indicate overall success despite no action
expandedCount: 0,
failedCount: 0,
skippedCount: 0,
tasksToExpand: 0,
feat(telemetry): Integrate telemetry for expand-all, aggregate results This commit implements AI usage telemetry for the `expand-all-tasks` command/tool and refactors its CLI output for clarity and consistency. Key Changes: 1. **Telemetry Integration for `expand-all-tasks` (Subtask 77.8):**\n - The `expandAllTasks` core logic (`scripts/modules/task-manager/expand-all-tasks.js`) now calls the `expandTask` function for each eligible task and collects the individual `telemetryData` returned.\n - A new helper function `_aggregateTelemetry` (in `utils.js`) is used to sum up token counts and costs from all individual expansions into a single `telemetryData` object for the entire `expand-all` operation.\n - The `expandAllTasksDirect` wrapper (`mcp-server/src/core/direct-functions/expand-all-tasks.js`) now receives and passes this aggregated `telemetryData` in the MCP response.\n - For CLI usage, `displayAiUsageSummary` is called once with the aggregated telemetry. 2. **Improved CLI Output for `expand-all`:**\n - The `expandAllTasks` core function now handles displaying a final "Expansion Summary" box (showing Attempted, Expanded, Skipped, Failed counts) directly after the aggregated telemetry summary.\n - This consolidates all summary output within the core function for better flow and removes redundant logging from the command action in `scripts/modules/commands.js`.\n - The summary box border is green for success and red if any expansions failed. 3. **Code Refinements:**\n - Ensured `chalk` and `boxen` are imported in `expand-all-tasks.js` for the new summary box.\n - Minor adjustments to logging messages for clarity.
2025-05-08 18:22:00 -04:00
telemetryData: allTelemetryData,
refactor(expand/all): Implement additive expansion and complexity report integration Refactors the `expandTask` and `expandAllTasks` features to complete subtask 61.38 and enhance functionality based on subtask 61.37's refactor. Key Changes: - **Additive Expansion (`expandTask`, `expandAllTasks`):** - Modified `expandTask` default behavior to append newly generated subtasks to any existing ones. - Added a `force` flag (passed down from CLI/MCP via `--force` option/parameter) to `expandTask` and `expandAllTasks`. When `force` is true, existing subtasks are cleared before generating new ones. - Updated relevant CLI command (`expand`), MCP tool (`expand_task`, `expand_all`), and direct function wrappers (`expandTaskDirect`, `expandAllTasksDirect`) to handle and pass the `force` flag. - **Complexity Report Integration (`expandTask`):** - `expandTask` now reads `scripts/task-complexity-report.json`. - If an analysis entry exists for the target task: - `recommendedSubtasks` is used to determine the number of subtasks to generate (unless `--num` is explicitly provided). - `expansionPrompt` is used as the primary prompt content for the AI. - `reasoning` is appended to any additional context provided. - If no report entry exists or the report is missing, it falls back to default subtask count (from config) and standard prompt generation. - **`expandAllTasks` Orchestration:** - Refactored `expandAllTasks` to primarily iterate through eligible tasks (pending/in-progress, considering `force` flag and existing subtasks) and call the updated `expandTask` function for each. - Removed redundant logic (like complexity reading or explicit subtask clearing) now handled within `expandTask`. - Ensures correct context (`session`, `mcpLog`) and flags (`useResearch`, `force`) are passed down. - **Configuration & Cleanup:** - Updated `.cursor/mcp.json` with new Perplexity/Anthropic API keys (old ones invalidated). - Completed refactoring of `expandTask` started in 61.37, confirming usage of `generateTextService` and appropriate prompts. - **Task Management:** - Marked subtask 61.37 as complete. - Updated `.changeset/cuddly-zebras-matter.md` to reflect user-facing changes. These changes finalize the refactoring of the task expansion features, making them more robust, configurable via complexity analysis, and aligned with the unified AI service architecture.
2025-04-25 02:57:08 -04:00
message: 'No tasks eligible for expansion.'
};
// --- End Fix ---
}
refactor(expand/all): Implement additive expansion and complexity report integration Refactors the `expandTask` and `expandAllTasks` features to complete subtask 61.38 and enhance functionality based on subtask 61.37's refactor. Key Changes: - **Additive Expansion (`expandTask`, `expandAllTasks`):** - Modified `expandTask` default behavior to append newly generated subtasks to any existing ones. - Added a `force` flag (passed down from CLI/MCP via `--force` option/parameter) to `expandTask` and `expandAllTasks`. When `force` is true, existing subtasks are cleared before generating new ones. - Updated relevant CLI command (`expand`), MCP tool (`expand_task`, `expand_all`), and direct function wrappers (`expandTaskDirect`, `expandAllTasksDirect`) to handle and pass the `force` flag. - **Complexity Report Integration (`expandTask`):** - `expandTask` now reads `scripts/task-complexity-report.json`. - If an analysis entry exists for the target task: - `recommendedSubtasks` is used to determine the number of subtasks to generate (unless `--num` is explicitly provided). - `expansionPrompt` is used as the primary prompt content for the AI. - `reasoning` is appended to any additional context provided. - If no report entry exists or the report is missing, it falls back to default subtask count (from config) and standard prompt generation. - **`expandAllTasks` Orchestration:** - Refactored `expandAllTasks` to primarily iterate through eligible tasks (pending/in-progress, considering `force` flag and existing subtasks) and call the updated `expandTask` function for each. - Removed redundant logic (like complexity reading or explicit subtask clearing) now handled within `expandTask`. - Ensures correct context (`session`, `mcpLog`) and flags (`useResearch`, `force`) are passed down. - **Configuration & Cleanup:** - Updated `.cursor/mcp.json` with new Perplexity/Anthropic API keys (old ones invalidated). - Completed refactoring of `expandTask` started in 61.37, confirming usage of `generateTextService` and appropriate prompts. - **Task Management:** - Marked subtask 61.37 as complete. - Updated `.changeset/cuddly-zebras-matter.md` to reflect user-facing changes. These changes finalize the refactoring of the task expansion features, making them more robust, configurable via complexity analysis, and aligned with the unified AI service architecture.
2025-04-25 02:57:08 -04:00
// Iterate over the already filtered tasks
for (const task of tasksToExpand) {
refactor(expand/all): Implement additive expansion and complexity report integration Refactors the `expandTask` and `expandAllTasks` features to complete subtask 61.38 and enhance functionality based on subtask 61.37's refactor. Key Changes: - **Additive Expansion (`expandTask`, `expandAllTasks`):** - Modified `expandTask` default behavior to append newly generated subtasks to any existing ones. - Added a `force` flag (passed down from CLI/MCP via `--force` option/parameter) to `expandTask` and `expandAllTasks`. When `force` is true, existing subtasks are cleared before generating new ones. - Updated relevant CLI command (`expand`), MCP tool (`expand_task`, `expand_all`), and direct function wrappers (`expandTaskDirect`, `expandAllTasksDirect`) to handle and pass the `force` flag. - **Complexity Report Integration (`expandTask`):** - `expandTask` now reads `scripts/task-complexity-report.json`. - If an analysis entry exists for the target task: - `recommendedSubtasks` is used to determine the number of subtasks to generate (unless `--num` is explicitly provided). - `expansionPrompt` is used as the primary prompt content for the AI. - `reasoning` is appended to any additional context provided. - If no report entry exists or the report is missing, it falls back to default subtask count (from config) and standard prompt generation. - **`expandAllTasks` Orchestration:** - Refactored `expandAllTasks` to primarily iterate through eligible tasks (pending/in-progress, considering `force` flag and existing subtasks) and call the updated `expandTask` function for each. - Removed redundant logic (like complexity reading or explicit subtask clearing) now handled within `expandTask`. - Ensures correct context (`session`, `mcpLog`) and flags (`useResearch`, `force`) are passed down. - **Configuration & Cleanup:** - Updated `.cursor/mcp.json` with new Perplexity/Anthropic API keys (old ones invalidated). - Completed refactoring of `expandTask` started in 61.37, confirming usage of `generateTextService` and appropriate prompts. - **Task Management:** - Marked subtask 61.37 as complete. - Updated `.changeset/cuddly-zebras-matter.md` to reflect user-facing changes. These changes finalize the refactoring of the task expansion features, making them more robust, configurable via complexity analysis, and aligned with the unified AI service architecture.
2025-04-25 02:57:08 -04:00
// Start indicator for individual task expansion in CLI mode
let taskIndicator = null;
if (!isMCPCall && outputFormat === 'text') {
taskIndicator = startLoadingIndicator(`Expanding task ${task.id}...`);
}
try {
feat(telemetry): Integrate telemetry for expand-all, aggregate results This commit implements AI usage telemetry for the `expand-all-tasks` command/tool and refactors its CLI output for clarity and consistency. Key Changes: 1. **Telemetry Integration for `expand-all-tasks` (Subtask 77.8):**\n - The `expandAllTasks` core logic (`scripts/modules/task-manager/expand-all-tasks.js`) now calls the `expandTask` function for each eligible task and collects the individual `telemetryData` returned.\n - A new helper function `_aggregateTelemetry` (in `utils.js`) is used to sum up token counts and costs from all individual expansions into a single `telemetryData` object for the entire `expand-all` operation.\n - The `expandAllTasksDirect` wrapper (`mcp-server/src/core/direct-functions/expand-all-tasks.js`) now receives and passes this aggregated `telemetryData` in the MCP response.\n - For CLI usage, `displayAiUsageSummary` is called once with the aggregated telemetry. 2. **Improved CLI Output for `expand-all`:**\n - The `expandAllTasks` core function now handles displaying a final "Expansion Summary" box (showing Attempted, Expanded, Skipped, Failed counts) directly after the aggregated telemetry summary.\n - This consolidates all summary output within the core function for better flow and removes redundant logging from the command action in `scripts/modules/commands.js`.\n - The summary box border is green for success and red if any expansions failed. 3. **Code Refinements:**\n - Ensured `chalk` and `boxen` are imported in `expand-all-tasks.js` for the new summary box.\n - Minor adjustments to logging messages for clarity.
2025-05-08 18:22:00 -04:00
// Call the refactored expandTask function AND capture result
const result = await expandTask(
refactor(expand/all): Implement additive expansion and complexity report integration Refactors the `expandTask` and `expandAllTasks` features to complete subtask 61.38 and enhance functionality based on subtask 61.37's refactor. Key Changes: - **Additive Expansion (`expandTask`, `expandAllTasks`):** - Modified `expandTask` default behavior to append newly generated subtasks to any existing ones. - Added a `force` flag (passed down from CLI/MCP via `--force` option/parameter) to `expandTask` and `expandAllTasks`. When `force` is true, existing subtasks are cleared before generating new ones. - Updated relevant CLI command (`expand`), MCP tool (`expand_task`, `expand_all`), and direct function wrappers (`expandTaskDirect`, `expandAllTasksDirect`) to handle and pass the `force` flag. - **Complexity Report Integration (`expandTask`):** - `expandTask` now reads `scripts/task-complexity-report.json`. - If an analysis entry exists for the target task: - `recommendedSubtasks` is used to determine the number of subtasks to generate (unless `--num` is explicitly provided). - `expansionPrompt` is used as the primary prompt content for the AI. - `reasoning` is appended to any additional context provided. - If no report entry exists or the report is missing, it falls back to default subtask count (from config) and standard prompt generation. - **`expandAllTasks` Orchestration:** - Refactored `expandAllTasks` to primarily iterate through eligible tasks (pending/in-progress, considering `force` flag and existing subtasks) and call the updated `expandTask` function for each. - Removed redundant logic (like complexity reading or explicit subtask clearing) now handled within `expandTask`. - Ensures correct context (`session`, `mcpLog`) and flags (`useResearch`, `force`) are passed down. - **Configuration & Cleanup:** - Updated `.cursor/mcp.json` with new Perplexity/Anthropic API keys (old ones invalidated). - Completed refactoring of `expandTask` started in 61.37, confirming usage of `generateTextService` and appropriate prompts. - **Task Management:** - Marked subtask 61.37 as complete. - Updated `.changeset/cuddly-zebras-matter.md` to reflect user-facing changes. These changes finalize the refactoring of the task expansion features, making them more robust, configurable via complexity analysis, and aligned with the unified AI service architecture.
2025-04-25 02:57:08 -04:00
tasksPath,
task.id,
feat(telemetry): Integrate telemetry for expand-all, aggregate results This commit implements AI usage telemetry for the `expand-all-tasks` command/tool and refactors its CLI output for clarity and consistency. Key Changes: 1. **Telemetry Integration for `expand-all-tasks` (Subtask 77.8):**\n - The `expandAllTasks` core logic (`scripts/modules/task-manager/expand-all-tasks.js`) now calls the `expandTask` function for each eligible task and collects the individual `telemetryData` returned.\n - A new helper function `_aggregateTelemetry` (in `utils.js`) is used to sum up token counts and costs from all individual expansions into a single `telemetryData` object for the entire `expand-all` operation.\n - The `expandAllTasksDirect` wrapper (`mcp-server/src/core/direct-functions/expand-all-tasks.js`) now receives and passes this aggregated `telemetryData` in the MCP response.\n - For CLI usage, `displayAiUsageSummary` is called once with the aggregated telemetry. 2. **Improved CLI Output for `expand-all`:**\n - The `expandAllTasks` core function now handles displaying a final "Expansion Summary" box (showing Attempted, Expanded, Skipped, Failed counts) directly after the aggregated telemetry summary.\n - This consolidates all summary output within the core function for better flow and removes redundant logging from the command action in `scripts/modules/commands.js`.\n - The summary box border is green for success and red if any expansions failed. 3. **Code Refinements:**\n - Ensured `chalk` and `boxen` are imported in `expand-all-tasks.js` for the new summary box.\n - Minor adjustments to logging messages for clarity.
2025-05-08 18:22:00 -04:00
numSubtasks,
useResearch,
refactor(expand/all): Implement additive expansion and complexity report integration Refactors the `expandTask` and `expandAllTasks` features to complete subtask 61.38 and enhance functionality based on subtask 61.37's refactor. Key Changes: - **Additive Expansion (`expandTask`, `expandAllTasks`):** - Modified `expandTask` default behavior to append newly generated subtasks to any existing ones. - Added a `force` flag (passed down from CLI/MCP via `--force` option/parameter) to `expandTask` and `expandAllTasks`. When `force` is true, existing subtasks are cleared before generating new ones. - Updated relevant CLI command (`expand`), MCP tool (`expand_task`, `expand_all`), and direct function wrappers (`expandTaskDirect`, `expandAllTasksDirect`) to handle and pass the `force` flag. - **Complexity Report Integration (`expandTask`):** - `expandTask` now reads `scripts/task-complexity-report.json`. - If an analysis entry exists for the target task: - `recommendedSubtasks` is used to determine the number of subtasks to generate (unless `--num` is explicitly provided). - `expansionPrompt` is used as the primary prompt content for the AI. - `reasoning` is appended to any additional context provided. - If no report entry exists or the report is missing, it falls back to default subtask count (from config) and standard prompt generation. - **`expandAllTasks` Orchestration:** - Refactored `expandAllTasks` to primarily iterate through eligible tasks (pending/in-progress, considering `force` flag and existing subtasks) and call the updated `expandTask` function for each. - Removed redundant logic (like complexity reading or explicit subtask clearing) now handled within `expandTask`. - Ensures correct context (`session`, `mcpLog`) and flags (`useResearch`, `force`) are passed down. - **Configuration & Cleanup:** - Updated `.cursor/mcp.json` with new Perplexity/Anthropic API keys (old ones invalidated). - Completed refactoring of `expandTask` started in 61.37, confirming usage of `generateTextService` and appropriate prompts. - **Task Management:** - Marked subtask 61.37 as complete. - Updated `.changeset/cuddly-zebras-matter.md` to reflect user-facing changes. These changes finalize the refactoring of the task expansion features, making them more robust, configurable via complexity analysis, and aligned with the unified AI service architecture.
2025-04-25 02:57:08 -04:00
additionalContext,
context, // Pass the whole context object { session, mcpLog }
feat(telemetry): Integrate telemetry for expand-all, aggregate results This commit implements AI usage telemetry for the `expand-all-tasks` command/tool and refactors its CLI output for clarity and consistency. Key Changes: 1. **Telemetry Integration for `expand-all-tasks` (Subtask 77.8):**\n - The `expandAllTasks` core logic (`scripts/modules/task-manager/expand-all-tasks.js`) now calls the `expandTask` function for each eligible task and collects the individual `telemetryData` returned.\n - A new helper function `_aggregateTelemetry` (in `utils.js`) is used to sum up token counts and costs from all individual expansions into a single `telemetryData` object for the entire `expand-all` operation.\n - The `expandAllTasksDirect` wrapper (`mcp-server/src/core/direct-functions/expand-all-tasks.js`) now receives and passes this aggregated `telemetryData` in the MCP response.\n - For CLI usage, `displayAiUsageSummary` is called once with the aggregated telemetry. 2. **Improved CLI Output for `expand-all`:**\n - The `expandAllTasks` core function now handles displaying a final "Expansion Summary" box (showing Attempted, Expanded, Skipped, Failed counts) directly after the aggregated telemetry summary.\n - This consolidates all summary output within the core function for better flow and removes redundant logging from the command action in `scripts/modules/commands.js`.\n - The summary box border is green for success and red if any expansions failed. 3. **Code Refinements:**\n - Ensured `chalk` and `boxen` are imported in `expand-all-tasks.js` for the new summary box.\n - Minor adjustments to logging messages for clarity.
2025-05-08 18:22:00 -04:00
force
);
refactor(expand/all): Implement additive expansion and complexity report integration Refactors the `expandTask` and `expandAllTasks` features to complete subtask 61.38 and enhance functionality based on subtask 61.37's refactor. Key Changes: - **Additive Expansion (`expandTask`, `expandAllTasks`):** - Modified `expandTask` default behavior to append newly generated subtasks to any existing ones. - Added a `force` flag (passed down from CLI/MCP via `--force` option/parameter) to `expandTask` and `expandAllTasks`. When `force` is true, existing subtasks are cleared before generating new ones. - Updated relevant CLI command (`expand`), MCP tool (`expand_task`, `expand_all`), and direct function wrappers (`expandTaskDirect`, `expandAllTasksDirect`) to handle and pass the `force` flag. - **Complexity Report Integration (`expandTask`):** - `expandTask` now reads `scripts/task-complexity-report.json`. - If an analysis entry exists for the target task: - `recommendedSubtasks` is used to determine the number of subtasks to generate (unless `--num` is explicitly provided). - `expansionPrompt` is used as the primary prompt content for the AI. - `reasoning` is appended to any additional context provided. - If no report entry exists or the report is missing, it falls back to default subtask count (from config) and standard prompt generation. - **`expandAllTasks` Orchestration:** - Refactored `expandAllTasks` to primarily iterate through eligible tasks (pending/in-progress, considering `force` flag and existing subtasks) and call the updated `expandTask` function for each. - Removed redundant logic (like complexity reading or explicit subtask clearing) now handled within `expandTask`. - Ensures correct context (`session`, `mcpLog`) and flags (`useResearch`, `force`) are passed down. - **Configuration & Cleanup:** - Updated `.cursor/mcp.json` with new Perplexity/Anthropic API keys (old ones invalidated). - Completed refactoring of `expandTask` started in 61.37, confirming usage of `generateTextService` and appropriate prompts. - **Task Management:** - Marked subtask 61.37 as complete. - Updated `.changeset/cuddly-zebras-matter.md` to reflect user-facing changes. These changes finalize the refactoring of the task expansion features, making them more robust, configurable via complexity analysis, and aligned with the unified AI service architecture.
2025-04-25 02:57:08 -04:00
expandedCount++;
feat(telemetry): Integrate telemetry for expand-all, aggregate results This commit implements AI usage telemetry for the `expand-all-tasks` command/tool and refactors its CLI output for clarity and consistency. Key Changes: 1. **Telemetry Integration for `expand-all-tasks` (Subtask 77.8):**\n - The `expandAllTasks` core logic (`scripts/modules/task-manager/expand-all-tasks.js`) now calls the `expandTask` function for each eligible task and collects the individual `telemetryData` returned.\n - A new helper function `_aggregateTelemetry` (in `utils.js`) is used to sum up token counts and costs from all individual expansions into a single `telemetryData` object for the entire `expand-all` operation.\n - The `expandAllTasksDirect` wrapper (`mcp-server/src/core/direct-functions/expand-all-tasks.js`) now receives and passes this aggregated `telemetryData` in the MCP response.\n - For CLI usage, `displayAiUsageSummary` is called once with the aggregated telemetry. 2. **Improved CLI Output for `expand-all`:**\n - The `expandAllTasks` core function now handles displaying a final "Expansion Summary" box (showing Attempted, Expanded, Skipped, Failed counts) directly after the aggregated telemetry summary.\n - This consolidates all summary output within the core function for better flow and removes redundant logging from the command action in `scripts/modules/commands.js`.\n - The summary box border is green for success and red if any expansions failed. 3. **Code Refinements:**\n - Ensured `chalk` and `boxen` are imported in `expand-all-tasks.js` for the new summary box.\n - Minor adjustments to logging messages for clarity.
2025-05-08 18:22:00 -04:00
// Collect individual telemetry data
if (result && result.telemetryData) {
allTelemetryData.push(result.telemetryData);
}
refactor(expand/all): Implement additive expansion and complexity report integration Refactors the `expandTask` and `expandAllTasks` features to complete subtask 61.38 and enhance functionality based on subtask 61.37's refactor. Key Changes: - **Additive Expansion (`expandTask`, `expandAllTasks`):** - Modified `expandTask` default behavior to append newly generated subtasks to any existing ones. - Added a `force` flag (passed down from CLI/MCP via `--force` option/parameter) to `expandTask` and `expandAllTasks`. When `force` is true, existing subtasks are cleared before generating new ones. - Updated relevant CLI command (`expand`), MCP tool (`expand_task`, `expand_all`), and direct function wrappers (`expandTaskDirect`, `expandAllTasksDirect`) to handle and pass the `force` flag. - **Complexity Report Integration (`expandTask`):** - `expandTask` now reads `scripts/task-complexity-report.json`. - If an analysis entry exists for the target task: - `recommendedSubtasks` is used to determine the number of subtasks to generate (unless `--num` is explicitly provided). - `expansionPrompt` is used as the primary prompt content for the AI. - `reasoning` is appended to any additional context provided. - If no report entry exists or the report is missing, it falls back to default subtask count (from config) and standard prompt generation. - **`expandAllTasks` Orchestration:** - Refactored `expandAllTasks` to primarily iterate through eligible tasks (pending/in-progress, considering `force` flag and existing subtasks) and call the updated `expandTask` function for each. - Removed redundant logic (like complexity reading or explicit subtask clearing) now handled within `expandTask`. - Ensures correct context (`session`, `mcpLog`) and flags (`useResearch`, `force`) are passed down. - **Configuration & Cleanup:** - Updated `.cursor/mcp.json` with new Perplexity/Anthropic API keys (old ones invalidated). - Completed refactoring of `expandTask` started in 61.37, confirming usage of `generateTextService` and appropriate prompts. - **Task Management:** - Marked subtask 61.37 as complete. - Updated `.changeset/cuddly-zebras-matter.md` to reflect user-facing changes. These changes finalize the refactoring of the task expansion features, making them more robust, configurable via complexity analysis, and aligned with the unified AI service architecture.
2025-04-25 02:57:08 -04:00
if (taskIndicator) {
stopLoadingIndicator(taskIndicator, `Task ${task.id} expanded.`);
}
refactor(expand/all): Implement additive expansion and complexity report integration Refactors the `expandTask` and `expandAllTasks` features to complete subtask 61.38 and enhance functionality based on subtask 61.37's refactor. Key Changes: - **Additive Expansion (`expandTask`, `expandAllTasks`):** - Modified `expandTask` default behavior to append newly generated subtasks to any existing ones. - Added a `force` flag (passed down from CLI/MCP via `--force` option/parameter) to `expandTask` and `expandAllTasks`. When `force` is true, existing subtasks are cleared before generating new ones. - Updated relevant CLI command (`expand`), MCP tool (`expand_task`, `expand_all`), and direct function wrappers (`expandTaskDirect`, `expandAllTasksDirect`) to handle and pass the `force` flag. - **Complexity Report Integration (`expandTask`):** - `expandTask` now reads `scripts/task-complexity-report.json`. - If an analysis entry exists for the target task: - `recommendedSubtasks` is used to determine the number of subtasks to generate (unless `--num` is explicitly provided). - `expansionPrompt` is used as the primary prompt content for the AI. - `reasoning` is appended to any additional context provided. - If no report entry exists or the report is missing, it falls back to default subtask count (from config) and standard prompt generation. - **`expandAllTasks` Orchestration:** - Refactored `expandAllTasks` to primarily iterate through eligible tasks (pending/in-progress, considering `force` flag and existing subtasks) and call the updated `expandTask` function for each. - Removed redundant logic (like complexity reading or explicit subtask clearing) now handled within `expandTask`. - Ensures correct context (`session`, `mcpLog`) and flags (`useResearch`, `force`) are passed down. - **Configuration & Cleanup:** - Updated `.cursor/mcp.json` with new Perplexity/Anthropic API keys (old ones invalidated). - Completed refactoring of `expandTask` started in 61.37, confirming usage of `generateTextService` and appropriate prompts. - **Task Management:** - Marked subtask 61.37 as complete. - Updated `.changeset/cuddly-zebras-matter.md` to reflect user-facing changes. These changes finalize the refactoring of the task expansion features, making them more robust, configurable via complexity analysis, and aligned with the unified AI service architecture.
2025-04-25 02:57:08 -04:00
logger.info(`Successfully expanded task ${task.id}.`);
} catch (error) {
refactor(expand/all): Implement additive expansion and complexity report integration Refactors the `expandTask` and `expandAllTasks` features to complete subtask 61.38 and enhance functionality based on subtask 61.37's refactor. Key Changes: - **Additive Expansion (`expandTask`, `expandAllTasks`):** - Modified `expandTask` default behavior to append newly generated subtasks to any existing ones. - Added a `force` flag (passed down from CLI/MCP via `--force` option/parameter) to `expandTask` and `expandAllTasks`. When `force` is true, existing subtasks are cleared before generating new ones. - Updated relevant CLI command (`expand`), MCP tool (`expand_task`, `expand_all`), and direct function wrappers (`expandTaskDirect`, `expandAllTasksDirect`) to handle and pass the `force` flag. - **Complexity Report Integration (`expandTask`):** - `expandTask` now reads `scripts/task-complexity-report.json`. - If an analysis entry exists for the target task: - `recommendedSubtasks` is used to determine the number of subtasks to generate (unless `--num` is explicitly provided). - `expansionPrompt` is used as the primary prompt content for the AI. - `reasoning` is appended to any additional context provided. - If no report entry exists or the report is missing, it falls back to default subtask count (from config) and standard prompt generation. - **`expandAllTasks` Orchestration:** - Refactored `expandAllTasks` to primarily iterate through eligible tasks (pending/in-progress, considering `force` flag and existing subtasks) and call the updated `expandTask` function for each. - Removed redundant logic (like complexity reading or explicit subtask clearing) now handled within `expandTask`. - Ensures correct context (`session`, `mcpLog`) and flags (`useResearch`, `force`) are passed down. - **Configuration & Cleanup:** - Updated `.cursor/mcp.json` with new Perplexity/Anthropic API keys (old ones invalidated). - Completed refactoring of `expandTask` started in 61.37, confirming usage of `generateTextService` and appropriate prompts. - **Task Management:** - Marked subtask 61.37 as complete. - Updated `.changeset/cuddly-zebras-matter.md` to reflect user-facing changes. These changes finalize the refactoring of the task expansion features, making them more robust, configurable via complexity analysis, and aligned with the unified AI service architecture.
2025-04-25 02:57:08 -04:00
failedCount++;
if (taskIndicator) {
stopLoadingIndicator(
taskIndicator,
`Failed to expand task ${task.id}.`,
false
);
}
logger.error(`Failed to expand task ${task.id}: ${error.message}`);
// Continue to the next task
}
}
feat(telemetry): Integrate telemetry for expand-all, aggregate results This commit implements AI usage telemetry for the `expand-all-tasks` command/tool and refactors its CLI output for clarity and consistency. Key Changes: 1. **Telemetry Integration for `expand-all-tasks` (Subtask 77.8):**\n - The `expandAllTasks` core logic (`scripts/modules/task-manager/expand-all-tasks.js`) now calls the `expandTask` function for each eligible task and collects the individual `telemetryData` returned.\n - A new helper function `_aggregateTelemetry` (in `utils.js`) is used to sum up token counts and costs from all individual expansions into a single `telemetryData` object for the entire `expand-all` operation.\n - The `expandAllTasksDirect` wrapper (`mcp-server/src/core/direct-functions/expand-all-tasks.js`) now receives and passes this aggregated `telemetryData` in the MCP response.\n - For CLI usage, `displayAiUsageSummary` is called once with the aggregated telemetry. 2. **Improved CLI Output for `expand-all`:**\n - The `expandAllTasks` core function now handles displaying a final "Expansion Summary" box (showing Attempted, Expanded, Skipped, Failed counts) directly after the aggregated telemetry summary.\n - This consolidates all summary output within the core function for better flow and removes redundant logging from the command action in `scripts/modules/commands.js`.\n - The summary box border is green for success and red if any expansions failed. 3. **Code Refinements:**\n - Ensured `chalk` and `boxen` are imported in `expand-all-tasks.js` for the new summary box.\n - Minor adjustments to logging messages for clarity.
2025-05-08 18:22:00 -04:00
// --- AGGREGATION AND DISPLAY ---
refactor(expand/all): Implement additive expansion and complexity report integration Refactors the `expandTask` and `expandAllTasks` features to complete subtask 61.38 and enhance functionality based on subtask 61.37's refactor. Key Changes: - **Additive Expansion (`expandTask`, `expandAllTasks`):** - Modified `expandTask` default behavior to append newly generated subtasks to any existing ones. - Added a `force` flag (passed down from CLI/MCP via `--force` option/parameter) to `expandTask` and `expandAllTasks`. When `force` is true, existing subtasks are cleared before generating new ones. - Updated relevant CLI command (`expand`), MCP tool (`expand_task`, `expand_all`), and direct function wrappers (`expandTaskDirect`, `expandAllTasksDirect`) to handle and pass the `force` flag. - **Complexity Report Integration (`expandTask`):** - `expandTask` now reads `scripts/task-complexity-report.json`. - If an analysis entry exists for the target task: - `recommendedSubtasks` is used to determine the number of subtasks to generate (unless `--num` is explicitly provided). - `expansionPrompt` is used as the primary prompt content for the AI. - `reasoning` is appended to any additional context provided. - If no report entry exists or the report is missing, it falls back to default subtask count (from config) and standard prompt generation. - **`expandAllTasks` Orchestration:** - Refactored `expandAllTasks` to primarily iterate through eligible tasks (pending/in-progress, considering `force` flag and existing subtasks) and call the updated `expandTask` function for each. - Removed redundant logic (like complexity reading or explicit subtask clearing) now handled within `expandTask`. - Ensures correct context (`session`, `mcpLog`) and flags (`useResearch`, `force`) are passed down. - **Configuration & Cleanup:** - Updated `.cursor/mcp.json` with new Perplexity/Anthropic API keys (old ones invalidated). - Completed refactoring of `expandTask` started in 61.37, confirming usage of `generateTextService` and appropriate prompts. - **Task Management:** - Marked subtask 61.37 as complete. - Updated `.changeset/cuddly-zebras-matter.md` to reflect user-facing changes. These changes finalize the refactoring of the task expansion features, making them more robust, configurable via complexity analysis, and aligned with the unified AI service architecture.
2025-04-25 02:57:08 -04:00
logger.info(
`Expansion complete: ${expandedCount} expanded, ${failedCount} failed.`
);
feat(telemetry): Integrate telemetry for expand-all, aggregate results This commit implements AI usage telemetry for the `expand-all-tasks` command/tool and refactors its CLI output for clarity and consistency. Key Changes: 1. **Telemetry Integration for `expand-all-tasks` (Subtask 77.8):**\n - The `expandAllTasks` core logic (`scripts/modules/task-manager/expand-all-tasks.js`) now calls the `expandTask` function for each eligible task and collects the individual `telemetryData` returned.\n - A new helper function `_aggregateTelemetry` (in `utils.js`) is used to sum up token counts and costs from all individual expansions into a single `telemetryData` object for the entire `expand-all` operation.\n - The `expandAllTasksDirect` wrapper (`mcp-server/src/core/direct-functions/expand-all-tasks.js`) now receives and passes this aggregated `telemetryData` in the MCP response.\n - For CLI usage, `displayAiUsageSummary` is called once with the aggregated telemetry. 2. **Improved CLI Output for `expand-all`:**\n - The `expandAllTasks` core function now handles displaying a final "Expansion Summary" box (showing Attempted, Expanded, Skipped, Failed counts) directly after the aggregated telemetry summary.\n - This consolidates all summary output within the core function for better flow and removes redundant logging from the command action in `scripts/modules/commands.js`.\n - The summary box border is green for success and red if any expansions failed. 3. **Code Refinements:**\n - Ensured `chalk` and `boxen` are imported in `expand-all-tasks.js` for the new summary box.\n - Minor adjustments to logging messages for clarity.
2025-05-08 18:22:00 -04:00
// Aggregate the collected telemetry data
const aggregatedTelemetryData = aggregateTelemetry(
feat(telemetry): Integrate telemetry for expand-all, aggregate results This commit implements AI usage telemetry for the `expand-all-tasks` command/tool and refactors its CLI output for clarity and consistency. Key Changes: 1. **Telemetry Integration for `expand-all-tasks` (Subtask 77.8):**\n - The `expandAllTasks` core logic (`scripts/modules/task-manager/expand-all-tasks.js`) now calls the `expandTask` function for each eligible task and collects the individual `telemetryData` returned.\n - A new helper function `_aggregateTelemetry` (in `utils.js`) is used to sum up token counts and costs from all individual expansions into a single `telemetryData` object for the entire `expand-all` operation.\n - The `expandAllTasksDirect` wrapper (`mcp-server/src/core/direct-functions/expand-all-tasks.js`) now receives and passes this aggregated `telemetryData` in the MCP response.\n - For CLI usage, `displayAiUsageSummary` is called once with the aggregated telemetry. 2. **Improved CLI Output for `expand-all`:**\n - The `expandAllTasks` core function now handles displaying a final "Expansion Summary" box (showing Attempted, Expanded, Skipped, Failed counts) directly after the aggregated telemetry summary.\n - This consolidates all summary output within the core function for better flow and removes redundant logging from the command action in `scripts/modules/commands.js`.\n - The summary box border is green for success and red if any expansions failed. 3. **Code Refinements:**\n - Ensured `chalk` and `boxen` are imported in `expand-all-tasks.js` for the new summary box.\n - Minor adjustments to logging messages for clarity.
2025-05-08 18:22:00 -04:00
allTelemetryData,
'expand-all-tasks'
);
if (outputFormat === 'text') {
const summaryContent =
`${chalk.white.bold('Expansion Summary:')}\n\n` +
`${chalk.cyan('-')} Attempted: ${chalk.bold(tasksToExpandCount)}\n` +
`${chalk.green('-')} Expanded: ${chalk.bold(expandedCount)}\n` +
// Skipped count is always 0 now due to pre-filtering
`${chalk.gray('-')} Skipped: ${chalk.bold(0)}\n` +
`${chalk.red('-')} Failed: ${chalk.bold(failedCount)}`;
console.log(
boxen(summaryContent, {
padding: 1,
margin: { top: 1 },
borderColor: failedCount > 0 ? 'red' : 'green', // Red if failures, green otherwise
borderStyle: 'round'
})
);
}
if (outputFormat === 'text' && aggregatedTelemetryData) {
displayAiUsageSummary(aggregatedTelemetryData, 'cli');
}
// Return summary including the AGGREGATED telemetry data
return {
feat(telemetry): Integrate telemetry for expand-all, aggregate results This commit implements AI usage telemetry for the `expand-all-tasks` command/tool and refactors its CLI output for clarity and consistency. Key Changes: 1. **Telemetry Integration for `expand-all-tasks` (Subtask 77.8):**\n - The `expandAllTasks` core logic (`scripts/modules/task-manager/expand-all-tasks.js`) now calls the `expandTask` function for each eligible task and collects the individual `telemetryData` returned.\n - A new helper function `_aggregateTelemetry` (in `utils.js`) is used to sum up token counts and costs from all individual expansions into a single `telemetryData` object for the entire `expand-all` operation.\n - The `expandAllTasksDirect` wrapper (`mcp-server/src/core/direct-functions/expand-all-tasks.js`) now receives and passes this aggregated `telemetryData` in the MCP response.\n - For CLI usage, `displayAiUsageSummary` is called once with the aggregated telemetry. 2. **Improved CLI Output for `expand-all`:**\n - The `expandAllTasks` core function now handles displaying a final "Expansion Summary" box (showing Attempted, Expanded, Skipped, Failed counts) directly after the aggregated telemetry summary.\n - This consolidates all summary output within the core function for better flow and removes redundant logging from the command action in `scripts/modules/commands.js`.\n - The summary box border is green for success and red if any expansions failed. 3. **Code Refinements:**\n - Ensured `chalk` and `boxen` are imported in `expand-all-tasks.js` for the new summary box.\n - Minor adjustments to logging messages for clarity.
2025-05-08 18:22:00 -04:00
success: true,
expandedCount,
refactor(expand/all): Implement additive expansion and complexity report integration Refactors the `expandTask` and `expandAllTasks` features to complete subtask 61.38 and enhance functionality based on subtask 61.37's refactor. Key Changes: - **Additive Expansion (`expandTask`, `expandAllTasks`):** - Modified `expandTask` default behavior to append newly generated subtasks to any existing ones. - Added a `force` flag (passed down from CLI/MCP via `--force` option/parameter) to `expandTask` and `expandAllTasks`. When `force` is true, existing subtasks are cleared before generating new ones. - Updated relevant CLI command (`expand`), MCP tool (`expand_task`, `expand_all`), and direct function wrappers (`expandTaskDirect`, `expandAllTasksDirect`) to handle and pass the `force` flag. - **Complexity Report Integration (`expandTask`):** - `expandTask` now reads `scripts/task-complexity-report.json`. - If an analysis entry exists for the target task: - `recommendedSubtasks` is used to determine the number of subtasks to generate (unless `--num` is explicitly provided). - `expansionPrompt` is used as the primary prompt content for the AI. - `reasoning` is appended to any additional context provided. - If no report entry exists or the report is missing, it falls back to default subtask count (from config) and standard prompt generation. - **`expandAllTasks` Orchestration:** - Refactored `expandAllTasks` to primarily iterate through eligible tasks (pending/in-progress, considering `force` flag and existing subtasks) and call the updated `expandTask` function for each. - Removed redundant logic (like complexity reading or explicit subtask clearing) now handled within `expandTask`. - Ensures correct context (`session`, `mcpLog`) and flags (`useResearch`, `force`) are passed down. - **Configuration & Cleanup:** - Updated `.cursor/mcp.json` with new Perplexity/Anthropic API keys (old ones invalidated). - Completed refactoring of `expandTask` started in 61.37, confirming usage of `generateTextService` and appropriate prompts. - **Task Management:** - Marked subtask 61.37 as complete. - Updated `.changeset/cuddly-zebras-matter.md` to reflect user-facing changes. These changes finalize the refactoring of the task expansion features, making them more robust, configurable via complexity analysis, and aligned with the unified AI service architecture.
2025-04-25 02:57:08 -04:00
failedCount,
skippedCount: 0,
feat(telemetry): Integrate telemetry for expand-all, aggregate results This commit implements AI usage telemetry for the `expand-all-tasks` command/tool and refactors its CLI output for clarity and consistency. Key Changes: 1. **Telemetry Integration for `expand-all-tasks` (Subtask 77.8):**\n - The `expandAllTasks` core logic (`scripts/modules/task-manager/expand-all-tasks.js`) now calls the `expandTask` function for each eligible task and collects the individual `telemetryData` returned.\n - A new helper function `_aggregateTelemetry` (in `utils.js`) is used to sum up token counts and costs from all individual expansions into a single `telemetryData` object for the entire `expand-all` operation.\n - The `expandAllTasksDirect` wrapper (`mcp-server/src/core/direct-functions/expand-all-tasks.js`) now receives and passes this aggregated `telemetryData` in the MCP response.\n - For CLI usage, `displayAiUsageSummary` is called once with the aggregated telemetry. 2. **Improved CLI Output for `expand-all`:**\n - The `expandAllTasks` core function now handles displaying a final "Expansion Summary" box (showing Attempted, Expanded, Skipped, Failed counts) directly after the aggregated telemetry summary.\n - This consolidates all summary output within the core function for better flow and removes redundant logging from the command action in `scripts/modules/commands.js`.\n - The summary box border is green for success and red if any expansions failed. 3. **Code Refinements:**\n - Ensured `chalk` and `boxen` are imported in `expand-all-tasks.js` for the new summary box.\n - Minor adjustments to logging messages for clarity.
2025-05-08 18:22:00 -04:00
tasksToExpand: tasksToExpandCount,
telemetryData: aggregatedTelemetryData
};
} catch (error) {
refactor(expand/all): Implement additive expansion and complexity report integration Refactors the `expandTask` and `expandAllTasks` features to complete subtask 61.38 and enhance functionality based on subtask 61.37's refactor. Key Changes: - **Additive Expansion (`expandTask`, `expandAllTasks`):** - Modified `expandTask` default behavior to append newly generated subtasks to any existing ones. - Added a `force` flag (passed down from CLI/MCP via `--force` option/parameter) to `expandTask` and `expandAllTasks`. When `force` is true, existing subtasks are cleared before generating new ones. - Updated relevant CLI command (`expand`), MCP tool (`expand_task`, `expand_all`), and direct function wrappers (`expandTaskDirect`, `expandAllTasksDirect`) to handle and pass the `force` flag. - **Complexity Report Integration (`expandTask`):** - `expandTask` now reads `scripts/task-complexity-report.json`. - If an analysis entry exists for the target task: - `recommendedSubtasks` is used to determine the number of subtasks to generate (unless `--num` is explicitly provided). - `expansionPrompt` is used as the primary prompt content for the AI. - `reasoning` is appended to any additional context provided. - If no report entry exists or the report is missing, it falls back to default subtask count (from config) and standard prompt generation. - **`expandAllTasks` Orchestration:** - Refactored `expandAllTasks` to primarily iterate through eligible tasks (pending/in-progress, considering `force` flag and existing subtasks) and call the updated `expandTask` function for each. - Removed redundant logic (like complexity reading or explicit subtask clearing) now handled within `expandTask`. - Ensures correct context (`session`, `mcpLog`) and flags (`useResearch`, `force`) are passed down. - **Configuration & Cleanup:** - Updated `.cursor/mcp.json` with new Perplexity/Anthropic API keys (old ones invalidated). - Completed refactoring of `expandTask` started in 61.37, confirming usage of `generateTextService` and appropriate prompts. - **Task Management:** - Marked subtask 61.37 as complete. - Updated `.changeset/cuddly-zebras-matter.md` to reflect user-facing changes. These changes finalize the refactoring of the task expansion features, making them more robust, configurable via complexity analysis, and aligned with the unified AI service architecture.
2025-04-25 02:57:08 -04:00
if (loadingIndicator)
stopLoadingIndicator(loadingIndicator, 'Error.', false);
logger.error(`Error during expand all operation: ${error.message}`);
if (!isMCPCall && getDebugFlag(session)) {
console.error(error); // Log full stack in debug CLI mode
}
refactor(expand/all): Implement additive expansion and complexity report integration Refactors the `expandTask` and `expandAllTasks` features to complete subtask 61.38 and enhance functionality based on subtask 61.37's refactor. Key Changes: - **Additive Expansion (`expandTask`, `expandAllTasks`):** - Modified `expandTask` default behavior to append newly generated subtasks to any existing ones. - Added a `force` flag (passed down from CLI/MCP via `--force` option/parameter) to `expandTask` and `expandAllTasks`. When `force` is true, existing subtasks are cleared before generating new ones. - Updated relevant CLI command (`expand`), MCP tool (`expand_task`, `expand_all`), and direct function wrappers (`expandTaskDirect`, `expandAllTasksDirect`) to handle and pass the `force` flag. - **Complexity Report Integration (`expandTask`):** - `expandTask` now reads `scripts/task-complexity-report.json`. - If an analysis entry exists for the target task: - `recommendedSubtasks` is used to determine the number of subtasks to generate (unless `--num` is explicitly provided). - `expansionPrompt` is used as the primary prompt content for the AI. - `reasoning` is appended to any additional context provided. - If no report entry exists or the report is missing, it falls back to default subtask count (from config) and standard prompt generation. - **`expandAllTasks` Orchestration:** - Refactored `expandAllTasks` to primarily iterate through eligible tasks (pending/in-progress, considering `force` flag and existing subtasks) and call the updated `expandTask` function for each. - Removed redundant logic (like complexity reading or explicit subtask clearing) now handled within `expandTask`. - Ensures correct context (`session`, `mcpLog`) and flags (`useResearch`, `force`) are passed down. - **Configuration & Cleanup:** - Updated `.cursor/mcp.json` with new Perplexity/Anthropic API keys (old ones invalidated). - Completed refactoring of `expandTask` started in 61.37, confirming usage of `generateTextService` and appropriate prompts. - **Task Management:** - Marked subtask 61.37 as complete. - Updated `.changeset/cuddly-zebras-matter.md` to reflect user-facing changes. These changes finalize the refactoring of the task expansion features, making them more robust, configurable via complexity analysis, and aligned with the unified AI service architecture.
2025-04-25 02:57:08 -04:00
// Re-throw error for the caller to handle, the direct function will format it
throw error; // Let direct function wrapper handle formatting
/* Original re-throw:
throw new Error(`Failed to expand all tasks: ${error.message}`);
*/
}
}
export default expandAllTasks;