Inconsistent user content wrapper tags across codebase

[hannesrudolph]

Problem

The codebase uses multiple different XML tags to wrap user content in prompts: <task>, <feedback>, <answer>, and <user_message>. This inconsistency creates unnecessary complexity in content handling and parsing logic.

Impact

• Developers: Must maintain separate detection logic for each tag type, increasing code complexity and maintenance burden
• LLM Processing: The model must handle multiple tag formats for semantically similar content, which adds cognitive overhead to prompt processing
• Code Maintainability: Changes to user content handling require updates across multiple tag detection points, increasing the risk of bugs and inconsistencies

[roomote]

I've analyzed this issue and here's my proposed implementation plan:

Summary of Findings

The codebase uses four different XML tags to wrap user content in prompts:

1. <task> - Used in Task.ts for initial user tasks
2. <feedback> - Used in responses.ts, ExecuteCommandTool.ts, AttemptCompletionTool.ts for user feedback
3. <answer> - Used in AskFollowupQuestionTool.ts for followup question answers
4. <user_message> - Used in Task.ts for task continuation messages

All of these are detected in processUserContentMentions.ts to trigger mention parsing.

Proposed Solution

Standardize on <user_message> as the unified tag for all user content wrappers because:

• It's semantically neutral and descriptive
• It clearly indicates the content is from the user
• It doesn't carry context that might be misleading in other scenarios

Files to Modify

1. src/core/task/Task.ts - Change <task> wrapper (line 1868) to <user_message>
2. src/core/prompts/responses.ts - Change <feedback> wrappers (lines 27, 38, 88) to <user_message>
3. src/core/tools/AskFollowupQuestionTool.ts - Change <answer> wrapper (line 89) to <user_message>
4. src/core/tools/ExecuteCommandTool.ts - Change <feedback> wrapper (line 344) to <user_message>
5. src/core/tools/AttemptCompletionTool.ts - Change <feedback> wrapper (line 153) to <user_message>
6. src/core/mentions/processUserContentMentions.ts - Simplify detection to only check for <user_message>

Note: The <task> tags inside <fetch_instructions> blocks (in modes.ts, mcp-servers.ts, fetch-instructions.ts) are tool parameters, not user content wrappers, so they will NOT be changed.

Benefits

• Reduces code complexity in mention detection from 4 conditions to 1
• Simplifies maintenance and reduces risk of bugs
• Provides consistent semantics for LLM processing

Please mention @roomote in a comment saying that you approve this plan, and I'll proceed with the implementation.