[Bug]: Context window tooltip shows the wrong provider instance name

[aimsdanny]

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area

apps/web

Steps to reproduce

1. Configure two Codex provider instances/profiles with different display names.
2. Start or resume a thread using the second instance and select one of its models.
3. Generate enough activity for the context-window meter to appear.
4. Open the context-window tooltip.

Expected behavior

The compaction copy should describe the model selected for the active thread, or use neutral copy if its model metadata is unavailable. It should not show the name of another provider instance.

Actual behavior

The tooltip can show the first/default instance name even when the thread uses a different instance. In the example below, the active thread was not using Yufei Pro 20x, but the tooltip said that it would compact its context.

The current lookup finds the exact selected instance, then calls a driver-scoped provider display-name helper. That helper resolves the default instance for the driver, so multiple instances of the same driver can leak the wrong profile name into the tooltip.

Impact

Cosmetic issue. The context statistics remain correct, but the label makes it look like the thread is using a different provider profile.

Version or commit

main at 887dd6e45

Environment

T3 Code web app with multiple Codex provider instances.

Screenshot

Workaround

No functional workaround is needed; the incorrect copy can be ignored.