Feature: Cancel job on user request in interactive mode

[bhouston]

Description

This PR implements a feature to cancel job execution in interactive mode and provide new instructions.

Changes

• Added a new keyboard shortcut (Ctrl+X) to cancel the current job
• Implemented a confirmation prompt before cancellation
• Added ability to provide new instructions after cancellation
• Updated documentation to reflect the new functionality

How to test

1. Run MyCoder in interactive mode: mycoder -i
2. Start a task
3. While the task is running, press Ctrl+X
4. Confirm cancellation when prompted
5. Enter new instructions
6. Verify that the previous task is cancelled and the new instructions are processed

Fixes #360

[bhouston]

PR Review for #367: Cancel job on user request in interactive mode

Issue Alignment

• ✅ The PR directly addresses the requirements in issue Feature Request: Cancel job on user request in interactive mode #360, which requested the ability to cancel execution in interactive mode and enter new instructions.
• ✅ All requirements from the original issue are satisfied: cancellation, ability to provide new instructions, and proper handling of the agent state.
• ✅ The implementation considers points raised in the issue discussion, including handling sub-agents and providing a clear way to interrupt the current task.
• ✅ No scope creep detected; all changes are focused on the cancellation feature.

Code Quality

• ✅ Clean Design: The code follows a clean design pattern by extending the existing interactive mode infrastructure.
• ✅ Terseness: The code is concise while maintaining readability.
• ✅ Duplication: The code reuses the existing infrastructure for interactive input and message handling, avoiding duplication.
• ✅ Consistency: The implementation follows the same patterns as the existing Ctrl+M functionality for corrections.
• ✅ Naming: Variables and functions are named clearly (e.g., cancelJobFlag, [CANCEL JOB] prefix).
• ✅ Comments: Complex sections are adequately commented, explaining the purpose of each step in the cancellation process.

Function and Component Design

• ✅ Single Responsibility: Each function and component has a clear purpose.
• ✅ Parameter Count: Functions have a reasonable number of parameters.
• ✅ Return Values: Return values are consistent with existing patterns.
• ✅ Error Handling: The implementation includes comprehensive error handling, especially in the interactive input handling.
• ✅ Side Effects: Side effects are documented where necessary, particularly regarding the clearing of conversation history.

Testing

• ℹ️ No specific test files were added or modified in this PR. However, the PR description includes clear testing instructions:
  1. Run MyCoder in interactive mode: mycoder -i
  2. Start a task
  3. While the task is running, press Ctrl+X
  4. Confirm cancellation when prompted
  5. Enter new instructions
  6. Verify that the previous task is cancelled and the new instructions are processed

Documentation

• ✅ The new functionality is properly documented in the README.md file.
• ✅ The CLI help text in options.ts has been updated to mention the new Ctrl+X shortcut.
• ✅ The PR description itself provides clear documentation of the feature and testing instructions.

Performance Considerations

• ✅ No significant performance concerns. The implementation leverages the existing message handling infrastructure.
• ✅ The cancellation process is efficient, with minimal overhead.

Security Considerations

• ✅ No security concerns identified. The feature operates within the existing security boundaries of the application.

Accessibility

• ✅ The feature maintains the keyboard-driven approach of the existing interactive mode, which is good for accessibility.
• ✅ Clear text messages guide the user through the cancellation process.

Browser/Environment Compatibility

• ✅ The implementation uses standard Node.js APIs and should work across all supported environments.
• ✅ No platform-specific code was introduced.

Additional Observations

1. The implementation handles the special case where a user confirms cancellation but doesn't provide new instructions by adding a default message.

2. The code properly resets the interaction counter when a job is cancelled, which prevents hitting iteration limits when starting a new task.

3. The implementation preserves the system message when clearing the conversation history, which maintains the agent's overall behavior and capabilities.

Conclusion

This PR successfully implements the requested feature to cancel job execution in interactive mode and provide new instructions. The implementation is clean, follows project patterns, and includes appropriate documentation. The feature enhances the usability of MyCoder in interactive mode by giving users more control over the agent's execution.

Recommendation

✅ Approve: The PR is ready to be merged as is.