[ENHANCEMENT] Show activated model next to each mode in mode selection menu

[pdecat]

Problem (one or two sentences)

Seeing which profile configuration/model is currently selected for each mode is not simple, one has to select each mode one at a time:

Context (who is affected and when)

I'm often caught by surprise when switching modes, especially using the orchestrator mode, to not get the configuration profile I expected.

Desired behavior (conceptual, not technical)

It would be way easier to show the activated profile configuration/model next to each mode in mode selection menu, e.g. like this:

Constraints / preferences (optional)

No response

Request checklist

• I've searched existing Issues and Discussions for duplicates
• This describes a specific problem with clear context and impact

Roo Code Task Links (optional)

No response

Acceptance criteria (optional)

No response

Proposed approach (optional)

I've got a working proof of concept that I use myself and can get in a proper PR submission if this issue is accepted.

Trade-offs / risks (optional)

No response

[roomote]

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

Implementation Approach

Based on my analysis of the codebase, I'll implement this feature by:

1. Extend the state management to include mode-to-model mappings:

   • The backend already tracks which API configuration is active for each mode via modeApiConfigs in ProviderSettingsManager
   • Pass this mapping along with the model information to the webview in getStateToPostToWebview

2. Update the ModeSelector component (webview-ui/src/components/chat/ModeSelector.tsx):

   • Receive the mode-to-model mapping from the extension state
   • For each mode in the dropdown, display the associated model name next to the mode name
   • Handle cases where a mode doesn't have a saved configuration (show default or "Not configured")

3. Ensure proper data flow:

   • When modes switch or API configurations change, the UI will automatically update
   • The model display will reflect the actual configuration that would be used when that mode is selected

Benefits of this approach:

• Minimal changes required - leverages existing infrastructure
• Real-time updates when configurations change
• Clear visual feedback about which model each mode will use
• Handles edge cases (unconfigured modes, missing models)

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

[pdecat]

Is this issue accepted? Can I submit my PR for review?