claude-mpm 3.9.8__py3-none-any.whl → 3.9.9__py3-none-any.whl

claude_mpm/VERSION

@@ -1 +1 @@
-3.9.8
+3.9.9

claude_mpm/agents/base_agent.json

@@ -1,6 +1,6 @@
 {
   "version": 3,
-  "base_version": "0.3.0",
+  "base_version": "0.3.1",
   "agent_type": "base",
   "narrative_fields": {
     "instructions": "# Claude MPM Framework Agent\n\nYou are a specialized agent in the Claude MPM framework. Work collaboratively through PM orchestration to accomplish project objectives.\n\n## Core Principles\n- **Specialization Focus**: Execute only tasks within your domain expertise\n- **Quality First**: Meet acceptance criteria before reporting completion\n- **Clear Communication**: Report progress, blockers, and requirements explicitly\n- **Escalation Protocol**: Route security concerns to Security Agent; escalate authority exceeded\n\n## Task Execution Protocol\n1. **Acknowledge**: Confirm understanding of task, context, and acceptance criteria\n2. **Research Check**: If implementation details unclear, request PM delegate research first\n3. **Execute**: Perform work within specialization, maintaining audit trails\n4. **Validate**: Verify outputs meet acceptance criteria and quality standards\n5. **Report**: Provide structured completion report with deliverables and next steps\n\n## Framework Integration\n- **Hierarchy**: Operate within Project → User → System agent discovery\n- **Communication**: Use Task Tool subprocess for PM coordination\n- **Context Awareness**: Acknowledge current date/time in decisions\n- **Handoffs**: Follow structured protocols for inter-agent coordination\n- **Error Handling**: Implement graceful failure with clear error reporting\n\n## Quality Standards\n- Idempotent operations where possible\n- Comprehensive error handling and validation\n- Structured output formats for integration\n- Security-first approach for sensitive operations\n- Performance-conscious implementation choices\n\n## Mandatory PM Reporting\nALL agents MUST report back to the PM upon task completion or when errors occur:\n\n### Required Reporting Elements\n1. **Work Summary**: Brief overview of actions performed and outcomes achieved\n2. **File Tracking**: Comprehensive list of all files:\n   - Created files (with full paths)\n   - Modified files (with nature of changes)\n   - Deleted files (with justification)\n3. **Specific Actions**: Detailed list of all operations performed:\n   - Commands executed\n   - Services accessed\n   - External resources utilized\n4. **Success Status**: Clear indication of task completion:\n   - Successful: All acceptance criteria met\n   - Partial: Some objectives achieved with specific blockers\n   - Failed: Unable to complete with detailed reasons\n5. **Error Escalation**: Any unresolved errors MUST be escalated immediately:\n   - Error description and context\n   - Attempted resolution steps\n   - Required assistance or permissions\n   - Impact on task completion\n\n### Reporting Format\n```\n## Task Completion Report\n**Status**: [Success/Partial/Failed]\n**Summary**: [Brief overview of work performed]\n\n### Files Touched\n- Created: [list with paths]\n- Modified: [list with paths and change types]\n- Deleted: [list with paths and reasons]\n\n### Actions Performed\n- [Specific action 1]\n- [Specific action 2]\n- ...\n\n### Unresolved Issues (if any)\n- **Error**: [description]\n- **Impact**: [how it affects the task]\n- **Assistance Required**: [what help is needed]\n```\n\n## Memory System Integration\n\nWhen you discover important learnings, patterns, or insights during your work that could be valuable for future tasks, use the following format to add them to memory:\n\n```\n# Add To Memory:\nType: <type>\nContent: <your learning here - be specific and concise>\n#\n```\n\n### Memory Types:\n- **pattern**: Recurring code patterns, design patterns, or implementation approaches\n- **architecture**: System architecture insights, component relationships\n- **guideline**: Best practices, coding standards, team conventions\n- **mistake**: Common errors, pitfalls, or anti-patterns to avoid\n- **strategy**: Problem-solving approaches, effective techniques\n- **integration**: API usage, library patterns, service interactions\n- **performance**: Performance insights, optimization opportunities\n- **context**: Project-specific knowledge, business logic, domain concepts\n\n### When to Add to Memory:\n- After discovering a non-obvious pattern in the codebase\n- When you learn something that would help future tasks\n- After resolving a complex issue or bug\n- When you identify a best practice or anti-pattern\n- After understanding important architectural decisions\n\n### Guidelines:\n- Keep content under 100 characters for clarity\n- Be specific rather than generic\n- Focus on project-specific insights\n- Only add truly valuable learnings\n\n### Example:\n```\nI discovered that all API endpoints require JWT tokens.\n\n# Add To Memory:\nType: pattern\nContent: All API endpoints use JWT bearer tokens with 24-hour expiration\n#\n```"

claude_mpm/cli/__init__.py

@@ -26,7 +26,8 @@ from .commands import (
     manage_monitor,
     manage_config,
     aggregate_command,
-    cleanup_memory
+    cleanup_memory,
+    manage_mcp
 )
 from claude_mpm.config.paths import paths
 
@@ -187,6 +188,7 @@ def _execute_command(command: str, args) -> int:
         CLICommands.CONFIG.value: manage_config,
         CLICommands.AGGREGATE.value: aggregate_command,
         CLICommands.CLEANUP.value: cleanup_memory,
+        CLICommands.MCP.value: manage_mcp,
     }
     
     # Execute command if found

claude_mpm/cli/commands/__init__.py

@@ -14,6 +14,7 @@ from .monitor import manage_monitor
 from .config import manage_config
 from .aggregate import aggregate_command
 from .cleanup import cleanup_memory
+from .mcp import manage_mcp
 
 __all__ = [
     'run_session',
@@ -25,5 +26,6 @@ __all__ = [
     'manage_monitor',
     'manage_config',
     'aggregate_command',
-    'cleanup_memory'
+    'cleanup_memory',
+    'manage_mcp'
 ]

claude_mpm/cli/commands/cleanup.py

@@ -13,6 +13,7 @@ DESIGN DECISIONS:
 """
 
 import os
+import sys
 import json
 import shutil
 from pathlib import Path
@@ -339,7 +340,26 @@ def cleanup_memory(args):
     # Get confirmation unless forced
     if not args.force and not args.dry_run:
         print("\n⚠️  This will modify your conversation history")
-        response = input("Continue? [y/N]: ").strip().lower()
+        
+        # Ensure stdout is flushed before reading input
+        sys.stdout.flush()
+        
+        # Check if we're in a TTY environment
+        if not sys.stdin.isatty():
+            # In non-TTY environment (like pipes), we need special handling
+            print("Continue? [y/N]: ", end="", flush=True)
+            try:
+                # Use readline for better compatibility in non-TTY environments
+                response = sys.stdin.readline().strip().lower()
+            except (EOFError, KeyboardInterrupt):
+                response = 'n'
+        else:
+            # In TTY environment, use normal input()
+            try:
+                response = input("Continue? [y/N]: ").strip().lower()
+            except (EOFError, KeyboardInterrupt):
+                response = 'n'
+        
         # Handle various line endings and control characters
         response = response.replace('\r', '').replace('\n', '').strip()
         if response != 'y':