[ENHANCEMENT] Show active provider + model in the mode

[mikesutton]

Problem (one or two sentences)

Not knowing what model is primarily responsible for processing the current task. This has implications for cost and effectiveness.

Context (who is affected and when)

When I pick a mode , it abstracts the API provider, the prompts etc. That is fine.
The way we set models for modes is not intuitive and generates uncertainty in users - especially new users. So I may be using the 'Code' mode but I cannot easily see what model it is using (without going into settings/providers).

Desired behavior (conceptual, not technical)

I want the mode to have an explicit model setting, not something unintuitive like 'last model used'.

A way to pick the API and Model in the Modes editor is also important. The abstraction of using profiles is not particularly clear.

I think the separation is Settings/Providers is about picking what models you are enabling with keys.
Modes is about which models are you using for which specialised function.

Constraints / preferences (optional)

The explicit setting should be at the bottom of the chat, next to the mode picker , so that when I change modes I can see the provider + model it is set to and that puts the cost in the request in full context.

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)

No response

Trade-offs / risks (optional)

No response

[roomote]

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

Current State

The bottom bar of the chat currently shows three elements in a row:
[ModeSelector] [ApiConfigSelector] [AutoApproveDropdown]

• ModeSelector displays only the mode name (e.g. "Code")
• ApiConfigSelector displays only the API config name (e.g. "default") -- the actual provider and model are hidden unless the user opens the dropdown or goes into settings
• The mapping between modes and API configs exists via modeApiConfigs (mode slug -> config ID), but the resolved model is not surfaced in the UI

Proposed Change

Show the model ID in the ApiConfigSelector trigger button, so the user can immediately see which model is active for the current mode without clicking anything. The bottom bar would look like:

[Code] [default · claude-sonnet-4-20250514] [Auto-Approve v]

When space is tight, the model ID would truncate with ellipsis (it already has text-ellipsis overflow-hidden styling).

Implementation Details

1. ChatTextArea.tsx: In the useMemo that computes currentConfigId and displayName (line ~109), also look up the current config's modelId from listApiConfigMeta and build a richer display string like "configName · modelId" (or just modelId if the config name and model are redundant).

2. ApiConfigSelector.tsx: The trigger button already renders displayName via <span className="truncate">{displayName}</span>. The enhanced display name from step 1 flows through naturally. No changes needed in the selector component itself -- it just renders what it receives.

3. Tooltip enhancement: Add the full provider + model info to the ApiConfigSelector tooltip so that even when the trigger text is truncated, hovering reveals the complete info (e.g. "anthropic / claude-sonnet-4-20250514").

This is a minimal, non-breaking change that:

• Requires no new state or backend changes (all data is already available in listApiConfigMeta)
• Respects the existing responsive layout (truncation handles long model names)
• Directly addresses the core ask: seeing which model is active when switching modes
• Does not alter mode configuration behavior (that's a separate, larger feature)

Out of Scope (for this PR)

The issue also mentions wanting an explicit model picker in the Modes editor and a way to set models per mode. That's a significantly larger UX/architecture change (new settings UI, new state management) and would be better addressed in a follow-up issue. This PR focuses on the immediate visibility problem.

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

[mikesutton]

@roomote I approve this plan

[roomote]

Thanks for the approval @mikesutton! I'll start implementing the plan now -- showing the active model ID alongside the API config name in the bottom bar. I'll open a draft PR shortly to share progress.

[roomote]

Opened a draft PR with my attempt at addressing this: #11292

The bottom bar now shows the model ID alongside the config name (e.g. default · claude-sonnet-4-20250514), and the tooltip shows the full provider info when truncated. Feedback welcome!