ros/claude-task-master
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat(telemetry): Integrate AI usage telemetry into update-tasks

Browse Source 
This commit applies the standard telemetry pattern to the update-tasks command and its corresponding MCP tool.

Key Changes:

1.  Core Logic (scripts/modules/task-manager/update-tasks.js):
    -   The call to generateTextService now includes commandName: 'update-tasks' and outputType.
    -   The full response { mainResult, telemetryData } is captured.
    -   mainResult (the AI-generated text) is used for parsing the updated task JSON.
    -   If running in CLI mode (outputFormat === 'text'), displayAiUsageSummary is called with the telemetryData.
    -   The function now returns { success: true, updatedTasks: ..., telemetryData: ... }.

2.  Direct Function (mcp-server/src/core/direct-functions/update-tasks.js):
    -   The call to the core updateTasks function now passes the necessary context for telemetry (commandName, outputType).
    -   The successful response object now correctly extracts coreResult.telemetryData and includes it in the data.telemetryData field returned to the MCP client.
This commit is contained in:
Eyal Toledano
2025-05-08 18:51:29 -04:00
parent c955431753
commit bbc8b9cc1f
7 changed files with 163 additions and 139 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
tasks/task_081.txt
View File

@@ -41,6 +41,12 @@ Key implementation details:
- Add commands to export telemetry data for manual analysis
- Create visualization tools for local telemetry data
6. Focus on user-facing benefits:
- Implement personal usage dashboards showing the user's own patterns
- Add productivity insights based on collected telemetry
- Create features that allow users to optimize their workflow based on their usage data
- Ensure all telemetry collection provides immediate value to the user
# Test Strategy:
The testing strategy for the expanded telemetry system should be comprehensive and cover all aspects of the implementation:
@@ -74,6 +80,7 @@ The testing strategy for the expanded telemetry system should be comprehensive a
- Test different telemetry level configurations
- Manually verify the accuracy of collected metrics
- Test the export functionality and analyze the exported data
- Validate that user-facing insights and dashboards provide accurate and useful information
6. Privacy Compliance Testing:
- Verify no PII is stored without proper anonymization
@@ -84,6 +91,11 @@ The testing strategy for the expanded telemetry system should be comprehensive a
- Verify existing functionality continues to work with the expanded telemetry
- Ensure the system is designed to be compatible with future server integration
8. User Experience Testing:
- Test the usability of personal dashboards and insights features
- Gather feedback on the usefulness of telemetry-based recommendations
- Verify users can easily understand their own usage patterns
# Subtasks:
## 1. Implement Additional Telemetry Data Collection Points [pending]
### Dependencies: None
@@ -115,3 +127,9 @@ Create a telemetry sanitization layer that removes or hashes PII before storage.
### Details:
Implement a developer console command to toggle telemetry debug mode. Create a UI panel that displays collected telemetry data when in debug mode. Add detailed logging of telemetry events to the application log when debugging is enabled. Create commands to export telemetry data in various formats (JSON, CSV) for manual analysis. Implement basic visualization tools for local telemetry data to help users understand their own usage patterns.
## 6. Develop User-Facing Telemetry Benefits [pending]
### Dependencies: 81.1, 81.2
### Description: Create features that provide immediate value to users based on their telemetry data, focusing on personal insights and workflow optimization.
### Details:
Implement a personal usage dashboard that visualizes the user's command usage patterns, feature adoption, and productivity trends. Create a 'productivity insights' feature that offers personalized recommendations based on usage patterns. Add workflow optimization suggestions that help users discover more efficient ways to use the application. Develop weekly/monthly usage reports that users can view to track their own progress. Ensure all telemetry collection has a direct benefit to the user in the absence of server-side analysis.